

What is Incident Response Planning for Insurance Agencies?
Incident response planning for an Alabama insurance agency is the written plan § 27-62-4(h) requires for handling a cybersecurity event. It sets who does what once an event is found, because notice to the Commissioner is due within three business days, and § 27-62-5 also requires a prompt investigation and five years of records.
By James Denney, Sales & Marketing Director | Technically reviewed by the AllTech security engineering team | Updated October 15, 2026
This guide is general information, not legal advice. Confirm your obligations with your attorney.
Alabama licensees need a written incident response plan as part of their information security program under § 27-62-4(h) of the Insurance Data Security Law.
Once an event is identified, the clock starts: notice to the Commissioner is due within three business days of determining that a qualifying event occurred.
The law also requires a prompt investigation and five years of records.
An agency that has already named its decision makers and printed its contacts on one page is far better placed to meet those deadlines.
Overview
Incident response planning is the work of deciding, before anything goes wrong, how an insurance agency will recognize, contain, investigate, document, and report a cybersecurity event. For Alabama licensees, the Insurance Data Security Law at Ala. Code Title 27, Chapter 62, calls for a written incident response plan as part of the information security program in § 27-62-4(h). The plan sets out who is in charge, who gets called, what gets written down, and how the agency returns to normal operations.
The plan matters because the law sets firm clocks once an event is identified. Section 27-62-5 requires a prompt investigation and five years of records, and § 27-62-6 requires notice to the Commissioner within three business days of determining that a qualifying event occurred. An agency that has already named its decision makers, gathered its contacts, and printed them on a single page is in a far better position to meet those deadlines than one that starts from scratch on the worst day of the year.
Benefits of Incident Response Planning for Insurance Agencies
It meets the written plan requirement in § 27-62-4(h). A plan built around the seven required elements gives the agency a document it can show the Alabama Department of Insurance on request.
It protects the three business day notice window. Clear roles and a ready contact list keep the agency from losing days deciding who should call whom.
It shortens the life of an incident. The IBM Cost of a Data Breach Report 2025 puts the average time to identify and contain a breach at 241 days, and a practiced plan helps an agency find and contain problems faster.
It keeps investigation records complete from the first hour. A plan that assigns documentation duties produces the five years of records § 27-62-5 requires without a scramble after the fact.
It reduces confusion for staff and clients. When everyone knows their role, the office can keep serving clients and speak with one consistent voice while the event is handled.

How AllTech Delivers
AllTech begins with a short conversation about the agency: who makes decisions, which systems hold client information, which outside vendors are involved, and what the agency already has in writing. From there, AllTech helps the agency build an incident response plan that follows the elements in § 27-62-4(h), including roles, communications, remediation, documentation, and post event review. The plan is written in plain language so an owner or office manager with no internal IT staff can follow it under pressure.
AllTech also helps the agency turn the plan into something usable on the day of an event, including a one page printed contact sheet, a simple documentation template for investigation notes, and a walkthrough with key staff so roles are understood before they are needed. AllTech serves agencies across Alabama, the Florida Panhandle, and South Georgia from offices in Birmingham and Dothan, and can support detection, containment, and recovery when the agency wants ongoing help.
Key Areas Addressed
Incident Response Handbook
A written plan covering the seven § 27-62-4(h) elements, with roles, contacts, and step by step response actions.
Cybersecurity Risk Assessment
A review of threats and safeguards that tells the plan which events are most likely and most damaging.
Advanced Cyber Protections
Monitoring and audit trails that help detect and respond to events, as § 27-62-4(d)(2)(i) contemplates.
Data Backup and Disaster Recovery
Recovery planning that supports restoring systems after an event and protects against technological failures.
Business Data Management
Organized storage of investigation records so the five year retention duty in § 27-62-5 can be met.
Virtual Technology Advisor
Ongoing guidance to review the plan after any event and keep it current as the agency changes.
The AllTech Approach to Incident Response Planning for Insurance Agencies
Build the plan around the statute. Every section of the plan maps to an element of § 27-62-4(h), so nothing required is left out.
Name people, not job titles alone. Each role in the plan has a primary person and a backup, so the response does not stall when someone is out of the office.
Put the essentials on paper. A one page printed contact sheet keeps critical numbers available even when email, phones, or computers are down.
Practice before it counts. A short tabletop walkthrough with key staff shows where the plan is unclear while there is still time to fix it.
Revise after every event. The plan is reviewed and updated after each incident, which is also one of the elements § 27-62-4(h) requires.
Related Services
Insurance Agency IT
Managed technology support built around the systems and workflows insurance agencies use every day.
Cybersecurity as a Service
Continuous security monitoring and management that helps spot events early and supports a faster response.
Managed IT Services
Day to day support, maintenance, and planning for agencies that have no internal IT staff.
About the author
James Denney is the Sales & Marketing Director at AllTech IT Solutions. He has 25+ years in IT, including nearly two decades running IT and operations for wholesale distributors and six years as an AllTech engineer. Every guide is technically reviewed by the AllTech security engineering team.
Frequently Asked Questions
What is incident response planning for an insurance agency?
Incident response planning is the process of writing down, in advance, how an agency will handle a cybersecurity event, from first detection through investigation, notice, recovery, and review. For Alabama licensees, the written incident response plan is part of the information security program required by Ala. Code § 27-62-4(h).
A good plan names the people in charge, lists who to contact, explains what to document, and sets out how the agency will restore normal operations. For the general version of this topic, see What is Incident Response Planning.
Does Alabama law require my agency to have a written incident response plan?
Section 27-62-4(h) requires each licensee subject to § 27-62-4 to establish a written incident response plan as part of its information security program. Licensed agencies and producers generally fall under the law, though some qualify for the small licensee exemption in § 27-62-9.
What must an incident response plan include under § 27-62-4(h)?
The plan must address seven areas: the internal process for responding to a cybersecurity event, the goals of the plan, clear roles, responsibilities, and levels of decision making authority, and external and internal communications and information sharing.
It must also address requirements for remediating identified weaknesses, documentation and reporting of cybersecurity events and response activities, and evaluation and revision of the plan after a cybersecurity event.
If my agency is exempt under § 27-62-9, do I still need a plan?
Section 27-62-9 exempts licensees with fewer than 25 employees, less than $5 million in gross annual revenue, or less than $10 million in year end total assets from § 27-62-4, which includes the written plan requirement. It also covers licensees that comply with HIPAA or the Gramm Leach Bliley Act requirements as the statute describes.
The exemption does not remove the investigation duties in § 27-62-5 or the notice duties in § 27-62-6. Because those deadlines still apply, a short written plan is the most practical way for an exempt agency to be ready.
What does § 27-62-5 require during an investigation?
When an agency learns that a cybersecurity event has or may have occurred, § 27-62-5 requires a prompt investigation. The investigation should determine, as far as possible, whether an event occurred, its nature and scope, and what nonpublic information may have been involved.
The agency must also perform or oversee reasonable measures to restore the security of the affected systems. An outside provider can carry out the investigation, but the agency remains responsible for it.
What if the cybersecurity event happens at one of our vendors?
If an event has or may have occurred in a system maintained by a third party service provider, § 27-62-5 requires the agency to either complete the investigation steps itself or confirm and document that the provider completed them.
This is a common scenario. A SecurityScorecard report released in February 2025 found that 59% of breaches affecting the insurance sector came through third party attack vectors. Vendor contracts should require prompt notice of events so the agency can meet its own deadlines.
When must the agency notify the Alabama Department of Insurance?
Under § 27-62-6, notice to the Commissioner is due as promptly as possible and no later than three business days from the determination that a qualifying cybersecurity event occurred. For a producer whose home state is Alabama, notice applies when the event is reasonably likely to materially harm an Alabama consumer or a material part of normal operations.
Notice is also required when the agency reasonably believes the event involves nonpublic information of 250 or more Alabama consumers and the event must be reported to another government body or is reasonably likely to cause material harm. The three days begin at determination, so the plan should make clear who makes that call.
What information goes in the notice, and do clients need to be told?
The notice asks for as much detail as possible, including the date of the event, how it was discovered, how information was exposed, any third party role, the types of information involved, the number of Alabama consumers affected, remediation steps, and a contact person. The agency must also update the Commissioner as material facts change.
Section 27-62-6 also requires the agency to follow the Alabama Data Breach Notification Act of 2018 where it applies, and to provide the Commissioner a copy of any notice sent to consumers. Keeping a draft notice outline in the plan saves time when it is needed.
What should go on a printed one page incident contact sheet?
As practical guidance, the sheet should list the person who declares an incident and a backup, the IT provider, legal counsel, the insurance carrier or cyber policy claims line, the Alabama Department of Insurance, local law enforcement, and key vendors that hold client data. Each entry should include a name, phone number, and after hours number.
The sheet should also note the three business day notice deadline and the first few steps staff should take. Print copies, keep them in the office and at home for key staff, and review the sheet at least once a year, since an event may take down the email and file systems where digital copies live.
How long must incident records be kept?
Section 27-62-5 requires a licensee to keep records concerning all cybersecurity events for at least five years from the date of the event and to produce them to the Commissioner on demand. Records should cover what happened, what was investigated, and what decisions were made.
Default deletion and recovery windows in Microsoft 365 and SharePoint are measured in days or weeks, not years, unless retention policies are configured, so incident records should be stored deliberately. Separately, the February 15 annual certification under § 27-62-4(i) applies to each insurer domiciled in Alabama.
How much does incident response planning cost for an insurance agency?
Cost depends on scope, including the size of the agency, the number of systems and vendors involved, whether a risk assessment is needed first, and whether the agency wants a staff walkthrough or ongoing response support.
The work is scoped after a short conversation about the agency, so the proposal reflects what the agency actually needs. To start that conversation, contact AllTech in Birmingham or Dothan.
