ISO 27001 A.5.15: access control rules, explained for startups

What A.5.15 asks of a small company, and what an auditor samples.

Decide who gets access to which information and systems, and enforce those decisions. Base access on real business need rather than convenience.

Why it exists: to give people only the access their job needs.

A.5.15 Access control

People get only the access their job needs. What proves it: access rules based on job need, and a recent access request that followed them.

A certification auditor samples the access control rules and sample access requests. A file that usually does the job: a ticket showing an access request, the manager approval and the access granted.

How to put it in place

Each step leaves a record, and the record is what the auditor samples rather than the step itself. Inside Polara, the control card for A.5.15 walks you through it in this order.

  1. Write down who approves access to each key system.
  2. Route every request through one place, such as a ticket or a form.
  3. Grant only what the role needs and keep the approval.

The free ISO 27001 readiness assessment asks one question that evidences it:

  • How is access to company systems granted?

Policies, connectors and the SOC 2 overlap

In the ISO 27001 policy pack, the Access Control Policy covers A.5.15. An auditor reads the policy for the rule, then samples the records to see the rule was followed.

Connected systems that pull evidence for it:

  • Amazon Web Services, IAM roles: privileged roles and the trust policies that grant them.
  • Amazon Web Services, IAM groups: groups and their member assignments.
  • GitHub, Organization teams: teams in the organization and their permissions.
  • Google Cloud, IAM members: project-level IAM policy bindings, showing which roles are granted to which members.
  • Google Workspace, Directory groups: all groups in the Workspace domain with member counts.

The same evidence counts toward SOC 2. The Trust Services criteria that cover this ground: CC6.1, logical access and CC6.3, least privilege.

Organizational controls

A.5.15 is one of the 37 organizational controls in Annex A. How the company runs security: policies, roles, suppliers, incidents, continuity and legal duties. Most of these are written decisions and the records that show you follow them.

Nearby controls in the same theme:

Before it: A.5.14, sending information out. After it: A.5.16, identities and accounts. Every control, by theme, is on the Annex A controls page.

Questions

What does ISO 27001 A.5.15 require?
Decide who gets access to which information and systems, and enforce those decisions. Base access on real business need rather than convenience.
What evidence does an auditor want for A.5.15?
Access rules based on job need, and a recent access request that followed them. A certification auditor samples the access control rules and sample access requests.

Get ready for ISO 27001 certification.

The readiness assessment is free, with no payment and no card. ISO 27001 is part of Constellation, at $10,800 a year: everything in Orbit plus the management system, the policies, the evidence and the management review for ISO 27001, and your SOC 2 Type 2 audit is included in every contract year. You contract the certification body directly.

The internal audit is priced separately: Polara arranges it with an independent internal auditor from our partner network who works in the platform, and quotes it for your company.

Take the free assessment

Polara Labs is not a certification body. Certification audits are performed by independent accredited certification bodies.