see more

Resources

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! 

Untitled-64

Blog

Jun 16, 2017 Ignite 2017: FireMon to Be a Committed Developer for Palo Alto Networks Application Framework

We had a great show in Vancouver this week for the annual Palo Alto Networks Ignite conference. We always value the time spent in the field where we can hear directly from our customers and others in the industry about the challenges they face in optimizing security for today’s threats and business processes. It’s essential to progressing our solutions.

Read more
Jun 12, 2017 FireMon + Palo Alto Networks: Six New Features that Can Help You Extend Your Next-Generation Security Capabilities
FireMon has committed to delivering advanced analysis and automation tools designed to help users streamline security operations and reduce risk with new features specifically for the Palo Alto Networks Next-Generation Security Platform. The integrations span FireMon’s flagship product Security Manager as well as security analytics platform Immediate Insight.
Read more








Apr 09, 2012

Log Your Accept Traffic

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:

    • It allows you to verify your technology is actually working (confirming that the millions of dollars you spent of your firewall is actually doing something)
    • Identify attacks that failed

    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:

      • Forensics review after a breach is discovered to learn when it started and how long it lasted
      • Threat alerts when known bad actors are SUCCEEDING in accessing resources in your organization
      • Anomaly detection when there is an unexpected spike (or drop) in typical traffic behavior

      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.]

      Events

      Webinars

      Jun 22, 2017 La vida del firewall: administración constante y automatizada del ciclo de vida de las políticas

      El nuevo paradigma de la automatización es la “Administración del Ciclo de Vida”

       

      Te mostraremos cómo FireMon Intelligent Policy Automation utiliza la tecnología de automatización e inteligencia para reducir el esfuerzo e incrementar la eficacia en cada etapa del proceso de cambios.
      View
      Jun 06, 2017 Top 5 Risks of "Dirty" Firewalls
      Firewall rules are notoriously complex and voluminous in nature. Even small organizations have multiple firewalls and significant complexity. But large organizations are overwhelmed.
      View
      Jun 01, 2017 4 Steps to Prepare for the Next WannaCry
      Now that the immediate threat of WannaCry has died down, it is time to take a step-back and analyze the situation to see what we can learn from this attack to better protect ourselves from the next “unknown”.
      View
      May 23, 2017 Der Countdown läuft, noch 365 Tage bis zur DSGVO (GDPR): Machen Sie Ihr Netzwerk fit für Compliance
      Netzwerksicherheit ist deutlich mehr als Cyberbedrohungen nur zu stoppen. Es geht auch darum für das Unvermeidliche gerüstet zu sein. Nämlich einen Datenschutzvorfall, den die Technik allein nicht hat verhindern können. Die EU Datenschutz-Grundverordnung (kurz DSGVO GDPR) ist, neben anderen mehr, ein solches Compliance-Rahmenwerk mit dem Unternehmen sich auseinandersetzen müssen und das im Mai des kommenden Jahres in Kraft tritt. Dann sind Unternehmen beispielsweise verpflichtet innerhalb von 72 Stunden nach einem Datenschutzvorfall darüber zu informieren.
      View

      News

      Jun 07, 2017
      Qakbot malware from 2009 returns, causes Active Directory lockouts
      SC Magazine UK
      Jun 06, 2017
      Botched security: Celebrities, other patients, affected after plastic surgery files are breached and stolen
      SC Magazine
      Jun 06, 2017
      Election cyberattack proves people are still the biggest flaw
      SearchSecurity
      Jun 01, 2017
      250K Photos Leaked in Cosmetic Surgery Extortion Attack
      Info Security
      Jun 01, 2017
      OneLogin Breach Reignites Concerns over Password Managers
      Dark Reading
      Jun 01, 2017
      OneLogin Breach Reignites Concerns over Password Managers
      Dark Reading
      May 29, 2017
      How to manage the Complexity Gap
      IT Pro Portal
      May 26, 2017
      Hackers upgrading malware to 64-bit code to evade detection
      SC Magazine UK
      May 25, 2017
      83 percent of security staff waste time fixing other IT problems
      Betanews
      May 24, 2017
      Unsanctioned Computer Support Costs Companies $88K per Year
      Dark Reading
      May 23, 2017
      WannaCry Successor Is New ‘Doomsday’ SMB Worm That Uses 7 NSA Hacking Tools
      Information Security Buzz
      May 23, 2017
      WannaCry? Not really. A report from the 11th Eskenzi PR IT Analyst and CISO Forum
      Computer Weekly
      May 18, 2017
      Cisco Warns Of Un-Patchable WannaCrypt Vulnerabilities
      Information Security Buzz
      May 16, 2017
      Here comes the cloud...and it's all right
      SC Magazine
      May 15, 2017
      10 ways cyber security will evolve in the face of growing threats
      Information Age
      May 12, 2017
      Managing Complexity Is No. 1 Security Challenge in FireMon’s Annual State of the Firewall Report
      Computing Security
      May 12, 2017
      Sabre Breach
      Information Security Buzz
      May 12, 2017
      FireMon Announces Industry’s First Intelligent Cloud Security Management Solution
      IT Security Guru
      May 12, 2017
      FireMon Releases Third Annual State of the Firewall Report
      Dark Reading
      May 12, 2017
      WikiLeaks drops 'Grasshopper' documents, part four of its CIA Vault 7 files
      Wired
        See all news from 2017



      Resource Library

      Audit Compliance

      Datasheets

      Policy Change

      Solution Briefs

      Policy Change

      White Papers

      Visibility Monitoring Management

      Analyst Reports

      Security Manager
      Overview of FireMon’s Flagship Firewall Management Solution
      Policy Planner
      Overview of FireMon’s Change Automation Solution
      Policy Optimizer
      Overview of FireMon’s Rule Recertification Automation Solution
      Risk Analyzer
      Overview of FireMon’s Attack Simulation and Risk Measurement Solution
      Immediate Insight
      Overview of FireMon’s Immediate Insight Solution
      Intelligent Security Management
      Delivering next-generation security management that boosts productivity and accelerates the agility of business
      Intelligent Policy Automation
      Intelligent Policy Automation: Orchestrating Change Management with Speed and Security.
      Hybrid Cloud Management
      Visibility into and control over Cloud Services, including AWS and OpenStack Platforms
      Accelerated Incident Response
      Immediate Insight in action - Orchestration, automation and analytics for data assembly and discovery
      Change Simulation & Risk Scoring
      Proactively reduce risk based upon network exposure and host accessibility
      2017 State of the Firewall
      Networking continues to evolve, yet the firewall remains critical to securing today’s enterprises. FireMon is proud to present its 3rd Annual State of the Firewall Report
      Firewall Cleanup
      The implications of firewall policy complexity, why it remains a problem today and how to resolve it.
      Real-Time Risk Analysis
      Risk analysis with real-time change configuration is key to managing security risks in your IT infrastructure.
      Real-Time Data Triage
      Our Immediate Insight platform from FireMon can help organizations overcome the limitations and gaps inherent to the current analytic market.
      Bridging the SIEM Alert Triage Gap
      Immediate Insight enables security teams to improve event triage and incident response, extending the value of your existing full-featured SIEM.
      Intelligent Policy Automation
      Automation Isn’t One-Size-Fits-All
      Intelligent Security Management

      Helping Enterprise Security Teams Improve Resource Efficiency & Reduce Overall Risk Exposure

      2016 State of the Firewall
      2nd Annual State of the Firewall Report based on survey of 600 IT security practitioners.
      The Top 5 Myths of Data Breaches
      Five of the biggest myths that exist about data breaches, and explain how and why they occur.
      Firewall Sprawl: Top Four Security Gaps Exposed

      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.

      When You Can't Patch It, Protect It from the Network
      Gartner
      Firewall Sprawl: How Complexity Is Adding Cost & Increasing Risk
      Aberdeen
      Quantifying the value of Intelligent Security Management
      Aberdeen
      Security Analytics Brings Data-Driven Security Into the 21st Century
      Forrester
      Automate Zero Trust Policy And Enforcement
      Forrester
      The Return on Security analysis for FireMon’s Security Manager
      IANS