Cookies on this site. Help us understand what works and improve your experience. Essential cookies keep the site working. With your permission, our visit insights and Google Analytics measure usage, and Google Ads measures advertising. Optional cookies are not required to use the free kit. Change your choice anytime in Cookie settings. Privacy policyCookie policy
A.5.2 Information security roles and responsibilities
Not mandatory by default – decided in your SoA
What it means in plain language
Define and assign who is responsible for which security tasks, so nothing falls between the cracks.
Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.
Why this control matters
Undefined responsibilities often create gaps between policy intent and operational action. Teams should assign named owners, deputies, and approval authorities for recurring security tasks, then keep those assignments aligned to job descriptions, RACI matrices, and onboarding materials. Remember that role clarity is not just organizational theory; it affects incident response, access reviews, backup checks, and risk ownership.
Common auditor findings to check for
Potential gaps to test in your own environment, not a claim about observed audit frequency.
A task was expected to be performed, but no named owner existed, so the activity was delayed or missed during routine operations or an incident.
The same security duty appeared in several job descriptions without a clear primary decision-maker, creating inconsistent approvals and duplicated effort.
Role assignments were not updated after reorganizations or staff changes, leaving obsolete names in documents and no evidence of interim delegation.
How you can implement it
Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.
Define a small but complete set of security roles: ISMS lead, asset owner, risk owner, incident coordinator, access approver, backup verifier, and system administrator. Record each role’s decision rights, deputies, escalation path, and required competence in the Information Security Roles & Responsibilities template.
Map security duties into job descriptions and onboarding packs so accountability survives staff turnover. A manager should confirm that each employee understands the responsibilities attached to their role, especially where duties involve privileged actions, incident reporting, or handling personal data.
Use a RACI matrix for operational processes such as onboarding, access review, backup review, vulnerability remediation, supplier approval, and incident handling. The matrix should identify who does the work, who approves, who is consulted, and who is informed, preventing overlap or silence.
Review assignments after organizational change, major incidents, audit findings, or when a role holder leaves. Capture delegation decisions, temporary cover, and handover notes so there is no gap between outgoing and incoming accountability.
What an auditor will ask to see
Completed roles and responsibilities template with named role holders, deputies, and escalation contacts.
Job descriptions or appointment letters containing specific security responsibilities.
RACI matrix for incidents, access reviews, backups, or risk treatment tasks.
Handover note or organization-change update showing revised ownership after staffing or structure changes.
Baseline documents in the kit
These free kit documents help you document or evidence A.5.2. Each one is tailored to your organization when you build your kit.
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.
Get these documents tailored to your organization
109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.