Contingency Planning, Incident Response, Reporting, and Quality Control
Preparedness and response
Contingency planning anticipates disruption: equipment failure, loss of secure storage, staff shortage, or a security incident. Plans define triggers, roles, communication, and fallback procedures. Incident response covers immediate action, containment, notification, and preservation of evidence. Reporting of security occurrences must be timely, accurate, and directed to the competent authority as required; under-reporting is itself a security weakness.
Quality control and improvement
Quality control monitors day-to-day performance against standards. Internal audit provides independent, systematic examination of the programme. Corrective action addresses the root cause, not just the symptom, and must be verified for effectiveness. A candidate must understand the difference between an audit finding and a corrective action, and that closure requires evidence.
Traps
Questions often treat a reported incident as a failure of the reporter rather than a control working. Another trap is corrective action that only retrains staff when the root cause was a procedure or equipment defect. A further trap is assuming an audit is complete when findings are listed but not verified as closed.
Rule of thumb
Ask "what is the root cause, and how will we know it is fixed?" If the answer is only "retrain", look again at the system.
Worked example
Repeated seal mismatches are found in audit. Retraining alone is insufficient if the handoff procedure lacks a verification step; the corrective action must change the procedure and then verify that mismatches fall.