ISO 27001 Annex A 5.2: Information security roles and responsibilities

What auditors look for

Auditors check that 5.2 is either justified as not applicable in your Statement of Applicability or implemented and working. Typical evidence includes:

• RACI or roles document
• Job descriptions with security duties
• Named owners for assets and risks

How to implement 5.2 in practice

1. Name one accountable owner per control
2. Agree ownership with each owner's manager
3. Review assignments when people change roles
4. Name an owner for 5.2, decide how often it runs and file evidence each time, so the control is audit-ready all year.

Recording 5.2 in the Statement of Applicability

List 5.2 with whether it applies, the reason (usually the risks it treats or a legal or contractual requirement), its implementation status and where the evidence lives. If you exclude it, explain why none of your risks or obligations require it.

Free resources

• How to drive security compliance across teams
• ISO 27001 and GDPR readiness assessment
• 10 steps to implement ISO 27001
• Remote ISO 27001 consultant

More organizational controls

• 5.1 Policies for information security
• 5.3 Segregation of duties
• 5.4 Management responsibilities
• 5.5 Contact with authorities
• 5.6 Contact with special interest groups
• 5.7 Threat intelligence
• 5.8 Information security in project management
• 5.9 Inventory of information and other associated assets