<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Sentinel IPS on Medium]]></title>
        <description><![CDATA[Stories by Sentinel IPS on Medium]]></description>
        <link>https://medium.com/@SentinelIPS?source=rss-acb8d295aa1c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*HVTeepY3tMHaGaMZ.png</url>
            <title>Stories by Sentinel IPS on Medium</title>
            <link>https://medium.com/@SentinelIPS?source=rss-acb8d295aa1c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 19:26:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@SentinelIPS/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Four Security Concepts to Know in 2016]]></title>
            <link>https://medium.com/@SentinelIPS/four-security-concepts-to-know-in-2016-1c0babafc224?source=rss-acb8d295aa1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c0babafc224</guid>
            <category><![CDATA[network-security]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[data-security]]></category>
            <dc:creator><![CDATA[Sentinel IPS]]></dc:creator>
            <pubDate>Mon, 15 Feb 2016 00:00:00 GMT</pubDate>
            <atom:updated>2016-02-17T21:14:10.533Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/734/0*a8emuFt_kXsrtKsG.jpg" /></figure><p>Network security can’t be a passive thing. Those who want into your network are constantly figuring out new ways to get there. If you’ve read this blog for any length of time, that should be a somewhat familiar message. And if that message feels familiar, so should this one. Because hackers are evolving their methods of attacking your networks then you need to be evolving your methods of defending yourself from them.</p><p>One of the best ways to do that is through education, and not just on new devices coming to the market, but by making sure you are familiar with emerging concepts and ideas.</p><p>With that in mind, we have four definitions and concepts you need to be familiar with for the new year.</p><h4>Passphrases</h4><p>We have spent years teaching people how to build strong passwords. The problem is we’ve been doing it wrong. We’ve told them that they need to use complicated combinations of letters, numbers and symbols that are hard to remember but relatively easy for a computer to crack.</p><p>What we should be encouraging instead are passphrases, strings of three and four random words that the user can easily remember but are infinitely harder for a computer to guess. We encourage their use by retraining our employs about what a strong password looks like then using updated algorithms that help determine if what employees are using is actually strong.</p><h4>Visibility</h4><p>Admittedly, visibility is a word that might start to lose a little bit of meaning due to it being just about everywhere. Almost every network security vendor mentions it at some point. The idea is that you need to have (automated) eyes on your servers, your endpoints, your switches and on the wire. What this feels like to us is the new way to talk about layered security, something that’s still a must-have but a term that has become a bit dated.</p><h4>Heuristics and Machine Learning</h4><p>These technical terms have been usurped by marketing departments to create blingy copy for all manner of network security companies, but the general idea is this: Based on measurable observations of a computer’s or program’s behavior, you can use algorithms to predict whether that behavior is malicious or not. If it is, you then do something to stop it. This varies from traditional security methods like firewall rules (which are simply ‘yes’ and ‘no’ policy-based decisions) and signature-based tools (which identify malicious traffic based on previously observed markers). Both of these traditional methods are passive. They rely on something to have happened. Using these newer techniques, security becomes more proactive.</p><p>Why is important to know these concepts? Because there are a lot of products out there touting their use of heuristics and machine learning. You need to be able to separate the hype from the reality.</p><h4>Vulnerability</h4><p>Ok, not a new term. We’ll admit that. But it’s not just the new ideas and concepts that are relevant to security. We can get a little bit caught in the shiny stuff, those things that we’ve never seen before. But keep in mind that 44 percent of breaches in 2014 came from old, unpatched vulnerabilities. The basics of network security are still important. Updated software. Strong passwords (or, better, passphrases). Smart and aware people. Those things have to be in place whether you have the newest devices or not.</p><p><em>Originally published at </em><a href="http://sentinelips.com/blog/2016/02/15/four-security-concepts-know-2016/"><em>sentinelips.com</em></a><em> on February 15, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c0babafc224" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lessons from the Annual Worst Passwords List]]></title>
            <link>https://medium.com/@SentinelIPS/lessons-from-the-annual-worst-passwords-list-5f401b484d24?source=rss-acb8d295aa1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/5f401b484d24</guid>
            <category><![CDATA[passwords]]></category>
            <category><![CDATA[network-security]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Sentinel IPS]]></dc:creator>
            <pubDate>Wed, 27 Jan 2016 00:00:00 GMT</pubDate>
            <atom:updated>2016-02-17T21:13:21.623Z</atom:updated>
            <content:encoded><![CDATA[<p>The annual list of bad passwords was released last week. The list for 2015 looks a lot like the list for the previous years. Still, these are always good for a bewildered chuckle.</p><p><em>Password</em> is still an unfortunately popular password. So is <em>123456</em> and the longer <em>12345678</em>. Sequential key combinations still rank very highly, although they shouldn’t. We’re looking at you QWERTY users. Then there are the pop culture references that people probably think are unique but actually aren’t. This year’s examples: <em>solo</em> and <em>starwars</em>.</p><p>But before we poke our fun and put the list aside, it’s worth asking if one of these passwords — or one that’s equally weak — is all that’s separating your network from a significant data breach.</p><p>Don’t be so quick with a confident no. While the passwords used by your employees may not make this list, chances are they aren’t as strong as you think. That’s because we’ve spent years teaching people the wrong way to create strong passwords. We tell them that they need to be using letters, numbers, special characters and all in different combinations. And while that makes for a password that’s definitely hard to remember, it doesn’t create a password that is much stronger than those on the list.</p><p>Essentially, even those “stronger” passwords aren’t that strong when put up against rainbow tables and sophisticated brute force hacking techniques. This classic cartoon from <a href="https://xkcd.com/936/">XKCD</a> does a better job of explaining it than we can:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/0*KyAGiOzM34umvci-.png" /></figure><p>With so many systems and web sites that require passwords, it’s difficult to mandate what passwords people use, but it’s still important to know what makes a good password and then training your people to use them.</p><p>While fancy hacking, DDoS, and malware may get all the headlines, the majority of breaches still come down to someone stealing (or guessing, or brute forcing) a user’s legitimate credentials. That’s why even though passwords are “boring”, they are still a really, really big deal.</p><p><em>Originally published at </em><a href="http://sentinelips.com/blog/2016/01/27/lessons-annual-worst-passwords-list/"><em>sentinelips.com</em></a><em> on January 27, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5f401b484d24" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Internet Explorer’s retirement means for you]]></title>
            <link>https://medium.com/@SentinelIPS/what-internet-explorer-s-retirement-means-for-you-7cff9cc2e9ce?source=rss-acb8d295aa1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/7cff9cc2e9ce</guid>
            <category><![CDATA[network-security]]></category>
            <category><![CDATA[data-security]]></category>
            <category><![CDATA[internet-explorer]]></category>
            <dc:creator><![CDATA[Sentinel IPS]]></dc:creator>
            <pubDate>Tue, 19 Jan 2016 00:00:00 GMT</pubDate>
            <atom:updated>2016-02-17T21:12:16.688Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/250/0*3dLLtyG_hyB4h0xr.png" /></figure><p>There was a lot of talk last week about Microsoft putting its browser Internet Explorer out to pasture. If you missed the news — hard to do for anyone with even a passing interest in technology, but not impossible — the software giant announced that it was no longer going to support any of the legacy versions of the browser and would only continue making updates to its latest version, IE 11, for a limited time. Instead, the company was going to focus on its new browser, Microsoft Edge, which comes with Windows 10.</p><p>The story obviously prompted fits of nostalgia, memories of times when the Internet was slower and graphics a little clunkier. But now that the moment of reflection has passed, it’s time to talk about the implications of Microsoft’s move, because there are some, and what those might mean for you.</p><p><strong>It’s time to move to IE 11.</strong> While Microsoft is retiring all versions of Internet Explorer up to IE 10, they are also making sure that the version of IE they will support — IE 11 — will be compatible with all versions of Windows as far back as Windows 7. In other words, unless you are running legacy applications that won’t work without an older version of Internet Explorer (And, if you are, then you probably need to take a close look at your stable of current applications.) then you have no reason to not upgrade to IE 11.</p><p><strong>Embrace the better browser.</strong> Microsoft has done a good job — some might argue they’ve overdone it — of pushing people toward Windows 10. Many who haven’t upgraded are seeing daily reminders that a new version of the operating system is available. There are plenty of reasons to hesitate when it comes to upgrades: Bugs in early versions; the software compatibility we’ve mentioned. But, if losing Internet Explorer was one of the reasons for you, it shouldn’t be. The Edge browser that comes with Windows 10 is proving to be a high-quality successor in regards to both security and development.</p><p><strong>Stiffen your defenses.</strong> Now, for those who just can’t make the upgrade, you are going to be stuck, at least for a time, on software that’s unsupported and increasingly vulnerable. It’s going to be up to you to stop people from exploiting your network. First and foremost, make sure you’re running the latest and greatest (and final) version of IE and its accompanying OS.</p><p>In addition, you’ll need to have the tools in place to keep your network as secure as possible. Start with the most basic, old-school thing you can do: solid anti-virus software. If Microsoft won’t support this stuff anymore, at least the AV vendors will do their best to keep up with any new vulnerabilities. Of course there are other endpoint solutions, and network-based devices that can help, too. For example, some IPS/IDS devices (full disclosure: like ours) can do a good job of identifying adware and malware traffic on infected endpoints, and stopping communication to malware command and control servers.</p><p>Stay safe!</p><p><em>Originally published at </em><a href="http://sentinelips.com/blog/2016/01/19/what-internet-explorers-retirement-means-you/"><em>sentinelips.com</em></a><em> on January 19, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7cff9cc2e9ce" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Battling Local Government Security Misconceptions: Security is a Shared Responsibility]]></title>
            <link>https://medium.com/@SentinelIPS/battling-local-government-security-misconceptions-security-is-a-shared-responsibility-e6843498fc9f?source=rss-acb8d295aa1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6843498fc9f</guid>
            <category><![CDATA[data-security]]></category>
            <category><![CDATA[government]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Sentinel IPS]]></dc:creator>
            <pubDate>Wed, 13 Jan 2016 00:00:00 GMT</pubDate>
            <atom:updated>2016-02-17T21:11:10.568Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/497/0*yQTMh-ENrxzV-1-5.jpg" /></figure><p>Over the last few weeks, we’ve been looking at common security misconceptions that plague state and local governments. There’s one more that we’ll examine on the blog although <a href="http://sentinelips.com/government/">we identify six in the ebook we recently published.</a> This last one is different than the three that have come before in that this one feels like it shouldn’t be a misconception at all. Here it is.</p><h4>Misconception No. 4: Security is a shared responsibility.</h4><p>That’s true, right? Security should be a shared responsibility. We all have a part in keeping whatever network we work in secure, don’t we? Well, yes. We do. And that’s why we advocate for training staff on constantly evolving tactics for breaching networks.</p><p>While every network is unique, there are two things that are common to almost all local government data centers: They have small budgets and small staffs, including some counties that are running with entire departments made up of one person.</p><p>Often, it’s teams of two, three, four people that are responsible for not only maintaining the network, but also maintaining end point devices and taking help desk calls. They are sharing the responsibility for all IT projects, including security.</p><p>The problem is that when it’s everyone’s job to monitor the networks security, chances are no one is actually doing it because they assume “well, someone else has taken care of that.” Security isn’t something that can be done by committee. It requires dedication and focus. It ultimately has to land at the feet of someone. And that’s how this misconception is corrected.</p><p><strong>How to combat this misconception:</strong> The only way to give security the attention it deserves is by hiring someone who knows his or her stuff and can concentrate on it. The argument against this is obvious. It’s not in the budget. The reality is you can’t afford for it not to be.</p><p>The cost of even a single breach can be staggering. Today, the average server rebuild costs about $60,000 per server. If you get hacked, the chances are high that you will have to at least rebuild one of your servers, and that’s almost an automatic $60,000 spent. And that doesn’t include any remediation costs that may come with a data breach, like paying for credit monitoring for anyone who may have been affected.</p><p>Without someone in place who knows security, you’re betting that you’re not going to be hacked, so you’re not going to have to spend that $60,000. But a good risk manager would spend $60,000 up front to better protect the server, because if you are hacked you’re going to end up spending the $60,000 one way or the other. It’s just a matter of when, how, and what other costs are going to be associated with it.</p><p><strong>Another route to consider: outsourcing.</strong> Whether it’s moving parts of your network to the cloud or using remotely managed devices, you can save money, time, and get top-level protection by looking to outside vendors to help you manage your security.</p><p><em>Originally published at </em><a href="http://sentinelips.com/blog/2016/01/13/battling-local-government-security-misconceptions-security-shared-responsibility/"><em>sentinelips.com</em></a><em> on January 13, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6843498fc9f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Battling Local Government Security Misconceptions: Last Year’s Training is Still Valid]]></title>
            <link>https://medium.com/@SentinelIPS/battling-local-government-security-misconceptions-last-year-s-training-is-still-valid-262f60ad1d52?source=rss-acb8d295aa1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/262f60ad1d52</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[government]]></category>
            <dc:creator><![CDATA[Sentinel IPS]]></dc:creator>
            <pubDate>Mon, 04 Jan 2016 00:00:00 GMT</pubDate>
            <atom:updated>2016-02-17T21:10:21.591Z</atom:updated>
            <content:encoded><![CDATA[<p>There’s nothing new about social engineering. It’s old-fashioned con artistry with a fancier sounding name. The Trojans had their horse. The schemer on the streets has his game of three-card Monte. And hackers and cybercriminals have their own tactics.</p><p>You’ve no doubt heard of (and received) phishing emails, when someone sends a legitimate looking message with an attachment that will infect a network if opened by an unsuspecting employee. Chances are your employees have seen them, too. At least they are familiar with the tactic, even if they don’t know exactly what it’s called.</p><p>What about water holing, though? Do your employees know what that is? Do you? That’s the practice of hackers infecting sites that people from their target company may go to and then infecting computers on the target network once users there do visit those sites. It’s a bit of a guessing game, and it can take a bit of time to be effective. But for hackers, it’s worth the effort.</p><p>The hacker’s playbook is big, and it’s growing. New threats, whether they are vulnerabilities in software or social engineering techniques, are emerging all the time. That’s why organizations can’t rely on last year’s training to be enough to protect today’s network. Still, that’s what many state and local governments are doing.</p><p>We’ve been looking at security misconceptions over the last few posts, and this is the third one that needs to be addressed.</p><h4>Misconception No. 3: Last year’s training is enough to keep the network safe.</h4><p>More and more, hackers are turning away from these brute force attacks and malware as the means of getting into a network. Instead, they are counting on the naiveté, and some would say ignorance, of the typical employee. They are using social engineering schemes to trick these employees into providing them with legitimate ways to enter the network.</p><p>It’s OK, though, because the training that was held a year or two ago covered all of those tricks. The network is protected. Well, that’s true if your company never hired another employee after that training. And if hackers weren’t constantly evolving their methods. Oh, and if your employees remember everything they learned two years ago. Unfortunately, that’s probably not the case.</p><p>How to combat this misconception: Training needs to be thorough, regular, and ongoing. Unfortunately, for smaller organizations the execution of that training is probably falling to someone in the IT department, and training and educating aren’t really in the skillsets of many in IT.</p><p>With that in mind, here are some things to know about effective training.</p><p><strong>Use Simplified Language</strong></p><ul><li>Speaking on a level that employees can fully comprehend is essential. It will result in fewer of your employees being confused and unsure about what they’re learning.</li></ul><p><strong>Encourage questions</strong></p><ul><li>The only way to know if what’s being conveyed is being understood is by encouraging questions. Stop and ask specific individuals questions regarding the content in order to reassure that everyone is on the same page.</li></ul><p><strong>Regular education and testing</strong></p><ul><li>Hackers are continually trying new methods for getting into a network. Keeping employees up to date on these methods is critical. The easiest way to do that is with a regular newsletter that addresses new or recurring threats.</li></ul><p>As the saying goes, a chain is only as strong as its weakest link. The only way you’ll know where those weak links are is by randomly testing employees on social engineering tactics.</p><p><em>Originally published at </em><a href="http://sentinelips.com/blog/2016/01/04/battling-local-government-security-misconceptions-last-years-training-still-valid/"><em>sentinelips.com</em></a><em> on January 4, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=262f60ad1d52" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Battling Local Government Security Misconceptions: I Know Where My Data Is]]></title>
            <link>https://medium.com/@SentinelIPS/battling-local-government-security-misconceptions-i-know-where-my-data-is-68037fe3ee7?source=rss-acb8d295aa1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/68037fe3ee7</guid>
            <category><![CDATA[data-security]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[government]]></category>
            <dc:creator><![CDATA[Sentinel IPS]]></dc:creator>
            <pubDate>Fri, 18 Dec 2015 00:00:00 GMT</pubDate>
            <atom:updated>2016-02-17T21:09:10.943Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*RiVLH_RlcjSkj2rs.jpg" /></figure><p>Here’s a pretty staggering number: 34,220,504.</p><p>That’s the number of personal records exposed, according to the Identity Theft Resource Center, through November 2015 because of government data breaches.</p><p>While that number does include some pretty high profile federal breaches, it also includes many more at the local level that didn’t make national headlines. Clearly, governments are going to be popular targets for hackers. The breadth of data they have on their citizens makes them enticing.</p><p>Unfortunately, local governments are also some of the easiest targets. <a href="http://sentinelips.com/blog/P/">We recently took a look at some of the data that we have from the networks we protect, and it bore that out.</a> By far, the Sentinels that tripped the most alerts were those that were protecting local governments and educational facilities. Those networks were four times as likely to be infected with Cryptowall and were responsible for 95 percent of all Kovter attacks that we saw.</p><p>Why is that these local government networks are so vulnerable? From our experience, it’s because there are six common misconceptions believed by local government employees that keep them from securing their networks. Over the next few posts, we will share those misconceptions with you and also provide ways that you can battle them.</p><p><strong>Misconception No. 2: I know exactly where my data is.</strong></p><p>There’s one commonality among all the news stories about federal government data breaches. In each instance, officials knew exactly what kind of information was compromised. If those stories had been about local governments instead, the information wouldn’t have been so detailed.</p><p>That’s because at the federal level, network administrators usually know exactly what information is living where. If Server A was breached then that means names and addresses were compromised. Server C it’s Social Security data.</p><p>At the local level, you may believe that you know where your data is, but you don’t. Not specifically. With single servers handling multiple departments and applications, knowing where data is to the level of detail that the federal agencies have isn’t possible. A single breach of a single server could mean that information from several departments has been compromised.</p><p>How to combat this misconception: To some degree, the local officials aren’t necessarily to blame. This is a misconception that can be blamed on dollars and cents. Buying a server for a single department or application is expensive, too expensive for many. Why buy four SQL servers when you only need one?</p><p>The solution: virtualization. Run virtual machines, splitting up your apps across the VMs, and segmenting the data. For example: If you’re using SQL servers, you are going to need to protect those databases. That means putting something on the wire that can recognize the difference between normal and abnormal calls and then something on the server that can segregate databases and permit only those with permission to access the tables.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/721/0*jewrbNdTMFyneuAu.png" /></figure><p><em>Originally published at </em><a href="http://sentinelips.com/blog/2015/12/18/battling-local-government-security-misconceptions-i-know-where-my-data/"><em>sentinelips.com</em></a><em> on December 18, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=68037fe3ee7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Battling Local Government Security Misconceptions: Our Data is Already Public]]></title>
            <link>https://medium.com/@SentinelIPS/battling-local-government-security-misconceptions-our-data-is-already-public-bbada53eb0df?source=rss-acb8d295aa1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/bbada53eb0df</guid>
            <category><![CDATA[data-security]]></category>
            <category><![CDATA[government]]></category>
            <category><![CDATA[network-security]]></category>
            <dc:creator><![CDATA[Sentinel IPS]]></dc:creator>
            <pubDate>Fri, 11 Dec 2015 00:00:00 GMT</pubDate>
            <atom:updated>2016-02-17T21:08:24.462Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*gMjRMPpl5wVJypU8.jpg" /></figure><p>There’s a saying that we’ve always liked: It’s a poor artist who blames his tools. There are other versions of that. They usually replace the word artist with workman, but we like our version better. Either way, though, the point is the same. Failings can rarely be blamed on the tools used in the execution.</p><p>The same thing can be said about network security breaches. Rarely do they happen solely because of bad equipment. Instead, there is almost always some other reason that the criminally minded were able to get into a network. Old software left a door open. Poorly installed equipment weakened defenses. Or — most often — someone unintentionally gave away login credentials because they simply didn’t know any better.</p><p>All of this points to the need for a change in approach. We have to stop thinking about security in terms of tools. And in some cases, there are some industries where misconceptions about security are so rampant that we need to clear those up before we can even talk about network protection. One of those industries is one where we have quite a bit of experience: local governments.</p><p>What we’ve found is that there are six common misconceptions believed by local government employees that hold them back from making their networks as secure as they could be. Over the next few posts, we will share those misconceptions with you and also provide ways that you can battle them if you find a particular misconception is something your organization is struggling with.</p><p><strong>Misconception No. 1: All of our information is public, so a breach isn’t really that damaging.</strong></p><p>While open records legislation has been wonderful for helping shine light into some areas of government that have been dark for too long, it’s also created a bit of confusion for those tasked with controlling who can see what.</p><p>The clerks working in some local government offices may see so many requests from activist groups or reporters or the public that they assume all information is public, so keeping the data digitally secure isn’t really necessary.</p><p>The truth is, most information that’s being held by local governments and agencies isn’t inherently public. Some of it can be obtained through the proper channels, but putting security in place to protect it is still necessary.</p><p><strong>How to battle this misconception:</strong> This is a battle fought on two fronts. The first is employees who don’t know any better. You have to educate them about what information is public, what is private, and when the court can order that information be turned over. While state and local governments do not have to adhere to federal Freedom of Information Act rules, all 50 states have adopted some type of open records law. So step one in fighting this misconception is making sure employees are familiar with the regulations that apply to them.</p><p><a href="http://www.rcfp.org/open-government-guide">Use this Open Government Guide to determine what information is public in your state.</a></p><p>The second front in combatting this misconception is disorganized data. Too many local governments can’t tell HIPAA data, from criminal data, from Social Security numbers. This presents two problems. First is that without classifying data simply as either public or private, you are making the work of your local clerks twice as hard. Data has to be managed in a whole different way. It has to be segmented. It has to be segregated. It has to be classified. And second, if you don’t know what information is private, you don’t know what information to protect. You don’t know where to put your stoutest defenses and build your highest walls.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/721/0*51z53b91x5NmZVWQ.png" /></figure><p><em>Originally published at </em><a href="http://sentinelips.com/blog/2015/12/11/battling-local-government-security-misconceptions-our-data-already-public/"><em>sentinelips.com</em></a><em> on December 11, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bbada53eb0df" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is It Time to Outsource Your Network Security?]]></title>
            <link>https://medium.com/@SentinelIPS/is-it-time-to-outsource-your-network-security-f84443c867ba?source=rss-acb8d295aa1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/f84443c867ba</guid>
            <category><![CDATA[data-security]]></category>
            <category><![CDATA[it-security]]></category>
            <category><![CDATA[network-security]]></category>
            <dc:creator><![CDATA[Sentinel IPS]]></dc:creator>
            <pubDate>Mon, 30 Nov 2015 00:00:00 GMT</pubDate>
            <atom:updated>2016-02-17T21:06:34.756Z</atom:updated>
            <content:encoded><![CDATA[<p>We are going to admit right from the outset that this post will seem self-serving. We are a company that provides a managed security service, so when we say what we are going to say you’ll think to yourself, “Well, sure. Of course that’s your opinion.” But, we’re going to say it anyway because it’s true. Here it is: Whenever possible, you should outsource your network security.</p><p>Now, if we were the only ones to say this, then we probably wouldn’t have said it at all. At least we wouldn’t have said it this matter of factly. But we aren’t the only ones to say it.</p><p><a href="https://www.secdata.com/resource/towards-threat-widsom-combining-data-context-and-expertise-to-optimise-threat-intelligence/">A recent report by IDC</a> and sponsored by SecureData was interesting on a couple of fronts. It focused on the use of threat intelligence by 300 large companies in the United Kingdom. For a company like ours that preaches the importance of threat intelligence, all of the conclusions were worth diving into. But it’s the last one that we want to focus on.</p><p>This is what it said:</p><p>Our study shows that around two-thirds of organizations outsource some or all of their security operations to a third party. One might think that they do this because of cost drivers, or because they cannot find sufficient staff to resource those operations. In fact, <em>our survey suggests that the primary driver for outsourcing is to achieve better performance</em>, most notably in improvements in visibility, monitoring and overall control of security.</p><p>The emphasis there is ours, but it’s worth reading again.</p><p><em>“… our survey suggests that the primary driver for outsourcing is to achieve better performance …”</em></p><p>The 300 companies in the survey each have more than 500 employees. These aren’t small businesses. These are businesses that have budget for IT departments. They can probably afford to hire staff members who can focus on security. Still, they aren’t. That’s because they’ve realized what a lot of smaller companies struggle to see. Often, hiring someone to handle either a portion of your security or someone to manage all of it will get you better results than you can get if you manage it on your own.</p><p>That’s no slight on the IT staffs at these smaller companies. Often, they are a small team with a small budget and are already asked to do a hero’s work. They keep the company network running; they handle the day-to-day support tasks that a help desk would often be asked to remedy. They keep software updated and upgraded. They don’t have the time to handle a complicated task like keeping the network secure on their own, not to the level that it needs to be managed.</p><p>The security world changes faster than maybe any other IT concern. New threats emerge everyday. New vulnerabilities are exposed. New methods of infiltration are constantly introduced. It’s hard enough for someone who does nothing but focus on security to keep up. For someone who has a dozen other IT concerns on their plate, it’s impossible.</p><p>Visibility into network traffic is too important to be left half done, or worse, undone. Monitoring is too important. Threat management is too. If security is something that you are struggling with, maybe it’s time to consider outsourcing some or all of your security operation. The people who do security all day, every day can get you better results. Studies prove it.</p><p><em>Originally published at </em><a href="http://sentinelips.com/blog/2015/11/30/it-time-outsource-your-network-security/"><em>sentinelips.com</em></a><em> on November 30, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f84443c867ba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Infographic: Security Mindsets to Adopt Today]]></title>
            <link>https://medium.com/@SentinelIPS/infographic-security-mindsets-to-adopt-today-1bc92ad920d0?source=rss-acb8d295aa1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/1bc92ad920d0</guid>
            <category><![CDATA[network-security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Sentinel IPS]]></dc:creator>
            <pubDate>Tue, 22 Sep 2015 21:04:25 GMT</pubDate>
            <atom:updated>2015-09-22T21:04:25.646Z</atom:updated>
            <content:encoded><![CDATA[<p>In today’s world, the landscape of network security is constantly evolving. High profile security breaches and vulnerabilities (think Ashley Madison, Target, and Heartbleed) have prompted increased awareness of cybersecurity, spurring on the continued advancement of emerging technologies.</p><p>But even the creation of updated devices and highly technical tools hasn’t stopped new breaches from happening. The reality is that if a cybercriminal is determined to get into your network, steal data or disrupt performance, one tool isn’t going to stop them.</p><p>Hackers constantly evolve their methods, enabling them to find new vulnerabilities to exploit. For that reason, the tool that works today will likely be much less effective tomorrow. And beyond that, every network is different. What might make sense for one might not for another.</p><p><strong>So is it a lost cause to effectively protect your network’s valuable information?</strong></p><p>Network security isn’t just about devices or hardware. It’s about mindsets: the principles guiding your data center security decisions. Set your business apart by adopting lasting mindsets to keep your networks safe. Keeping up with current-day trends, you can stay ahead of the curve.</p><p>To help get you started, we outlined seven mindsets businesses should implement as guiding principles when designing and building a network’s architecture. By creating this in the form of an infographic, all the information is in easy-to-digest chunks, so you don’t have to waste time looking for the pertinent information. Check it out below!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*TLbfZlyVJK1lpjX6.jpg" /></figure><p><em>Originally published at </em><a href="http://sentinelips.com/blog/2015/09/15/infographic-security-mindsets-adopt-today/"><em>sentinelips.com</em></a><em> on September 15, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1bc92ad920d0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Defining DDoS and protecting against it]]></title>
            <link>https://medium.com/@SentinelIPS/defining-ddos-and-protecting-against-it-b6af718bbdaa?source=rss-acb8d295aa1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/b6af718bbdaa</guid>
            <category><![CDATA[ddos]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Sentinel IPS]]></dc:creator>
            <pubDate>Wed, 16 Sep 2015 20:11:33 GMT</pubDate>
            <atom:updated>2015-09-16T20:11:33.637Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*mizsxD1dC9_he2bQ.jpg" /></figure><p>It’s a question we get regularly. “Do you guys protect against DDoS?” The question makes sense. Distributed Denial of Service attacks should be top of mind for business owners and network security professionals. The data bears that out.</p><p>Consider these statistics from a recent study on the state of the Internet by Akamai, one the world’s largest Content Delivery Networks (CDNs). They are comparing numbers from the second quarter of 2014 to the first quarter of 2014.</p><p>Increase in total DDoS attacks from Q1 to Q2 2014: 7.13%</p><p>… What about 2015?</p><p>Increase in total DDoS attacks from Q1 to Q2 2014: 132.42%</p><p>Clearly, DDoS attacks should be a concern. But what is a DDoS attack? Judging by some of our interactions with potential customers, this is something we should take a moment and define.</p><p><strong>Defining DDoS</strong></p><p>Somebody at a trade show we attended once came up to us and the first question out of his mouth was, “Hey, do you stop DDoS?” So we began talking and could tell by the look in his eye that he wasn’t quite following what we were saying. So we asked him a couple follow-up questions, and it ended up that he wasn’t talking about DDoS at all. He was talking about somebody trying to brute force the login on his remote desktop server. That’s definitely a problem, but it’s not DDoS. So what is?</p><p>It’s using hundreds or thousands of devices from across the Internet to flood a network with so much legitimate traffic that it renders parts or all of a network unavailable for a period of time. It fills up the bandwidth, fills up the pipe. So you can’t get traffic out to all the routers and switches and things inside the system start freaking out and you can’t get anything done. It’s really more about downtime than it is anything else.</p><p><strong>Defending against DDoS</strong></p><p>If you feel like you might be the target of a DDoS attack, there are a couple of things that you can do.<br>Make sure your providers are protected. The first thing you need to do is contact your ISP and find out what type of DDoS protection it is that they employ. You will also want to ask how they can help you if you do find yourself under attack.</p><p>If you have public-facing web servers or services, you might also consider cloud-based content delivery networks like <a href="https://www.cloudflare.com/">CloudFlare</a> or <a href="https://www.akamai.com/">Akamai</a>. Also, If you have moved any part of your network to the cloud then you’ll want to contact your cloud services provider to make sure proper protection against DDoS is in place there, too.</p><p><strong>Protect your own network as best you can.</strong></p><p>The hardest thing about protecting against most DDoS attacks is that they use legitimate traffic to do their damage. Sometimes standard protection systems like firewalls, IPSs and IDSs — which are geared toward stopping malicious traffic — aren’t going to be as effective at protection. Still, those protections need to be in place, so make sure they are there, too.</p><p><em>Originally published at </em><a href="http://sentinelips.com/blog/2015/09/10/defining-ddos-and-protecting-against-it/"><em>sentinelips.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b6af718bbdaa" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>