Cookies on this site. Help us understand what works and improve your experience. Essential cookies keep the site working. With your permission, our visit insights and Google Analytics measure usage, and Google Ads measures advertising. Optional cookies are not required to use the free kit. Change your choice anytime in Cookie settings. Privacy policyCookie policy
Define rules on who may access which information and systems, based on business need and least privilege.
Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.
Why this control matters
Access control should turn business need into consistent approval rules, not just state that access is restricted. It needs to connect ownership, role design, default-deny choices, and periodic review so reviewers can trace why each entitlement exists and who accepted the risk. Weak access governance leaves application owners, HR, and IT with conflicting decisions, creating orphaned, excessive, or poorly justified access paths.
Common auditor findings to check for
Potential gaps to test in your own environment, not a claim about observed audit frequency.
Role definitions exist but systems still allow direct grants without owner approval, creating excessive access and inconsistent least-privilege decisions.
Access requests are approved informally in chat or email, leaving no durable record of scope, risk acceptance, or reviewer identity.
Periodic access reviews happen for some platforms only, so privileged or sensitive shares can remain unchallenged after role changes or leavers.
How you can implement it
Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.
Assign system and data owners to define access rules by information classification, job family, supplier status, and remote-working need. Use an access matrix or decision table for each key application, share, and admin function. Require documented approval before provisioning, with a clear default-deny position for confidential assets and exceptions time-boxed with expiry dates.
Link access granting to the joiner-mover-leaver flow so HR changes trigger review of entitlements, not just new account creation. The access control policy should define who can approve standard, elevated, and emergency access, while the procedure explains the workflow. Keep a log of requests, approval names, dates, business justification, and revoked rights.
Run illustrative review cycles based on risk: monthly for privileged and externally exposed systems, quarterly for customer or finance data, and after role changes or supplier offboarding. Use access recertification reports, manager attestations, and exception registers. The accountable role should verify that temporary access, dormant accounts, and shared mailboxes are either justified or removed.
Tie technical settings to the documented rules through group-based access, conditional access, and segregation of duties checks. Where a platform cannot enforce the intended rule, record the compensating control, such as compensating review or monitoring, and assign an owner. Capture evidence of exceptions, risk acceptance, and remediation so findings can be shown as tracked to closure.
What an auditor will ask to see
Access Control Policy and system-specific access matrix showing required approvals, role mapping, and default-deny rules.
Completed access request tickets with business justification, approver identity, date/time stamps, and granted scope.
Quarterly access review report listing users, privileged roles, anomalies, exceptions, and corrective actions with owner due dates.
Baseline documents in the kit
These free kit documents help you document or evidence A.5.15. Each one is tailored to your organization when you build your kit.
Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.
For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.
Get these documents tailored to your organization
109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.