Skip to content
Organisational controls
ISO 27001A.5.2

ISO 27001 Annex A 5.2 Information security roles and responsibilities

What it says

Information security roles and responsibilities shall be defined and allocated according to the organization needs.

Quoted as published. Everything else on this page is written by Control Stack.

In plain English

Define information security roles and responsibilities and allocate each one according to your organisation's needs, whether as dedicated roles or as duties added to existing jobs.

Your organisation must define information security roles and responsibilities and allocate them according to its needs. Both parts are required:

  • Defined: each role's security responsibilities are spelled out, so people can tell what is theirs and what is someone else's.
  • Allocated: each one is given to someone.

Your organisation's needs decide how the roles are set up. A large organisation may have dedicated security roles, while a small one may add the duties to existing jobs. No job title is prescribed.

Why it matters

When responsibility is unclear, security tasks fall between people: a process nobody runs, or a risk accepted by someone without the authority. Defining and allocating roles gives each task a person who answers for it, so gaps can be seen and closed.

How to implement

  1. List the security responsibilities your organisation actually has.

    Start with what your policies assign (Annex A 5.1). Add protecting information and other assets, running processes such as patching and access reviews, managing risk and accepting what remains, and what everyone using your systems must do (allocated to all users, not one person).

  2. Group the responsibilities into roles and allocate each to a person.

    Record the role, its duties and its holder in a responsibility matrix. Choose people with the knowledge and authority to do the work. In a small organisation, add duties to existing jobs. Keep conflicting duties apart, because Annex A 5.3 requires them to be segregated.

  3. Allocate duties carried out by suppliers too.

    Where a managed service or cloud provider does the work, record the task against that provider and name an internal person accountable for checking it is done. Annex A 5.20 covers the security requirements agreed with each supplier.

  4. Tell each holder what they own and what they can decide.

    Send them the description and state their limits of authority, such as which risks they can accept and which access they can approve. Make clear that anyone who hands a task to someone else stays accountable and checks that it was done.

Keep it running

Reallocate duties as soon as someone holding them leaves or changes job, so nothing sits with an empty position. Look again after a restructure, a new major system or outsourced service, or an incident that exposed unclear ownership.

Evidence and audit

  1. Check 1 of 4What an auditor asks for

    Ask for

    The responsibility matrix, matched to the current staff list and recent leavers and movers.

    Look at

    Whether each holder is still in the organisation and in that job.

    Good evidence

    Every role has a current holder, and no duty still sits with someone who has left or moved on.

  2. Check 2 of 4What an auditor asks for

    Ask for

    A sample of security tasks taken from policies, procedures and the risk register, traced to the matrix and role descriptions.

    Look at

    Whether each task, including risk acceptance and work done by suppliers, is stated against one role, in the matrix or the role's description, rather than falling under a catch-all entry.

    Good evidence

    Each sampled task is stated against a role with a named holder, and outsourced tasks have a named internal person accountable.

  3. Check 3 of 4What an auditor asks for

    Ask for

    Records of recent security work from a sample of role holders, such as a completed access review or a risk acceptance.

    Look at

    Who did or approved the work, compared with who the matrix says holds it.

    Good evidence

    The person who approved each sampled item is the allocated holder, or a delegate whose work the holder checked.

  4. Check 4 of 4What an auditor asks for

    Ask for

    The organisation chart and list of bought services, compared with the matrix.

    Look at

    Whether the roles fit how this organisation really runs, rather than a template with teams or systems it does not have.

    Good evidence

    Each role relates to a team, system or service the organisation really has, and each main system or bought service is covered by a role.

Mappings

Closest match in ASD Information Security Manual: ISM-1997, Board defines cyber security roles across the organisation, which asks for the same thing.

ISO 42001

ISO/IEC 42001: 3 mappings

  • A.3.2AI roles and responsibilitiesPartially overlaps
  • A.4.6Human resourcesPartially overlaps
  • A.10.2Allocating responsibilitiesPartially overlaps
ASD ISM

ASD Information Security Manual: 17 mappings

ASD Essentials

ASD Essentials for enterprise IT: 2 mappings

Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.

Get help with this control

ISO 27001 training

Mindset Cyber, a PECB Authorised Titanium Partner, sells official PECB ISO/IEC 27001 courses that map directly to the controls in this library.