Study guide
3.3 Organizational Controls: Access Control & Identity Management (A.5.15–A.5.18)
PECB ISO/IEC 27001 Lead Implementer Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: ISMS Fundamentals & Regulatory Context
1.1 ISO/IEC 27000 Standards Family & Information Security Principles 1.2 Context of the Organization & Interested Parties (Clauses 4.1 & 4.2) 1.3 Determining ISMS Scope & Boundaries (Clause 4.3) 1.4 Leadership, Commitment & Security Policy (Clauses 5.1, 5.2, 5.3)
2 Chapter 2: Planning the ISMS, Risk Management & Support
2.1 Gap Analysis & Implementation Project Initiation 2.2 Information Security Risk Assessment Framework (Clause 6.1.2 & ISO 27005) 2.3 Risk Evaluation & Risk Treatment Methodology 2.4 Statement of Applicability (SoA) & Control Selection (Clause 6.1.3) 2.5 Information Security Objectives & Planning (Clauses 6.2 & 7.1) 2.6 Support Processes: Competence, Communication & Documented Information (Clauses 7.2–7.6)
3 Chapter 3: Implementing Annex A Organizational & People Controls
3.1 Organizational Controls: Governance, Roles & Threat Intelligence (A.5.1–A.5.8) 3.2 Organizational Controls: Asset Management & Information Classification (A.5.9–A.5.14) 3.3 Organizational Controls: Access Control & Identity Management (A.5.15–A.5.18) 3.4 Organizational Controls: Supplier Relationships & Cloud Security (A.5.19–A.5.23) 3.5 Organizational Controls: Incident Management & Evidence (A.5.24–A.5.28) 3.6 Organizational Controls: Continuity, Legal & Compliance (A.5.29–A.5.37) 3.7 People Controls: Screening, Awareness & Remote Working (A.6.1–A.6.8)
4 Chapter 4: Implementing Annex A Physical & Technological Controls
4.1 Physical Controls: Secure Areas & Equipment Protection (A.7.1-A.7.14) 4.2 Technological Controls: Endpoint & User Security (A.8.1-A.8.6) 4.3 Technological Controls: Network Security, Cryptography & Vulnerability Management (A.8.7-A.8.14) 4.4 Technological Controls: Operations, Logging, Web Filtering & Monitoring (A.8.15-A.8.24) 4.5 Technological Controls: Secure Development Lifecycle & Coding (A.8.25-A.8.34)
5 Chapter 5: ISMS Performance Evaluation & Internal Audit
5.1 Monitoring, Measurement, Analysis & Evaluation (Clause 9.1 & ISO 27004) 5.2 ISMS Internal Audit Program & Principles (Clause 9.2 & ISO 19011) 5.3 Conducting the Internal Audit & Gathering Audit Evidence 5.4 Management Review Process & Decisions (Clause 9.3)
6 Chapter 6: Continual Improvement & Certification Audit
6.1 Nonconformity & Corrective Action Management (Clause 10.1) 6.2 Continual Improvement & Maturity Enhancement (Clause 10.2) 6.3 Stage 1 Certification Audit Preparation & Document Review 6.4 Stage 2 Certification Audit, Findings & 3-Year Surveillance Cycle
3.3 Organizational Controls: Access Control & Identity Management (A.5.15–A.5.18)
Key Takeaways Explain This Topic AI
Control A.5.15 requires a formal Access Control Policy built upon the fundamental principles of Need-to-Know and Least Privilege.
Control A.5.16 (Identity Management) governs the full lifecycle of unique user identities from initial provisioning, role modifications, to prompt de-provisioning upon termination.
Control A.5.17 (Authentication Information) mandates secure management of credentials, enforcing Multi-Factor Authentication (MFA), FIDO2 hardware keys, and salted hash storage.
Control A.5.18 (Access Rights) dictates strict management of privileged access (PAM), Just-In-Time elevation, and mandatory periodic access recertifications.
Shared or generic administrative accounts are strictly prohibited unless explicitly authorized by management with documented compensating controls and 100% session audit logging.
Last updated: July 2026
3.3 Organizational Controls: Access Control & Identity Management (A.5.15–A.5.18)
Access control and identity management constitute the logical security perimeter of modern digital enterprises. Controls A.5.15 through A.5.18 establish how digital identities are established, authenticated, authorized, monitored, and reviewed throughout their lifecycle to prevent unauthorized access to organizational assets.
Overview of Access & Identity Controls (A.5.15 – A.5.18)
Control ID Control Name Core Standard Requirement Primary Lead Implementer Artifact
A.5.15 Access control Rules to grant, restrict, and manage access based on business and security requirements. Formal Access Control Policy (RBAC / ABAC rules)
A.5.16 Identity management Full lifecycle management of user identities (provisioning to de-provisioning). IAM / IdP Workflow & HR Integration Architecture
A.5.17 Authentication information Provisioning, management, and protection of authentication credentials and secrets. MFA Policy, Passphrase Standards & FIDO2 Baseline
A.5.18 Access rights Provisioning, modification, revocation, and periodic review of access rights. Periodic Access Recertification Reports & PAM Logs
Access Control Policy Principles (A.5.15)
Control A.5.15 mandates that top management approve a comprehensive Access Control Policy aligned with business objectives and risk assessments. The policy must strictly enforce two foundational security tenets:
Need-to-Know: Personnel are granted access only to the specific information assets and systems required to perform their assigned business duties.
Least Privilege: Users are granted the minimum level of permission (e.g., read-only vs. read/write/execute) necessary to execute their authorized job functions.
Access Control Architectural Models
Role-Based Access Control (RBAC): Access permissions are grouped into structured organizational roles (e.g., Payroll Specialist, Network Admin). Users are assigned roles, simplifying permission management and preventing ad-hoc permission drift.
Attribute-Based Access Control (ABAC): Access decisions dynamically evaluate user attributes (department, clear level), resource attributes (classification tag), and environmental context (device health, IP location, time of day).
Zero Trust Network Access (ZTNA): Applies continuous authentication and contextual authorization under the principle of "never trust, always verify," replacing traditional perimeter-based network access.
Identity Management Lifecycle (A.5.16)
Control A.5.16 requires that every user operating within the ISMS scope be assigned a unique identifier (User ID) . Shared or generic accounts (e.g., admin , support_team ) are strictly prohibited because they destroy audit accountability. Where shared system accounts cannot be avoided due to legacy architecture, compensating controls—such as Privileged Access Management (PAM) vaulting with single-user checkout logging—must be implemented. +-------------------------------------------------------------------------+
- | IDENTITY LIFECYCLE MANAGEMENT (A.5.16 & A.5.18) |
- +-------------------------------------------------------------------------+
1. Provisioning --> Identity created automatically upon HR onboarding trigger.
2. Authentication --> Credentials verified via MFA / SAML 2.0 / FIDO2 (A.5.17).
3. Modification --> Job transfer triggers immediate access right adjustment.
4. Recertification--> Asset Owners perform periodic access reviews (A.5.18).
5. Revocation --> HR offboarding triggers instant logical account disablement.
Emergency / Break-Glass Accounts
For catastrophic system outages where identity providers (IdPs) are unreachable, pre-configured Break-Glass Emergency Accounts are maintained. Break-glass credentials must be stored in secure dual-custody physical or digital vaults, trigger immediate high-priority SOC alarms upon use, and require 100% video session recording.
Authentication Information Management (A.5.17)
Control A.5.17 governs the issuance, management, and protection of authentication credentials (passwords, PINs, cryptographic keys, biometric templates, hardware tokens):
Multi-Factor Authentication (MFA): Mandatory for all remote access (VPN/ZTNA), cloud admin consoles, and applications handling confidential data. Phishing-resistant MFA (such as FIDO2 / WebAuthn hardware security keys) is strongly preferred over SMS-based OTPs or push notifications vulnerable to MFA fatigue attacks.
Passphrase & Credential Policies: ISO 27001:2022 guidelines emphasize long passphrases (16+ characters) and automated checking against compromised credential databases (e.g., HaveIBeenPwned API) over arbitrary monthly forced password expirations.
Cryptographic Storage: Passwords stored in databases must be hashed using salted, computationally intensive algorithms such as Argon2id, bcrypt, or PBKDF2 with high iteration counts.
Management of Access Rights & Privileged Access (A.5.18)
Control A.5.18 dictates that the allocation, modification, and revocation of access rights must follow a formal authorization workflow. Uncontrolled allocation causes Privilege Creep —where personnel accumulate access permissions as they move across departments.
Privileged Access Management (PAM)
Privileged access rights (e.g., root, domain admin, global tenant admin) pose extreme risk. Control A.5.18 mandates:
Account Separation: Standard daily work (email, web browsing) must be strictly segregated from administrative accounts.
Just-In-Time (JIT) Elevation: Administrative privileges are granted dynamically for approved change windows and automatically revoked upon task completion.
Session Recording & Monitoring: Full auditing and real-time monitoring of all privileged sessions.
Periodic Access Recertification
Asset Owners and Managers must perform periodic access reviews (e.g., quarterly for privileged accounts, semi-annually for standard accounts). Unused or unnecessary permissions identified during recertification must be promptly revoked.
Real-World Implementation Scenario:
A financial services company deploys an Identity Governance and Administration (IGA) platform integrated with HR software. When a Financial Analyst transfers to the Marketing team, HR updates the employee role. The IGA system automatically executes Control A.5.18: revoking financial ledger access while provisioning Marketing analytics permissions based on RBAC (A.5.15). Multi-Factor Authentication via FIDO2 hardware keys (A.5.17) is enforced for all system logins.