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
    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! Download the large versions here: Awareness Poster (Portrait) Awareness Poster (Landscape)   You are welcome to print out and distribute this around your office. Interested in one of ours […]
    President Biden recently signed a bill tasking the agency with evaluating the unique risks that schools face… An article review. Taking note of the unique challenges educational institutions face in securing their networks, President Biden has signed a bill into law directing the Cybersecurity and Infrastructure Security Agency (CISA) to look into ways that they can […]
    Thanks for being interested in our Technology Planning Webinars! This year‘s annual update to our annual Technology Planning webinar will include a panel discussion, a review of the previous years’ movies that are already available, and a discussion about alternative tactics that have arisen from recent conferences as well as the impact of the AIO […]
    Welcome Cybersecurity Conference Attendees! Thanks for joining us for the Cybersecurity Conference today! We have created this page for you to have access to the deliverables from Dan’s talk.  
    What you need to know for compliance coast-to-coast. Back in 2020 we posted an article containing links to data breach laws from each state, and it has proven to be one of our more popular posts.  Because laws surrounding the use (and abuse) of technology are always evolving, we thought it was worth taking another […]
    Why It Rhymes With SEEM (And its Not the I Before E Rule) Another one of those Dan’s New Leaf Posts, meant to inspire thought about IT Governance . . . . It’s the Gestalt. The idea that the whole is greater than the sum of it’s parts. That’s not something that is often brought […]
    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! Download the large versions here: Awareness Poster (Portrait) Awareness Poster (Landscape)   You are welcome to print out and distribute this around your office. Interested in one of ours […]
    Questions about China’s new disclosure laws only highlight the uncertainty about disclosure in general… An article review. China recently made waves in the security world by announcing a new set of data security laws, one of which has added new fuel to a long running debate: how and when should security vulnerabilities be disclosed…and to […]
    Four Conditions … …For Why a Network Can be Anything But a Network! Another one of those Dan’s New Leaf Posts, meant to inspire thought about IT Governance . . . . I have to admit that infotex is being called into engineering meetings with larger organizations these days that are NOT community based banks.  We […]