Study guide
6.5 Service Accounts, Non-Human Identities, and Privilege Management
CISSP Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: CISSP Orientation, CAT, and Official Source Control
1.1 Credential Scope, CISSP Mindset, and Search Language 1.2 Exam Outline Effective Date and Eight-Domain Map 1.3 CAT Format, 100-150 Items, and Forward-Only Rules 1.4 Passing Grade, Results, Feedback, and Retake Policy 1.5 Experience, Endorsement, and Associate of ISC2 Path 1.6 Pricing, AMF, CPE, and Maintenance Overview
2 Chapter 2: Security and Risk Management
2.1 Professional Ethics, CIA, and Security Governance 2.2 Policies, Standards, Procedures, Guidelines, and Control Ownership 2.3 Legal, Regulatory, Privacy, and Investigation Context 2.4 Risk Identification, Analysis, Treatment, and Reporting 2.5 Business Continuity, BIA, and Recovery Prioritization 2.6 Personnel Security, Training, Awareness, and Culture 2.7 Threat Modeling, Supply Chain Risk, and Third-Party Governance 2.8 Security and Risk Management Case Lab
3 Chapter 3: Asset Security and Data Lifecycle
3.1 Asset and Data Classification, Ownership, and Roles 3.2 Handling Requirements, Labeling, Privacy, and Cross-Border Data 3.3 Data States and Protection Methods: DLP, DRM, and CASB 3.4 Data Lifecycle, Retention, Remanence, and Destruction 3.5 Secure Provisioning, Inventory, and Asset Management 3.6 Asset Security Case Lab
4 Chapter 4: Security Architecture, Engineering, and Cryptography
4.1 Secure Design Principles and Security Models 4.2 Control Selection, System Security, and Architecture Risk 4.3 Cryptography Foundations: Symmetric, Asymmetric, Hashing, and PKI 4.4 Cryptographic Lifecycle, Key Management, and Attack Patterns 4.5 Cloud, Container, IoT, Edge, and Shared Responsibility Architecture 4.6 Physical Site, Facility, and Environmental Security 4.7 Information System Lifecycle Engineering and Retirement 4.8 Architecture and Engineering Case Lab
5 Chapter 5: Communication, Network Security, and Zero Trust
5.1 Network Architecture, OSI/TCP/IP, and Secure Design 5.2 Secure Protocols, Encryption in Transit, and Channel Protection 5.3 Segmentation, Microsegmentation, SDN, VPC, and Zero Trust 5.4 Wireless, Cellular, Remote Access, and Third-Party Connectivity 5.5 Network Components: NAC, IDS/IPS, Firewalls, and Endpoints 5.6 Monitoring, Observability, Capacity, and Resilient Communications 5.7 Communication and Network Security Case Lab
6 Chapter 6: Identity and Access Management
6.1 Identity Proofing, Authentication, Authorization, and Accountability 6.2 Access Control Models: RBAC, MAC, DAC, ABAC, and Risk-Based Access 6.3 Federation, SSO, MFA, Passwordless, and Session Management 6.4 Provisioning, Deprovisioning, JML, and Access Reviews 6.5 Service Accounts, Non-Human Identities, and Privilege Management 6.6 Physical, Logical, Cloud, and Hybrid Access Boundaries 6.7 IAM Case Lab
7 Chapter 7: Security Assessment, Testing, and Audit Strategy
7.1 Assessment, Test, and Audit Strategy Selection 7.2 Control Testing, Vulnerability Assessment, and Penetration Testing 7.3 Log Review, Code Review, Misuse Cases, and Compliance Checks 7.4 Security Process Data, KPIs, KRIs, and Reporting 7.5 Remediation, Exceptions, Risk Acceptance, and Evidence Quality 7.6 Security Assessment and Testing Case Lab
8 Chapter 8: Security Operations, Incident Response, and Resilience
8.1 Investigations, Evidence, Forensics, and Legal Readiness 8.2 Logging, Monitoring, SOC, and Alert Triage 8.3 Configuration, Change, Patch, and Vulnerability Operations 8.4 Incident Management, Containment, Eradication, and Recovery 8.5 Disaster Recovery, Backup, Availability, and Resilience 8.6 Physical Security Operations and Safety 8.7 Security Operations Case Lab
9 Chapter 9: Software Development Security and DevSecOps
9.1 Secure SDLC Governance and Requirements 9.2 Architecture, Threat Modeling, and Design Review 9.3 Secure Coding, Code Review, and Application Testing 9.4 CI/CD, Source Control, and Environment Separation 9.5 Software Supply Chain, Third-Party Components, and Deployment 9.6 DevSecOps Vulnerability Management and Release Risk 9.7 Software Development Security Case Lab
10 Chapter 10: Integrated CISSP Governance Scenario Labs
10.1 Enterprise Risk Committee Decision Lab 10.2 Cloud Migration Security Architecture Lab 10.3 Ransomware Incident and Business Continuity Lab 10.4 Identity Modernization and Zero Trust Lab 10.5 Third-Party Breach and Contract Governance Lab 10.6 Secure SDLC Transformation Lab 10.7 Full CISSP Manager Simulation
11 Chapter 11: Final Review, Endorsement, CPE, and Test-Day Strategy
11.1 Final 45-Day CISSP Study Plan 11.2 CAT Timing and Forward-Only Decision Workflow 11.3 Mixed-Domain Remediation and Manager Mindset Review 11.4 Test-Day Checklist and Pearson VUE Readiness 11.5 Endorsement, Associate Path, and Work Experience Documentation 11.6 CPE, AMF, and Three-Year Maintenance Plan 11.7 CISSP Final Mixed Review
6.5 Service Accounts, Non-Human Identities, and Privilege Management
Key Takeaways Explain This Topic AI
Non-human identities include service accounts, workloads, bots, devices, pipelines, and API clients, and they require the same lifecycle rigor as human identities.
Standing privilege should be minimized through scoped permissions, just-in-time elevation, privileged access management, and monitored sessions.
Secrets, keys, certificates, and tokens are credentials that need ownership, rotation, storage protection, and revocation processes.
Break-glass and emergency access should be rare, strongly controlled, logged, tested, and reviewed after use.
Last updated: May 2026
Governing Non-Human Identity
Not every identity represents a person. Modern environments use service accounts, machine identities, application identities, CI/CD pipeline identities, containers, serverless functions, managed identities, API clients, bots, scripts, robotic process automation accounts, network devices, and IoT devices. These identities may authenticate with passwords, keys, certificates, tokens, instance metadata, workload identity federation, or signed requests.
Non-human identities can be harder to govern than human identities because they may not have a manager, employment status, or obvious business owner. They are also tempting places to store broad permissions because applications need to keep running. A service account that can read every database, write to storage, and administer cloud resources may appear to solve deployment problems, but it creates a powerful compromise path.
The first control is inventory. The organization should know which non-human identities exist, what system owns them, who approves changes, which credentials they use, what permissions they hold, where secrets are stored, and when they expire. Unknown service accounts are like unmanaged administrator accounts. They may survive migrations, mergers, vendor departures, and application retirements.
The second control is least privilege. A workload should receive only the permissions needed for its function, in the environment where it runs, for the resources it must access. Development, test, and production identities should be separate. Read-only reporting jobs should not use write-capable credentials. A backup process may need broad read access but should be isolated, monitored, and protected from deletion or encryption abuse.
Secrets management is central to non-human IAM. Secrets should not be hard-coded in source code, scripts, container images, tickets, documentation, or local configuration files. They should be stored in approved vaults or managed identity systems, accessed at runtime, rotated on a defined schedule, and revoked when no longer needed. Rotation must be tested because fragile applications may break when a credential changes.
Privileged access management controls accounts that can administer systems, change security settings, view sensitive data, or bypass normal controls. PAM may include credential vaulting, checkout workflows, just-in-time privilege, session recording, command filtering, approval, and post-use review. The goal is to reduce standing privilege and create accountability for high-impact actions.
- Identity type Main risk Control expectation
- Service account Persistent broad access Owner, scope, vaulting, rotation, monitoring
CI/CD pipeline identity Deployment or supply chain compromise Environment separation, signed artifacts, limited deploy rights
- Cloud workload identity Excess permissions across resources Managed identity, scoped roles, policy review
- API client Token theft or overbroad scopes Short-lived tokens, minimum scopes, revocation
- Break-glass account Uncontrolled emergency use Strong protection, alerting, session review, testing
Just-in-time access grants privilege only when needed and often only for a limited time. A database administrator may request elevated rights for a maintenance window, receive approval, complete the task, and lose privilege automatically. This pattern reduces the time an attacker can exploit a compromised account. It also creates evidence linking the privileged action to a request, approver, and business purpose.
Privilege escalation risk includes both legitimate elevation and attacker abuse. Legitimate elevation should be controlled through workflows, policy, and logging. Attacker escalation may exploit weak permissions, misconfigured roles, token theft, vulnerable software, or excessive delegation. IAM teams should work with security operations to monitor unusual privilege grants, new credentials, role changes, and access to sensitive secrets.
Break-glass accounts are emergency accounts used when normal access paths fail. They are necessary in many environments because identity providers, MFA services, networks, or PAM tools can fail. They should not become everyday shortcuts. Break-glass credentials should be protected, rarely used, monitored in real time, documented, and reviewed after every use. The organization should periodically test that emergency access works without exposing it to routine abuse.
Cloud environments increase the importance of non-human identity. A cloud role attached to a compute instance, function, or container can access storage, secrets, databases, queues, and administrative APIs. Misconfigured trust policies may allow one workload to assume another role. Overbroad permissions such as wildcard actions or global resource access should be challenged. Cloud identity policy should be reviewed with the same seriousness as network firewall rules.
Privileged and Non-Human Access Checklist
Assign a named human owner and system owner to every service, workload, and automation identity.
Store credentials in an approved secrets management system or use managed identity where possible.
Separate production and nonproduction identities, credentials, and permissions.
Use scoped permissions, short-lived tokens, and just-in-time elevation for high-risk access.
Monitor secret access, privilege grants, credential creation, failed authentication, and unusual API calls.
Retire identities and revoke secrets when applications, integrations, vendors, or devices are decommissioned.
The governance point is that non-human identity is not an exception to IAM. It is IAM at machine speed and cloud scale. If a service account has no owner, no expiration, broad permissions, and a secret stored in code, the organization has accepted a hidden privileged access path. Least privilege, lifecycle ownership, and monitoring bring that risk back into management view.