ISO 27001 Control A.5.15: Access Control
Almost every security question eventually becomes an access question. Who can read the customer database? Who can approve a payment? Who can walk into the room with the servers? A.5.15 is where ISO 27001 asks you to answer those questions deliberately, with rules, instead of letting access grow by accident. It is the 15th of 37 organizational controls in our walk through Annex A.
Access control is also where good intentions meet daily friction. Teams want to move quickly, and a broad permission is always the fastest fix. The skill is to design rules that are strict where it matters and light everywhere else, so that people follow them rather than work around them.
What the control requires
Annex A control 5.15 of ISO 27001:2022 states that rules to control physical and logical access to information and other associated assets shall be established and implemented based on business and information security requirements.
The key elements:
- Rules - a defined set of principles for granting and restricting access, usually captured in a topic-specific access control policy
- Physical and logical access - buildings and rooms as well as systems, applications, data and networks
- Information and other associated assets - not only data, but the equipment, services and facilities that handle it
- Established and implemented - written down and enforced in practice
- Business and information security requirements - the rules are driven by what the organization needs to do and by its risks, not by what is technically convenient
A.5.15 is a preventive control in ISO/IEC 27002:2022. Annex A states the control; ISO 27002 gives guidance, including principles such as need-to-know, need-to-use, “everything is generally forbidden unless expressly permitted”, and separation of roles for requesting, authorizing and administering access. The related controls that implement those rules, namely identity management, authentication information and access rights, follow in the next three posts of the series.
How to implement access control
Write a short, usable access control policy
The policy should state the principles and the responsibilities, not the detail of every system. Cover the following:
- The default position, usually least privilege and need-to-know
- Who owns the decision to grant access to each type of information or system, normally the asset owner
- Which roles can approve requests, and which roles administer access
- Rules for physical access to sensitive areas, consistent with physical entry
- Rules for remote access and for access by third parties
- How often access is reviewed and what happens when someone changes role or leaves
Link it to your wider policies for information security so it sits in the same document structure. Two or three pages is plenty. If a new starter cannot read it over coffee, it is too long.
Define access by role and by information
Most organizations get better results by defining standard access profiles for roles, such as developer, finance analyst or support agent, than by deciding each person’s access one request at a time. Start with your inventory of information and other associated assets and the classification of information of each item. Systems that hold confidential data deserve narrower profiles and stricter approval than a shared marketing folder.
For each important system, record who owns it, which roles need which level of access, and who can approve exceptions. A simple matrix of roles against systems is often enough, and it gives you the basis for the periodic review that A.5.18, access rights, calls for.
Apply the rules to physical access as well
Do not stop at logins. Server rooms, archives, wiring cupboards and storage for equipment are covered by the same control. Make sure that the rules for who may enter match the rules for who may use the systems inside, and that visitors, cleaners and maintenance staff are treated as part of the picture. The secure-area controls we covered earlier, such as physical security perimeters, supply the physical side of the design.
Separate duties and handle privileged access carefully
Some combinations of access should not sit with one person, for example creating a supplier and approving its payments, or writing code and releasing it unreviewed to production. Apply segregation of duties in your rules, and where small teams cannot separate fully, add compensating checks such as review or logging. Administrator and other privileged accounts need extra rules about approval, use and review; the Annex A technological controls cover those in detail later in the series.
Review the rules as the organization changes
Access rules are never finished. New systems arrive, teams reorganize and suppliers come and go. Build a lightweight routine: when a new system is introduced, its owner agrees the access roles before go-live; when a team changes, the access profiles are checked; and once a year the policy itself is reread by the people who apply it. Record changes and the reasons for them.
It also helps to decide in advance how you handle urgent requests. An incident at midnight sometimes needs broader access quickly. A documented emergency route, with approval after the fact and an automatic expiry, is far better than a culture of informal workarounds that nobody records. Keep the log of such events short and review it at the next management meeting, so patterns are noticed early.
Lastly, think about how people ask for access. A request form or ticket that names the person, the system, the level, the business reason and the approver takes two minutes to complete and produces exactly the evidence an auditor wants. If it takes twenty minutes, people will ask in a chat message instead, and the trail disappears.
Related controls and clauses
A.5.1 connection. Policies for information security provides the framework in which the access control policy lives.
A.5.3 connection. Segregation of duties prevents a single person from holding conflicting access.
A.5.9 and A.5.12 connection. The inventory of information and other associated assets and classification of information tell you what needs protecting and how strictly.
A.5.14 connection. Information transfer covers what happens to information after someone with access sends it on.
A.7.2 connection. Physical entry implements the physical half of access control.
Clause 6.1 connection. Clause 6.1, Actions to address risks and opportunities, is where you decide how strict the rules need to be for each risk.
Forward reference. Identity management (A.5.16) is covered in the next post, followed by authentication information (A.5.17) and access rights (A.5.18).
What auditors check
A documented policy and rules. Auditors ask for the access control policy and check that it reflects need-to-know and least privilege, and that it matches how access is actually granted.
Alignment with business needs. They look for evidence that the rules were set with business owners and risk in mind, not copied from a template.
Sampling of access. Expect them to pick a few systems and people, then compare the access held with the role and the approval trail.
Physical access too. They may walk to the server room or office entrance and check that physical access follows the same logic.
Third-party and remote access. Auditors ask how suppliers and remote staff get access, who approves it and when it ends.
Exceptions. They look at how exceptions are requested, approved, recorded and reviewed. A pile of undocumented exceptions suggests the rules are not working.
Common mistakes to avoid
A policy nobody uses. A long document written for the audit and never consulted does not control anything. Keep it short and refer to it in day-to-day decisions.
Access by seniority. Giving managers access to everything their team has is a common habit and a common finding. Access should follow need, not rank.
Only logical access. Strong password rules in a building anyone can walk into leave a gap. Treat physical and logical access together.
Shared accounts. If several people use one login, you cannot show who did what. Where they are unavoidable, document why and add compensating controls.
No owner for each system. If nobody is responsible for approving access to an application, approvals default to whoever is available.
Forgetting suppliers. Third-party access is often broader and longer-lived than staff access. Include it in the rules from the start.
How 27kay can help
We help organizations turn access control from a pile of historical permissions into a short set of rules and role profiles that people understand. As part of ISO 27001 implementation, we draft proportionate policy, map roles to systems and prepare the evidence an auditor will ask for. For the full picture, see our ISO 27001 knowledge hub.
If you had to explain, today, why each person has the access they have, how far would you get? Get in touch - we will help you build an answer you are proud to show.