BIZOPS-8 Security Incident Testing

What is BIZOPS-8 Security Incident Testing Control about?

A security incident testing process should identify and list all possible violations and ways to detect them. 

The most common reason for the lack of incidents is that they are never identified. You can have many security policy violations occurring each day, but if you don’t have a way of identifying them, you will never know. It is recommended to test the whole incident reporting, analysis, and remediation process at least once a year in order to identify any inefficiencies and improve the process.

Available tools in the marketplace

Tools

No tool recommendations are made for this section.

Available templates

TrustCloud has a curated list of templates, internally or externally sourced, to help you get started. Click on the link for a downloadable version:

• TrustCloud incident report template

Control implementation

To implement this control, 

If there was no incident during the year,

• Define and document a test plan to gauge the effectiveness of the incident management plan.
• Designate a team or personnel responsible for testing the incident response plan.
• Choose a day to perform the test and document the process in a ticketing system.

If there was an incident, simply ensure there is a process to document and remediate it.

What evidence do auditors look for?

Most auditors, at a minimum, are looking for the below-suggested action:

1. (in case there was an incident) Provide the incident response testing ticket documenting the identification, analysis, and resolution.

Evidence example

For the suggested action, an example is provided below:

1. Provide the incident response testing ticket documenting the identification, analysis, and resolution.
   The following screenshot shows the ticket created to document the incident.