Study guide

2.6 Personnel Security, Training, Awareness, and Culture

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

2.6 Personnel Security, Training, Awareness, and Culture

Key Takeaways Explain This Topic AI

Personnel security covers the full worker lifecycle: screening, onboarding, role changes, access reviews, monitoring, offboarding, and post-employment obligations.

Awareness, training, and education are different levels of learning and should be tailored to roles and risk.

Culture is shaped by incentives, leadership behavior, reporting safety, usable controls, and consistent accountability.

Insider risk programs must balance detection and prevention with privacy, labor rules, proportionality, and fairness.

Last updated: May 2026

People Controls Across The Lifecycle

Personnel security begins before access is granted and continues after access is removed. Screening, background checks where lawful, employment agreements, acceptable use acknowledgement, confidentiality obligations, role-based access, training, supervision, monitoring, transfer controls, termination procedures, and post-employment reminders all reduce people-related risk. The right control depends on role sensitivity, law, contract, and business context.

Pre-employment screening should be proportional and lawful. A finance administrator, system engineer, delivery contractor, and call center agent may need different checks. Screening is not proof of trustworthiness, and it should not become discriminatory or excessive. It is one input to risk management, combined with least privilege, separation of duties, logging, supervision, and a culture where concerns can be reported.

Onboarding should connect identity proofing, job role, manager approval, policy acknowledgement, training, device issuance, and access provisioning. Access should be based on role and business need, not copied blindly from a previous employee. Privileged access should require stronger approval, separate accounts where appropriate, MFA, session logging, and periodic review. Emergency access should be controlled and reviewed after use.

  • Lifecycle stage Security focus Common failure
  • Pre-hire or pre-contract Screening and role suitability Overcollecting data or ignoring local law
  • Onboarding Approved access and policy acknowledgement Copying access from another user
  • Employment or engagement Training, supervision, review, monitoring No review after job duties change
  • Transfer Remove old access and add new need-based access Privilege accumulation over time
  • Termination Timely revocation, asset return, reminders Delayed deprovisioning or shared accounts
  • Post-employment Enforce obligations and monitor unusual activity No record of signed agreements

Transfers are high risk because access accumulates. A developer who moves into product management may retain repository admin rights. A support lead who transfers to sales may keep case export privileges. A privileged administrator who joins a vendor management role may retain production access without need. Joiner, mover, and leaver processes should remove access no longer required and document approval for new access.

Termination procedures should be coordinated with HR, legal, management, physical security, identity teams, and IT support. Timing matters. A planned departure may allow normal offboarding, while an involuntary termination involving privileged access may require synchronized account disablement, badge revocation, session termination, device collection, and monitoring. Shared accounts make termination control weaker because access cannot be tied to one person.

Awareness, training, and education are not synonyms. Awareness creates recognition and attention, such as phishing reporting reminders or data handling notices. Training builds task-specific skill, such as secure coding, incident triage, or data classification. Education develops deeper understanding for professionals who design, manage, or audit programs. Role-based learning is more effective than one generic annual slide deck.

A role-based learning plan might include:

All workforce members: phishing recognition, reporting channels, acceptable use, data handling, and physical security basics.

Developers: secure design, code review, dependency risk, secrets handling, and threat modeling.

Administrators: privileged access, logging, change control, backup, and emergency access.

Executives: risk appetite, incident decision-making, legal notification, and crisis communications.

Help desk: identity verification, social engineering, password reset, and escalation.

Culture is what people do when policy and pressure collide. If leaders reward speed while punishing security reporting, employees will hide risk. If controls are impossible to use, people will create workarounds. If phishing reporters are mocked, reporting will drop. A healthy security culture makes reporting easy, treats honest mistakes as learning opportunities, and applies accountability consistently when people knowingly bypass controls.

Insider risk programs need care. Indicators such as unusual downloads, access outside normal hours, privilege misuse, policy violations, or resignation timing can be relevant. They are not proof of wrongdoing by themselves. Programs should be authorized, privacy-aware, proportional, documented, and reviewed for fairness. Legal, HR, works councils, or labor representatives may need involvement depending on jurisdiction and organization.

Scenario: a high-performing engineer keeps production admin access after moving to a product strategy role. The manager says the access is convenient for occasional questions. The CISSP answer is to remove unneeded privileged access and provide a controlled request path for rare support needs. Convenience does not justify standing privilege when job duties changed.

Scenario: phishing simulation metrics show that employees click less often but also report fewer suspicious messages. The program may be discouraging reporting or confusing users. A better metric set includes report rate, time to report, true positive reports, repeat susceptibility, department trends, and whether employees know how to report real incidents. Training should improve behavior, not just reduce embarrassment.

Scenario: a customer support team routinely exports full customer records to spreadsheets because the official tool is slow. More awareness training alone will not fix this. The control design must address workflow usability, least-privilege exports, DLP, manager review, tool performance, data minimization, and clear accountability. Culture improves when secure behavior is practical.

Personnel controls should be measured. Useful metrics include access review completion, terminated account disablement time, privileged account recertification, training completion by role, phishing report quality, policy exception trends, and unresolved separation-of-duties conflicts. Metrics should drive action. A dashboard that shows overdue privileged reviews but has no escalation path is a weak control.