What does a cyber application ask about incident response?
Incident response appears on 26 application questions across 17 of the 48 carrier forms. Each question below is verbatim, with the control it reaches and the evidence to have on file. This page never says what a carrier will accept: that is the carrier's underwriting decision.
The questions, verbatim and mapped
Application question Do you have an incident response plan for network intrusions and malware incidents?
- ISO 27001:2022 A.5.24: Information security incident management planning and preparation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.25: Assessment and decision on information security events. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.26: Response to information security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.3: Evaluating security events to identify incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.4: Responding to security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.MA-01: The incident response plan is executed in coordination with relevant third parties once an incident is declared. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.CO-02: Internal and external stakeholders are notified of incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 23: Detect and respond to incidents promptly. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 25: Response plan content: stages and escalation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
Application question Do you have a written incident response plan in the event that Personally Identifiable Information is/may be compromised?
- ISO 27001:2022 A.5.24: Information security incident management planning and preparation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.25: Assessment and decision on information security events. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.26: Response to information security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.3: Evaluating security events to identify incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.4: Responding to security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.MA-01: The incident response plan is executed in coordination with relevant third parties once an incident is declared. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.CO-02: Internal and external stakeholders are notified of incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 23: Detect and respond to incidents promptly. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 25: Response plan content: stages and escalation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
Application question Does the Applicant have a written incident response plan?
- ISO 27001:2022 A.5.24: Information security incident management planning and preparation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.25: Assessment and decision on information security events. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.26: Response to information security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.3: Evaluating security events to identify incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.4: Responding to security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.MA-01: The incident response plan is executed in coordination with relevant third parties once an incident is declared. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.CO-02: Internal and external stakeholders are notified of incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 23: Detect and respond to incidents promptly. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 25: Response plan content: stages and escalation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
Application question Are copies of the business continuity/disaster recovery and incident response plans stored so that they will be accessible if the Applicant's network became completely unavailable?
- ISO 27001:2022 A.5.29: Information security during disruption. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- ISO 27001:2022 A.5.30: ICT readiness for business continuity. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- SOC 2 CC9.1: Mitigating risks of business disruption. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- SOC 2 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- NIST CSF 2.0 PR.IR-03: Mechanisms are implemented to achieve resilience requirements in normal and adverse situations. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- NIST CSF 2.0 RC.RP-01: The recovery portion of the incident response plan is executed once initiated from the incident response process. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 23: Detect and respond to incidents promptly. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 25: Response plan content: stages and escalation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- CIS Controls v8 11.1: Establish and Maintain a Data Recovery Process. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- CIS Controls v8 11.5: Test Data Recovery. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
Application question Does the organization have an incident response plan - tested and in-effect - setting forth specific action items and responsibilities for relevant parties in the event of a cyber incident or data breach matter?
- ISO 27001:2022 A.5.29: Information security during disruption. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- ISO 27001:2022 A.5.30: ICT readiness for business continuity. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- SOC 2 CC9.1: Mitigating risks of business disruption. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- SOC 2 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- NIST CSF 2.0 PR.IR-03: Mechanisms are implemented to achieve resilience requirements in normal and adverse situations. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- NIST CSF 2.0 RC.RP-01: The recovery portion of the incident response plan is executed once initiated from the incident response process. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 23: Detect and respond to incidents promptly. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 25: Response plan content: stages and escalation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- CIS Controls v8 11.1: Establish and Maintain a Data Recovery Process. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- CIS Controls v8 11.5: Test Data Recovery. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
Application question Do all applicants have a Cyber Incident Response Plan or Business Continuity plan in place to respond to a computer system disruption?
- ISO 27001:2022 A.5.29: Information security during disruption. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- ISO 27001:2022 A.5.30: ICT readiness for business continuity. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- SOC 2 CC9.1: Mitigating risks of business disruption. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- SOC 2 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- NIST CSF 2.0 PR.IR-03: Mechanisms are implemented to achieve resilience requirements in normal and adverse situations. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- NIST CSF 2.0 RC.RP-01: The recovery portion of the incident response plan is executed once initiated from the incident response process. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 23: Detect and respond to incidents promptly. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 25: Response plan content: stages and escalation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- CIS Controls v8 11.1: Establish and Maintain a Data Recovery Process. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- CIS Controls v8 11.5: Test Data Recovery. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
Application question If yes, how often is the Cyber Incident Response or Business Continuity plan tested?
- ISO 27001:2022 A.5.29: Information security during disruption. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- ISO 27001:2022 A.5.30: ICT readiness for business continuity. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- SOC 2 CC9.1: Mitigating risks of business disruption. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- SOC 2 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- NIST CSF 2.0 PR.IR-03: Mechanisms are implemented to achieve resilience requirements in normal and adverse situations. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- NIST CSF 2.0 RC.RP-01: The recovery portion of the incident response plan is executed once initiated from the incident response process. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 23: Detect and respond to incidents promptly. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 25: Response plan content: stages and escalation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- CIS Controls v8 11.1: Establish and Maintain a Data Recovery Process. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- CIS Controls v8 11.5: Test Data Recovery. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
Application question Does the firm have a documented Incident Response Plan?
- ISO 27001:2022 A.5.24: Information security incident management planning and preparation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.25: Assessment and decision on information security events. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.26: Response to information security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.3: Evaluating security events to identify incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.4: Responding to security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.MA-01: The incident response plan is executed in coordination with relevant third parties once an incident is declared. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.CO-02: Internal and external stakeholders are notified of incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 23: Detect and respond to incidents promptly. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 25: Response plan content: stages and escalation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
Application question If "Yes", have any table top exercises for the Incident Response Plan been conducted in the last 24 months?
- ISO 27001:2022 A.5.24: Information security incident management planning and preparation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.25: Assessment and decision on information security events. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.26: Response to information security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.3: Evaluating security events to identify incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.4: Responding to security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.MA-01: The incident response plan is executed in coordination with relevant third parties once an incident is declared. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.CO-02: Internal and external stakeholders are notified of incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 23: Detect and respond to incidents promptly. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 25: Response plan content: stages and escalation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
Application question Do you have an information security incident response plan?
- ISO 27001:2022 A.5.24: Information security incident management planning and preparation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.25: Assessment and decision on information security events. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.26: Response to information security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.3: Evaluating security events to identify incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.4: Responding to security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.MA-01: The incident response plan is executed in coordination with relevant third parties once an incident is declared. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.CO-02: Internal and external stakeholders are notified of incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 23: Detect and respond to incidents promptly. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 25: Response plan content: stages and escalation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
Application question Do you have an incident response or digital forensic outsourcing retainer agreement in place?
- ISO 27001:2022 A.5.24: Information security incident management planning and preparation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.25: Assessment and decision on information security events. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.26: Response to information security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.3: Evaluating security events to identify incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.4: Responding to security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.MA-01: The incident response plan is executed in coordination with relevant third parties once an incident is declared. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.CO-02: Internal and external stakeholders are notified of incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 23: Detect and respond to incidents promptly. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 25: Response plan content: stages and escalation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
Application question A document incident response plan is in place.
- ISO 27001:2022 A.5.24: Information security incident management planning and preparation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.25: Assessment and decision on information security events. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.26: Response to information security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.3: Evaluating security events to identify incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.4: Responding to security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.MA-01: The incident response plan is executed in coordination with relevant third parties once an incident is declared. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.CO-02: Internal and external stakeholders are notified of incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 23: Detect and respond to incidents promptly. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 25: Response plan content: stages and escalation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
Application question There is an incident response plan documented with specific focus on Cyber incident management.
- ISO 27001:2022 A.5.24: Information security incident management planning and preparation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.25: Assessment and decision on information security events. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.26: Response to information security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.3: Evaluating security events to identify incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.4: Responding to security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.MA-01: The incident response plan is executed in coordination with relevant third parties once an incident is declared. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.CO-02: Internal and external stakeholders are notified of incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 23: Detect and respond to incidents promptly. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 25: Response plan content: stages and escalation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
Application question There is an endpoint threat detection and response (ETDR or EDR) tool in place, which does the following: monitors for threat indicators; identifies patterns which match known threats; automatically responds by removing or containing threats; alerts security personnel of incidents; provides forensic and analysis capabilities to allow analysts to perform threat hunting activities.
- ISO 27001:2022 A.5.24: Information security incident management planning and preparation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.25: Assessment and decision on information security events. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.26: Response to information security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.3: Evaluating security events to identify incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.4: Responding to security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.MA-01: The incident response plan is executed in coordination with relevant third parties once an incident is declared. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.CO-02: Internal and external stakeholders are notified of incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 23: Detect and respond to incidents promptly. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 25: Response plan content: stages and escalation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- CIS Controls v8 8.2: Collect Audit Logs. Evidence to have on file: the logging configuration and the sources collected, with their retention; a sample of a security alert and how it was triaged.
- CIS Controls v8 8.9: Centralize Audit Logs. Evidence to have on file: the logging configuration and the sources collected, with their retention; a sample of a security alert and how it was triaged.
- CIS Controls v8 8.11: Conduct Audit Log Reviews. Evidence to have on file: the logging configuration and the sources collected, with their retention; a sample of a security alert and how it was triaged.
- PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- PCI DSS 4.0 Requirement 10: Log and Monitor All Access to System Components and Cardholder Data. Evidence to have on file: the logging configuration and the sources collected, with their retention; a sample of a security alert and how it was triaged.
Application question Please tick below to indicate which of the following the applicant has in place? Business Continuity Planning, Incident response plan, Disaster recovery plan
- ISO 27001:2022 A.5.29: Information security during disruption. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- ISO 27001:2022 A.5.30: ICT readiness for business continuity. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- SOC 2 CC9.1: Mitigating risks of business disruption. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- SOC 2 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- NIST CSF 2.0 PR.IR-03: Mechanisms are implemented to achieve resilience requirements in normal and adverse situations. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- NIST CSF 2.0 RC.RP-01: The recovery portion of the incident response plan is executed once initiated from the incident response process. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 23: Detect and respond to incidents promptly. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 25: Response plan content: stages and escalation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- CIS Controls v8 11.1: Establish and Maintain a Data Recovery Process. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- CIS Controls v8 11.5: Test Data Recovery. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
Application question Does the Applicant currently have an incident response plan in place?
- ISO 27001:2022 A.5.24: Information security incident management planning and preparation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.25: Assessment and decision on information security events. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.26: Response to information security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.3: Evaluating security events to identify incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.4: Responding to security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.MA-01: The incident response plan is executed in coordination with relevant third parties once an incident is declared. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.CO-02: Internal and external stakeholders are notified of incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 23: Detect and respond to incidents promptly. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 25: Response plan content: stages and escalation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
Application question Does the Applicant have an incident response plan dealing with network unauthorized access or computer viruses?
- ISO 27001:2022 A.5.24: Information security incident management planning and preparation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.25: Assessment and decision on information security events. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.26: Response to information security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.3: Evaluating security events to identify incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.4: Responding to security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.MA-01: The incident response plan is executed in coordination with relevant third parties once an incident is declared. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.CO-02: Internal and external stakeholders are notified of incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 23: Detect and respond to incidents promptly. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 25: Response plan content: stages and escalation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
Application question Do you have an incident response plan or business continuity plan in place? If yes, is it tested at least annually?
- ISO 27001:2022 A.5.29: Information security during disruption. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- ISO 27001:2022 A.5.30: ICT readiness for business continuity. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- SOC 2 CC9.1: Mitigating risks of business disruption. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- SOC 2 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- NIST CSF 2.0 PR.IR-03: Mechanisms are implemented to achieve resilience requirements in normal and adverse situations. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- NIST CSF 2.0 RC.RP-01: The recovery portion of the incident response plan is executed once initiated from the incident response process. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 23: Detect and respond to incidents promptly. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 25: Response plan content: stages and escalation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- CIS Controls v8 11.1: Establish and Maintain a Data Recovery Process. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- CIS Controls v8 11.5: Test Data Recovery. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
Application question Do you have an incident response plan or other processes for responding to a cyber security incident?
- ISO 27001:2022 A.5.24: Information security incident management planning and preparation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.25: Assessment and decision on information security events. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.26: Response to information security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.3: Evaluating security events to identify incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.4: Responding to security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.MA-01: The incident response plan is executed in coordination with relevant third parties once an incident is declared. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.CO-02: Internal and external stakeholders are notified of incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 23: Detect and respond to incidents promptly. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 25: Response plan content: stages and escalation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
Application question Has the incident response plan been tested in the last 12 months?
- ISO 27001:2022 A.5.29: Information security during disruption. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- ISO 27001:2022 A.5.30: ICT readiness for business continuity. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- SOC 2 CC9.1: Mitigating risks of business disruption. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- SOC 2 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- NIST CSF 2.0 PR.IR-03: Mechanisms are implemented to achieve resilience requirements in normal and adverse situations. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- NIST CSF 2.0 RC.RP-01: The recovery portion of the incident response plan is executed once initiated from the incident response process. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 23: Detect and respond to incidents promptly. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 25: Response plan content: stages and escalation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- CIS Controls v8 11.1: Establish and Maintain a Data Recovery Process. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- CIS Controls v8 11.5: Test Data Recovery. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
Application question Do you have a disaster recovery plan and/or incident response plan that takes account of loss of functionality/data as a result of a hack, including provision to notify those affected if their personal data is compromised?
- ISO 27001:2022 A.5.29: Information security during disruption. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- ISO 27001:2022 A.5.30: ICT readiness for business continuity. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- ISO 27001:2022 A.8.14: Redundancy of information processing facilities. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- SOC 2 CC9.1: Mitigating risks of business disruption. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- SOC 2 A1.2: Environmental protection, backup and recovery infrastructure. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- NIST CSF 2.0 PR.IR-03: Mechanisms are implemented to achieve resilience requirements in normal and adverse situations. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- NIST CSF 2.0 RC.RP-01: The recovery portion of the incident response plan is executed once initiated from the incident response process. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- ACSC Essential Eight BACKUP: Regular backups. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- APRA CPS 234 para 23: Detect and respond to incidents promptly. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 25: Response plan content: stages and escalation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- CIS Controls v8 11.1: Establish and Maintain a Data Recovery Process. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- CIS Controls v8 11.5: Test Data Recovery. Evidence to have on file: the business-continuity or disaster-recovery plan with its recovery objectives; the record of the last test or exercise, with the date and the outcome.
- PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
Application question Do you have an incident response plan (for cyber attacks and data breaches) that identifies an incident response team?
- ISO 27001:2022 A.5.24: Information security incident management planning and preparation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.25: Assessment and decision on information security events. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.26: Response to information security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.3: Evaluating security events to identify incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.4: Responding to security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.MA-01: The incident response plan is executed in coordination with relevant third parties once an incident is declared. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.CO-02: Internal and external stakeholders are notified of incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 23: Detect and respond to incidents promptly. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 25: Response plan content: stages and escalation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
Application question Does the Applicant have an incident response plan for data breaches, network intrusions and virus incidents?
- ISO 27001:2022 A.5.24: Information security incident management planning and preparation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.25: Assessment and decision on information security events. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.26: Response to information security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.3: Evaluating security events to identify incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.4: Responding to security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.MA-01: The incident response plan is executed in coordination with relevant third parties once an incident is declared. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.CO-02: Internal and external stakeholders are notified of incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 23: Detect and respond to incidents promptly. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 25: Response plan content: stages and escalation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
Application question Does the applicant have a written data breach response plan in place?
- ISO 27001:2022 A.5.24: Information security incident management planning and preparation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.25: Assessment and decision on information security events. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.26: Response to information security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.3: Evaluating security events to identify incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.4: Responding to security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.MA-01: The incident response plan is executed in coordination with relevant third parties once an incident is declared. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.CO-02: Internal and external stakeholders are notified of incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 23: Detect and respond to incidents promptly. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 25: Response plan content: stages and escalation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
Application question Does the Applicant have a data breach response plan in place in the event of a security breach or system failure?
- ISO 27001:2022 A.5.24: Information security incident management planning and preparation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.25: Assessment and decision on information security events. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.26: Response to information security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.3: Evaluating security events to identify incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.4: Responding to security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.MA-01: The incident response plan is executed in coordination with relevant third parties once an incident is declared. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.CO-02: Internal and external stakeholders are notified of incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 23: Detect and respond to incidents promptly. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 25: Response plan content: stages and escalation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
Application question Does the Proposer have an incident response plan for network intrusions and virus incidents?
- ISO 27001:2022 A.5.24: Information security incident management planning and preparation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.25: Assessment and decision on information security events. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- ISO 27001:2022 A.5.26: Response to information security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.3: Evaluating security events to identify incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- SOC 2 CC7.4: Responding to security incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.MA-01: The incident response plan is executed in coordination with relevant third parties once an incident is declared. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- NIST CSF 2.0 RS.CO-02: Internal and external stakeholders are notified of incidents. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 23: Detect and respond to incidents promptly. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 24: Maintain information security response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 25: Response plan content: stages and escalation. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- APRA CPS 234 para 26: Annual review and testing of response plans. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
- PCI DSS 4.0 Requirement 12: Support Information Security with Organizational Policies and Programs. Evidence to have on file: the incident-response plan and its contact or escalation list; the record of the last tabletop exercise or plan test, with the date.
Frequently asked questions
How many carriers ask about incident response?
17 of the 48 carrier forms ask about incident response, on 26 questions.
Do the forms ask whether the plan was tested?
Several do, and testing is a control question, not a loss-history line. The questions on this page show which forms ask about the plan and which ask whether it was tested.
All answer pages: the answers index. The controls each question reaches: the controls index. Map your own answers in the tool.