Get to know us better! Gain valuable insights into how we think by visiting our blog, or take a look at the industry events we're frequenting on our events page. You can also geek out with us by attending one of our security management webinars, or dive head first into the products and solutions we provide in our Resource Library. There's lots to keep you busy!
My years of experience managing security programs, across a broad spectrum of industries, has given me a greater understanding of how technology and people both play a critical role in influencing the overall security posture of any organization.
I was watching a video from Cloud Passage earlier today about their new Beta for Windows Firewall management: Halo for Windows. I don't mean to take anything away from their work and I think it is a good new offering. But something jumped out at me near the end of the video that the administrator in the video only chose to log drops. Why just the dropped traffic?
I hear this fairly frequently from people that choose to only log drop traffic, since it represent the bad traffic and they can send these logs to their SIEM to get alerts on these dropped connections. Particularly when performance of logging is a concern and administrators want to reduce the performance impact by reducing their logging, they will turn logging off on highly utilized rules where they *know* what traffic is flowing through those rules. But, they continue to log ALL their dropped traffic. This is completely wrong.
Logging dropped packets does two positive things for you:
I don't dismiss there is some value in #2, to build up a repository of threats. And, it can aid in discovering malware inside your network and a few other good uses. For this reason, I still strongly encourage logging many drop rules. But remember, this traffic FAILED. The preventative technology (firewall, IPS, etc) succeeded. As for the first case, if you don't trust the technology, don't buy it. And certainly don't use this count like a scoreboard of security success. The fact that you successfully blocked traffic is not proof of security...no matter how many things you drop. This is not a security success metric!
Instead, if you care about security, you should be logging your accepts. This is the traffic that can represent an actual risk to your organization. This is the traffic that successfully passes through your security defenses. There is a ton of value in this data:
This attitude to log all dropped traffic has been promoted by just about everyone. Starting with the firewall and IDS vendors, who want to show value by logging dropped traffic (look, see, I dropped another attack!). And it is promoted by standards that say almost nothing about what a firewall policy should or should not do, but will nearly always include a recommendation to include a clean up rule and LOG it. I don't disagree with logging cleanup rules. But this is not nearly as important as logging successful access. In the case of the drop, you already succeeding in thwarting the attack, the log is of little additional value. In the case of an accept, it is worthy of some additional scrutiny.
My suggestion...log all accepted traffic and reassess which drop rules you want to log.
[NOTE: in the Halo example above, since it is a host-based firewall, there can be limited value in logging the http accepts to the local web server since the web server should be logging connections as well. This video just happened to get me thinking about this topic this morning.]
So you’ve purchased a new firewall. Now what?
You’ve got to decide which access is allowed, which isn’t allowed and whether or not rules are compliant with internal and regulatory standards.
Things are running along smoothly and then the dreaded “change.” A user submits a new access request and the fun begins. Is this access necessary? Safe? Compliant? And what happens when it’s time to retire unused rules?
How Effective Security Management Can Help Teams Cover the Exponentially Increasing Gap between Technology & the Resources Available to Manage It
Security teams today are under tremendous pressure due to the rising frequency and impact of breaches and a business that wants to move faster and faster. The answer to both of these challenges has always been to add more technology and staff resources.
However, each new technology added creates complexity. More rules are created and more data is generated. As networks continue to evolve, this complexity will only grow. And while staff resources may increase, they will never match the exponential growth of technology.
FireMon calls this phenomenon The Complexity Gap and has set out to help security teams close it.
Join us for this webinar with Frost & Sullivan where we’ll explore the causes of “The Gap” and how workforce multipliers such as intelligence and automation help staff manage their security more efficiently and more effectively.
En la actualidad, uno de los retos principales es preparar las redes de seguridad, no sólo para enfrentar las amenazas, sino también para enfrentar los cumplimientos. El día 26 de enero se publicó en el Diario Oficial la LEY GENERAL DE PROTECCIÓN DE DATOS PERSONALES EN POSESIÓN DE SUJETOS OBLIGADOS.
¿Está tu red preparada?
¿Cuentas con los procesos necesarios para el cumplimiento?
En esta era digital los datos personales de nuestros clientes y proveedores pasan por una red y se almacenan en una base de datos. Éstos, por ley, deben protegerse por medio de sistemas y procesos. Uno de los objetivos de esta ley es establecer las condiciones de tratamiento de datos personales y fomentar la cultura de protección.
La Ley de protección de datos es mucho más que un simple aviso de privacidad; esta ley describe derechos y obligaciones que de incumplirse pueden ser penalizados. Asiste a este Webinar para conocer más y prepararte. Te mostraremos:
In the fall of 2016, we sought the answer to a very simple question: What benefits do users who have a firewall management tool deployed with their firewalls see over nonusers? To find out, we commissioned Forrester Consulting to survey 188 IT security decision makers.
In their study, “Automate Zero Trust Policy & Enforcement,” Forrester Consulting found that organizations with firewall auditing and configuration tools realize more benefits that those without, including:
In this webinar, guest Speaker Josh Zelonis, Senior Analyst with Forrester, will review and discuss the results of the study with FireMon CTO Paul Calatayud who will bring his own experiences and best practices for deploying firewall management tools to improve productivity and reduce risk.
Helping Enterprise Security Teams Improve Resource Efficiency & Reduce Overall Risk Exposure
Firewall technology has come a long way since its initial, most rudimentary forms. Next-Generation Firewalls (NGFW) are the latest development, and organizations are accelerating adoption to the new technology. But NGFWs aren’t a fix-all solution.