About Us | Contact Us
View Cart

Incident Response Boilerplate Update

By Adam Reynolds | Monday, October 15, 2018 - Leave a Comment

We have recently made a significant change to our Incident Response Policy regarding Disclosure Incidents.


At infotex we are always revising and updating our boilerplates. We have recently made a significant change to our Incident Response Policy regarding Disclosure Incidents. It is of course very important to comply with all applicable laws and regulations, but understanding which of these you are required to comply with, and when compliance is necessary, will prevent undue burden on your institution. We want our policy to queue up that financial institutions do not have to comply with state law if their policy requires them to comply with federal law (such as FDIC’s Financial Institution Letter 27-2005, the OCC Supervisor Letter 2005-13, SR 05-23 / CA 05-10 for Federal Reserve banks, and NCUA Rules and Regulation 748 Appendix B for NCUA institutions).  This will get you out of a lot of busy work required by the state if you don’t need the help of law enforcement.

If you DO need law enforcement’s help, they will ask you to hit on certain parts of state law.  (Usually notifying the State Attorney General’s office.)  And there may be other reasons you should comply with state law that arise out of the unpredictable incident itself.

Thus, our boilerplate USED to say:

  • Disclosure Incidents:  These are incidents which, because of some statute or regulation, require [name of financial institution] to notify customers, law enforcement, examiners, or the board of directors.  The [Incident Response Team (IRT) / IRT / Technology Steering Committee / Disaster Recovery Team] must comply with all applicable laws and regulations, including state laws such as [Indiana Code 24-4.9 / applicable law in your state] and federal regulations such as the [FDIC’s Financial Institution Letter 27-2005, the OCC Supervisor Letter 2005-13, SR 05-23 / CA 05-10 for Federal Reserve banks, and NCUA Rules and Regulation 748 Appendix B for NCUA institutions —> the FFIEC’s Interagency Guidance on Response Programs for Unauthorized Access to Customer Information and Customer Notice] and/or any other applicable guidance or regulations as they are developed.

However, we feel this can be interpreted to mean that you are REQUIRED to comply with state law.  Not so.

In the newest version of our boilerplate, we have changed our wording to reflect that while federal regulations regarding disclosure incidents should always be followed, state regulations should only be addressed when absolutely necessary.  The new language is as follows:

  • Disclosure Incidents:  These are incidents which, because of some statute or regulation, require [name of financial institution] to notify customers, law enforcement, examiners, or the board of directors.  The [Incident Response Team (IRT) / IRT / Technology Steering Committee / Disaster Recovery Team] must comply with all applicable laws and regulations, including (only when absolutely necessary) the state laws such as [Indiana Code 24-4.9 / applicable law in your state] and always including federal regulations such as the [FDIC’s Financial Institution Letter 27-2005, the OCC Supervisor Letter 2005-13, SR 05-23 / CA 05-10 for Federal Reserve banks, and NCUA Rules and Regulation 748 Appendix B for NCUA institutions —> the FFIEC’s Interagency Guidance on Response Programs for Unauthorized Access to Customer Information and Customer Notice] and/or any other applicable guidance or regulations as they are developed.

Please note that we have passed our interpretation of this issue on to our own attorneys, who have agreed that we are interpreting it correctly, with one all-caps stipulation:  THE BANK STILL HAS TO COMPLY WITH FEDERAL GUIDANCE.  (To which we said, hey, they’re banks, of course they will comply with the federal guidance!!)


Adam Reynolds is a Staff Auditor at infotex.


same_strip_012513


 

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 […]
    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 […]
    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 […]
    If Zero days need Zero clicks, are there any secure devices in the mix? Tanvee Dhir explores the Pegasus spyware. Another technical post, meant to inspire thought about IT Governance . . . . Introduction Over the past couple of weeks, we have seen multiple stories regarding a powerful piece of spyware called Pegasus sold […]
    Our Lead Non-Technical Auditor takes a look at the new AIO Guidance… Architecture, Infrastructure, and Operations (AIO) is the latest booklet released by the Federal Financial Institutions Examination Council (FFIEC) in their line of  IT Examination Handbooks. It is an update to their 2004 Operations booklet and, as the name implies, expands into the areas […]
    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 […]
    Many organizations still fail to consider the unique risks posed by cloud computing… An article review. Last month thousands of Western Digital MyCloud device owners learned about the risks of cloud-based solutions the hard way: their data had been wiped remotely due to a flaw in the internet-facing component of their external hard drives. While […]
    infotex does not use Kaseya… We are protecting our Clients! Another blog post meant to inspire thought about IT Governance . . . . To all infotex managed security service Clients: As you may be aware there was a large ransomware attack recently that leveraged a remote management tool called Kaseya that is used by many […]
    While we’re not a news service, we often use current events to comment on trends and our services. This blog is intended to get people thinking about topics and trends in Technology Risk Management, through our article reviews, as well as through original blog articles about current events and our MSSP services (such as our […]