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
    A Webinar-Movie What are the top seven risks your board should know about in 2022? Since his first board presentation in 2000, when Dan presents audit reports to boards of directors, he also talks to the board about the top risks the institution is facing. Since 2006, Dan has been compiling a list of the […]
    Seven Trends . . . that small bank Information Security Officers face in 2022 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 […]
    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 […]
    Millions of phishing emails will get through automated defenses this year, are your employees ready? An article review. With cybersecurity threats such as cryptocurrency miners and ransomware seeming to dominate the news, it can be easy to forget about older threats such as phishing…but a recent report from cybersecurity firm Tessian reminds us that criminals […]
    The FFIEC’s latest guidance: The Architecture, Infrastructure, and Operations, has brought many changes to exactly how a small financial institution may look at their Technology Planning for 2022. Included in that will be the opportunity to write your first Architecture Plan and we intend to show you what may be involved in that! Have any […]
    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 […]
    Following the contribution, Have I Been Pwned will host more than 800 million compromised credentials… An article review. Have any of your login credentials been revealed in a breach?  If you’re unsure about that, Have I Been Pwned (HIBP) can help you out by letting you check against over 600 million compromised credentials…and with the […]
    infotex and Log4j We are keeping our Clients’ safety in mind. To all infotex managed security service Clients: On Friday December 10th, infotex became aware of a zero-day vulnerability in the Apache Log4j library that allows unauthenticated remote code execution. We began incident response and took steps to proactively disable potentially vulnerable applications until 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 […]