About Us | Contact Us
View Cart

Firewall Log Retention: Beyond The Guidance

By Dan Hadaway | Monday, March 26, 2018 - One Comment

In the absence of specific guidance, organizations are left to use their judgement in retaining logs…


Another one of those Dan’s New Leaf Posts, meant to inspire thought about IT Governance . . . .


ServIcons_ITAudit_01

Not long ago a Client asked for my input on their firewall log policy, as they were collecting logs but were unsure about how long they needed to retain them.

Interestingly, we too have still not found exactly how long a bank should retain their firewall logs or, for that matter, other logs. The guidance does require us to collect and analyze logs, but does not specify how long we must keep the logs. Specifically, the FFIEC says this:

“Regardless of the method of log management, management should develop processes to collect, aggregate, analyze, and correlate security information. Policies should define retention periods for security and operational logs.

Just recently we asked two different examiners from two different FFIEC agencies, who need to remain “anonymous*,” how long event logs should be retained. We received these replies:

“To my knowledge, regulatory guidance does not dictate the duration that ‘key event logs’ should be retained. Industry best practice tends to support a one year time horizon, or at least until the area is subject to subsequent independent review/audit.”

and

“That is correct. One year is generally a ‘best practice’ minimum. Some organizations are saving them longer due to the low cost of storage media for potential forensics value.”

Based on this, we believe that from a regulatory standpoint how long you keep logs is up to you, but you should have a method to the madness…and now that the Cybersecurity Assessment Tool is in place you should document what you require.

We think that is a good thing, because if we can not keep logs for some reason, we can carve those logs out in our policy. But we also believe that while the regulators have no definite length of time for retention that logs should be kept, for forensics purposes, indefinitely. We want the ability, in ten years, to prove the context of the environment we’re managing today. That is what logs are for.

Therefore, we store 395 days (a year and one month), and then encourage our Clients to put a copy of the logs in their normal backup system, so that they would be retained “indefinitely.” Yes, by “indefinitely,” we mean “forever.”

So, in summary: the policy should say one year, your requirement from your MSSP should be more than one year, and in practice they should be retained indefinitely.

 

* Neither of these two examiners are in the examination team that completed infotex’ most recent FFIEC examination.


Original article by Dan Hadaway CRISC CISA CISM. Founder and Managing Partner, infotex

Dan’s New Leaf is a fun blog to inspire thought in the area of IT Governance.


same_strip_012513


 

One Response to “Firewall Log Retention: Beyond The Guidance”

Comment from KundaliniArt
Time 03/28/2018 at 11:16 am

Thank you so much!xx

Latest News
    The Four Basic Truths of System Security Webinar-Video The last thirty years have seen an evolution of frameworks, laws, and assessment approaches to information security which can intimidate the management team with their complexity. This webinar will discuss the four basic truths of system security regardless of frameworks or approach, and eight control systems to […]
    Community Banking and their layers of security. . . Michael Hartke’s first post as Executive Vice President! Thinking back to my first talk to security professionals in community banking almost 10 years ago, the question continues to this day. First some background… infotex was moderating the Indiana Bankers Association Security Conference when one of the […]
    Reasons why we should be considered! infotex provides a number of services that can be checked out if you click over to offerings.infotex.com! We even made a movie with all the reasons why infotex should be your next MSOC!  
    infotex and GoTo To all infotex managed security service Clients: As recently reported by major news outlets there was a data breach affecting GoTo (formerly LogMeIn) wherein attackers stole encrypted backups containing customer information in November 2022.  Based on the advisory from GoTo the products they offer that are affected include LogMeIn Pro, LogMeIn Central, […]
    An option for increasing security for ALL organizations. . . The threat landscape is evolving daily, and it is becoming increasingly difficult for even large organizations providing cyber defense services to keep up. As Brandao (2021) notes, it is important for organizations to adapt holistic technologies that can correlate all attack events. Therefore, developing XDR […]
    Another awareness poster for YOUR customers (and users).  Now that we have our own employees aware, maybe it’s time to start posting content for our customers! Check out posters.infotex.com for the whole collection! Download the large versions here: Awareness Poster (Portrait) Awareness Poster (Landscape) You are welcome to print out and distribute this around your […]
    A relic of the internet’s less secure past, many small firms struggle to secure their email systems… An article review. With a great deal of cybersecurity related news focused on new threats and similarly new techniques aimed at combating them, it can be easy to forget some of the older threats that have never gone […]
    Seven Trends . . . …that small bank Information Security Officers face in 2023 Another one of those Dan’s New Leaf Posts, meant to inspire thought about IT Governance . . . . Welcome to the Magnificent Seven, my annual predictive article about the seven trends in technology that will impact the Information Security Officers of […]
    System Security and Cybersecurity are not the same thing. . . Another one of those Dan’s New Leaf Posts, meant to inspire thought about IT Governance . . . . Regarding “information security,” the last thirty years have seen an evolution of frameworks, laws, and assessment approaches which intimidate the management team with their complexity.  […]
    The cryptographic algorithm is vulnerable to attack and is no longer considered secure… An article review. NIST has announced that it plans to retire the SHA-1 cryptographic algorithm by the end of 2030, citing multiple vulnerabilities in the standard, effectively ending its use after nearly 30 years.  Introduced in 1995, SHA-1 used a 160-bit hash […]