Compliance
  Governance
  Risk-Management
  Security
Features


< Back

Security : Policy Management : Network :  

Back to Basics: 7 Common Pitfalls of Security Policy Management
May 13, 2015 12:00 PM

By Nimmy Reichenberg
Nimmy Reichenberg
VP Marketing and Strategy
AlgoSec

It’s no surprise to security practitioners that managing security is becoming more and more demanding. We are facing more threats, greater complexity and increased demand for both security and application connectivity. While many companies are deploying the latest and greatest technologies to fight back against cyber-attacks, they often neglect their security policy management basics.

In my years of interactions with companies across pretty much every geography and industry vertical, I’ve found that going “back to the basics” is key when managing an effective security policy and a crucial first step in making your organization more responsive, agile, compliant and secure.

  1. Think about the process first. Even a great technology solution cannot fix a bad process, but it can force you to think about how your process should work. Generally, security teams have a process for adding rules, but very few have a process for removing or recertifying rules, changing objects, and removing IP addresses. Bring your teams together and think about how and when you update or remove rules and objects, and develop a repetitive process for managing these critical and ongoing tasks that you will use Every. Single. Time.
  2. Look through a single pane of glass: When different teams with different goals use different tools and procedures, conflicts and errors occur. The teams tasked with security, operations and applications already have different cultures and reporting structures that they follow. If they also have different degrees of visibility across the network, they are unlikely to agree on overarching goals, ultimately making your entire organization less secure and agile. If everyone is working with the same tools and procedures, they will see the same picture and be able to recognize—and agree on—the current status, risks and opportunities.
  3. Take an application-centric approach: The number one trigger for a policy change is a change to a business application, so you need to think about security from the application perspective. Visually map application flows (using a network topology map) so you can see how data flows across the network, what’s not working and where traffic is blocked. If you focus on the application first and figure out how traffic needs to flow, you can easily understand what each application needs in terms of connectivity to function and deliver its business benefits, while ensuring security.
  4. Proactively assess risk: Once you know what changes are needed, perform ‘what-if’ analysis to make sure that your changes do not add any risk, violate PCI compliance requirements, conflict with your network segmentation strategy, or introduce any new vulnerabilities. With this strategy, you can mitigate risks before policies are implemented and catch major issues before they occur.
  5. Validate and reconcile: Assuming all of your security policy changes are in place, you need to be able to verify that they were actually implemented or see, at a glance, what kept them from being implemented. On the flip side, you also need to be able to quickly identify any out-of-process changes or “cowboy changes” that were snuck in without going through the proper approval process. Relying on manually documented processes will not capture all your out-of-process or dropped changes. Reining in the cowboys will also make it much easier to find potentially risky changes.
  6. Automate everything you can: Automation will streamline your processes, enable you to quickly change designs, identify rules that can be reused, seamlessly push out policies, conduct risk analysis and auditing quickly, instantly create documentation and validate and reconcile, all in real time. There will always be some tasks that require human intervention, but you will have a more secure system if you keep the people on your team focused on the jobs that need analysis and investigation, rather than mundane tasks that can be automated.
  7. And last but not least…don’t forget the security basics: With the advanced threats and well publicized breaches of today, it’s natural for the media and analyst community to disproportionately cover the latest shiny toys. You know, those cloud-based, crowd-sourced, next-generation, advanced kill’em all flux-capacitor powered solutions. But you can greatly improve your security posture by not forgetting, and even emphasizing the security basics that are often overlooked, such as:
  • Updating to the latest Anti-Virus
  • Identifying and patching vulnerabilities
  • Hardening systems
  • Solid processes for configuring policies across firewalls and routers
  • Removing administrator privileges from endpoints
  • Security awareness programs
  • And the list goes on…

 





Nimmy Reichenberg
VP Marketing and Strategy
AlgoSec

Nimmy Reichenberg has over 10 years’ executive marketing and business development experience in enterprise technology. Prior to joining AlgoSec, Mr. Reichenberg served as the VP of Worldwide Marketing and Business Development at NextNine. Previously Mr. Reichenberg held various product management and marketing roles at M-Systems (acquired by SanDisk) and founded the marketing department for the company's enterprise security solutions. Mr. Reichenberg is a frequent speaker at information security events and a regular contributor to industry publications. Mr. Reichenberg has a B.Sc. in Computer Science and an MBA.








About Us Editorial

© 2017 Simplex Knowledge Company. All Rights Reserved.   |   TERMS OF USE  |   PRIVACY POLICY