Skip to content
Organisational controls
ISO 27001A.5.4

ISO 27001 Annex A 5.4 Management responsibilities

What it says

Management shall require all personnel to apply information security in accordance with the established information security policy, topic-specific policies and procedures of the organization.

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

In plain English

Management must require all personnel to apply information security as set out in the organisation's established information security policy, topic-specific policies and procedures.

Management must require all personnel to apply information security in line with the organisation's established information security policy, topic-specific policies (each on one subject, such as backup) and procedures. Three points set the scope:

  • A requirement: management makes this mandatory, not a suggestion.
  • All personnel: everyone doing work under the organisation's direction, including temporary staff, contractors, volunteers and managers themselves.
  • Established documents: the policies and procedures already in force. Annex A 5.1 covers defining and approving the policies.

Why it matters

Policies get ignored when managers treat them as optional: a team skips a procedure to meet a deadline and nobody objects. When management requires everyone, itself included, to follow them, applying security becomes part of the job, not a personal choice.

How to implement

  1. Have management state the requirement in writing.

    Put it in the top-level policy or a signed directive: everyone, including managers and contractors, must follow the information security policy, topic-specific policies and procedures, and they are not optional. Issue it to all personnel, so nobody can claim it applies only to IT.

  2. Make following policies and procedures a condition of working for you, before access begins.

    Annex A 6.2 requires employment agreements to state security responsibilities, so add a clause there and in contractor agreements. Where terms cannot change, such as existing staff or agency and managed service staff under your direction, have each person sign a short statement.

  3. Give each manager specific duties for their own team.

    Write them into the manager's role description: tell team members which procedures apply to their jobs, allow time to follow them, correct shortcuts, and follow the same rules themselves. Annex A 6.3 covers awareness and education.

  4. Act when the requirement is not met.

    Have managers follow up each missed procedure found by compliance reviews (Annex A 5.36) and fix the cause. Use the disciplinary process (Annex A 6.4) for policy violations. Where practicable, offer a confidential way to report violations, so problems reach someone who can act.

Keep it running

Repeat the requirement when someone joins or moves role and when a policy or procedure changes. Look again when a compliance review (Annex A 5.36) or an incident shows a team or manager working around a procedure.

Evidence and audit

  1. Check 1 of 4What an auditor asks for

    Ask for

    The written requirement from management, with the list of who received it.

    Look at

    Whether management issued it, whether it makes following the documents mandatory, and whether the recipients match current staff and contractor lists.

    Good evidence

    Management has stated the requirement as mandatory, and no one on the current staff or contractor lists was left out.

  2. Check 2 of 4What an auditor asks for

    Ask for

    Signed terms or statements for a sample of recent joiners, long-serving staff and contractors.

    Look at

    Whether they require the person to follow the organisation's information security policy, topic-specific policies and procedures, and, for recent joiners, whether they were in place when access began.

    Good evidence

    Every sampled person, whether long-serving or a contractor, is bound by terms or a signed statement that require this.

  3. Check 3 of 4What an auditor asks for

    Ask for

    Cases where a procedure was not followed, taken from compliance reviews, incidents and exception logs.

    Look at

    What the responsible manager did about each one.

    Good evidence

    Each case shows the manager acted, such as correcting the work or starting the disciplinary process, and none was left without a recorded decision.

  4. Check 4 of 4What an auditor asks for

    Ask for

    The records of one procedure, such as access approval, filtered to managers and senior staff.

    Look at

    Whether senior people go through the same steps as everyone else.

    Good evidence

    Senior people appear in the records on the same terms as everyone else, with no unrecorded exemptions.

Mappings

Closest match in ASD Information Security Manual: ISM-2105, Advise staff to limit posting work information on unauthorised online services, which this control covers in full and more.

ASD ISM

ASD Information Security Manual: 13 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.

PolicyMint

Need this as a written policy?

PolicyMint drafts the ISO 27001 documentation this control expects, customised to your business and checked by three independent verifiers before you see it. Not a boilerplate template you have to fight into shape. First document free.

Draft your ISO 27001 documentation