A.5 Organizational controls
Know which authorities to contact (police, data protection authority, CERT, regulator) and keep the contacts up to date, so you can react quickly in an incident.
During an incident, hesitation over who to call can waste the response window and complicate legal duties. Teams should maintain a current list of authorities such as police, national CERT, and the relevant data protection authority, while defining who is allowed to contact them, under what circumstances, and what information may be shared. The Legal & Regulatory Requirements Register should anchor jurisdiction-specific obligations and notification triggers.
Potential gaps to test in your own environment, not a claim about observed audit frequency.
Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.
These free kit documents help you document or evidence A.5.5. Each one is tailored to your organization when you build your kit.
Review the dependencies with A.5.24 — Information security incident management planning and preparation and A.5.31 — Legal, statutory, regulatory and contractual requirements. Keep the ownership and evidence consistent across these activities.
Required information and the kit’s 19-document core for the wider implementation context.
Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.
For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.
109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.
Start freePlain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.