Docy Child

BIZOPS-20 Security Incident Change Management

Estimated reading: 2 minutes 546 views

What is this control about?

Depending on the nature of the incident/violation, a code change may be needed. It is important to track such instances and ensure that the code change follows the existing change management process of approval, code review and deployment to production.

Available tools in the marketplace 

 No tools recommendation 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:

Control implementation

Document in the incident management policy that incidents resulting in code changes follow the change management process

Track such incidents by linking them to the change ticket

Document in the change ticket the origination of the change request

What evidence do auditors look for?

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

  • Provide a recent example of an incident report ticket that includes a link to a change ticket (if applicable)
  • Provide the corresponding change ticket which shows evidence that the code change origination was the incident (if applicable)

Evidence example

From the suggested action above, an example is provided below.

1.    Provide a most recent example of incident report ticket that includes a link to a change ticket  (see incident report example under BIZOPS-8)

2.    Provide the corresponding change ticket which indicates that the origination was the incident.

BIZOPS 20 screenshot1

Join the conversation

Twitter Facebook LinkedIn

❤️  Joyfully crafted by a 100% distributed team.