Study guide

2.1 Professional Ethics, CIA, and Security Governance

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.1 Professional Ethics, CIA, and Security Governance

Key Takeaways Explain This Topic AI

Security governance connects business objectives, risk appetite, accountability, policy, and measurable control performance.

The CIA triad remains central, but CISSP judgment also considers authenticity, accountability, nonrepudiation, safety, privacy, and mission impact.

Professional ethics require lawful, honest, competent, and public-interest-oriented conduct even when a shortcut appears convenient.

Governance decisions should identify ownership, escalation paths, evidence, and tradeoffs rather than treating security as a purely technical preference.

Last updated: May 2026

Ethics And Governance Before Tools

CISSP work begins with a leadership obligation, not a product choice. A security professional is expected to protect society, the organization, and the profession while staying lawful, honest, diligent, and competent. That obligation matters when a manager asks for quiet exception handling, when a sales team wants to overstate a control, or when an engineer wants to bypass review because a release date is near.

The ethical answer is not always the most aggressive security answer. A hospital cannot simply shut down clinical systems because a scanner found a vulnerability. A bank cannot secretly monitor employees without checking policy, notice, privacy, labor, and legal constraints. A software company cannot hide a material incident from customers when contracts or law require notice. Professional judgment balances protection with lawful authority and business mission.

Governance is the system that makes those judgments repeatable. It defines who decides, what principles they use, what risk level is acceptable, how conflicts are escalated, and how performance is measured. Good governance prevents security from becoming personality driven. If the CISO, privacy officer, general counsel, data owner, and operations leader disagree, the organization needs an approved process for deciding and documenting the outcome.

Governance element Practical question Example evidence

Mission alignment What business objective does security protect? Board risk memo, strategy map, service criticality list

  • Risk appetite How much risk is leadership willing to accept? Approved appetite statement, tolerance thresholds
  • Accountability Who owns the decision and result? RACI chart, control owner register
  • Policy authority What rule has been approved? Information security policy, privacy policy
  • Oversight How does leadership know controls work? Metrics, audit reports, exceptions, risk register

The CIA triad is still a useful mental model. Confidentiality limits disclosure to authorized parties. Integrity protects accuracy, completeness, and authorized change. Availability ensures systems and data are usable when required. In real scenarios, these objectives compete. Encrypting all data supports confidentiality, but poor key recovery can harm availability. Strict change freeze may protect integrity, but it can delay urgent security patches.

CISSP scenarios often add related assurance goals. Authenticity asks whether an entity or message is genuine. Accountability asks whether actions can be traced to responsible parties. Nonrepudiation supports proof that a party cannot credibly deny an action, often through digital signatures, logging, time sources, and process controls. Safety matters when cyber failures can injure people or damage physical environments.

Consider a manufacturer running connected production equipment. Confidentiality protects formulas and customer designs. Integrity protects machine instructions and quality data. Availability keeps production running. Safety may override all three if a control change could create physical danger. A governance board should not approve a patch window only from a server perspective; it should include plant operations, safety, vendor support, rollback planning, and business impact.

Security governance also defines separation of duties. The person requesting access should not be the only person approving it. The developer who writes a production change should not be the only person who validates it. The administrator who can alter logs should not be the only person who reviews evidence. These separations reduce fraud, error, and conflict of interest while preserving accountability.

Use this governance workflow when a security decision is contentious:

State the business objective and affected stakeholders.

Identify the security objectives at stake: confidentiality, integrity, availability, privacy, safety, authenticity, accountability, or nonrepudiation.

Identify applicable law, contracts, policies, and risk appetite.

List feasible options with cost, residual risk, and operational impact.

Assign a decision owner with authority to accept the residual risk.

Record the decision, evidence, review date, and exception conditions.

Scenario: a business unit wants to launch a customer analytics feature using personal data collected for account support. The security team sees no immediate technical weakness, but the privacy team questions purpose limitation and notice. The right governance move is not to approve the launch just because access controls exist. The team should review privacy basis, data minimization, consent or notice obligations, retention, customer expectations, and whether the use matches approved policy.

Scenario: an executive asks a security analyst to send raw investigation logs to a personal email account before a board meeting. The analyst should not comply merely because the request is senior. The ethical and governance response is to use approved evidence handling, legal hold, encryption, need-to-know access, and counsel-approved distribution. Authority does not eliminate handling requirements.

A mature security program links governance to metrics. Metrics should not reward the wrong behavior. Closing every vulnerability ticket within seven days sounds strong, but it may encourage false closure or emergency changes that destabilize critical systems. Better reporting separates severity, exploitability, asset criticality, remediation status, accepted exceptions, overdue approvals, and business risk. Leadership needs decision-quality information, not inflated activity counts.

The CISSP exam outline frames this domain as a broad management domain, so study the language of governance as carefully as control vocabulary. When an answer choice says to install a tool immediately, ask whether the scenario first needs policy authority, business owner approval, legal consultation, risk assessment, or executive acceptance. The best answer often respects process before technology.