liveBook · Manning

Incident response

As explained in AI Governance

Incident response is the organized process for detecting, containing, investigating, remediating, and documenting harmful or unauthorized system events.

When a live AI application suffers a serious failure, incident response prioritizes containment before recovery. section 3.6

Containment and recovery decisions:

  • Restrict access, route affected cases to people, or pause the application while the cause is fixed. section 3.6
  • Repeat the failed test, confirm the fix, and record why the system was allowed to resume. section 3.6

How AI Governance covers it

How deep it goes
Defines containment choices, recovery verification, and restart records, but does not detail root-cause investigation procedures.
Examples
Considers restricting access, routing cases to people, or pausing service, then repeating a failed test before resuming.
What you can do after
Operate a failure workflow by containing service, verifying the fix, and recording the decision to resume.
How it connects
Links containment and recovery with repeat testing, change review, and operational monitoring.

Also explained in

Compare how 5 books explain incident response →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of AI Governance. The section links point to the parts of the book it draws on.