Study guide
7.5 Remediation, Exceptions, Risk Acceptance, and Evidence Quality
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
7.5 Remediation, Exceptions, Risk Acceptance, and Evidence Quality
Key Takeaways Explain This Topic AI
Remediation governance assigns ownership, due dates, validation criteria, and escalation for findings that require action.
Exceptions are temporary, risk-based departures from a requirement and need documented justification, expiration, compensating controls, and approval.
Risk acceptance must be made by an accountable business authority with enough information to understand residual risk.
Evidence quality determines whether assessments, audits, and closure decisions are defensible.
Last updated: May 2026
Governing What Happens After Findings
Assessment and testing create value only when the organization acts on results. A finding should describe a condition, criteria, cause, effect, affected scope, risk rating, owner, and recommended treatment. Remediation governance then determines who fixes it, by when, how completion will be validated, and what happens if it remains unresolved. Without this discipline, reports accumulate while risk stays in place.
Remediation should be prioritized by risk, not by report order. A critical weakness on an exposed payment system may need emergency action. A similar technical weakness on a segmented lab host may have a different deadline. Prioritization should consider asset criticality, exploitability, exposure, data sensitivity, compensating controls, business process impact, regulatory obligation, and available threat intelligence.
Closure requires validation. A team may say a patch was installed, but validation should confirm the vulnerable version is gone, the service restarted, the compensating configuration is active, or the control operates as expected. For process findings, validation may require updated procedures, evidence samples, training records, workflow changes, or control test results. The evidence should match the finding.
Exceptions are sometimes necessary. A legacy medical device may not support a patch. A vendor application may require an insecure protocol until a replacement is complete. A factory system may need a longer maintenance window. An exception is not permission to ignore risk. It is a documented, approved, time-bounded decision to operate outside the normal requirement while residual risk is managed.
Risk acceptance is a business decision. Security can explain the risk, propose treatments, and recommend escalation, but the accountable risk owner accepts residual risk. The approver should have authority over the affected business process and consequences. Acceptance by a low-level technical administrator is weak when the impact is enterprise, regulatory, financial, or safety related.
Item Required content Good evidence Weak evidence
Remediation plan Owner, action, due date, validation method Change record, test result, updated configuration Email saying fixed
Exception Scope, reason, compensating controls, expiry Approved risk memo, asset list, monitoring evidence Permanent waiver with no owner
Risk acceptance Residual risk, impact, alternatives, approver Signed decision by accountable owner Approval by someone without authority
Closure package Finding, fix, retest, date, reviewer Reproducible retest evidence and ticket trail Screenshot with no timestamp or system name
Compensating controls need scrutiny. A compensating control should reduce the same risk in a meaningful way. Network isolation may compensate for an unpatchable service if it truly limits access and is monitored. Extra logging alone may not compensate for a vulnerability that enables immediate unauthorized data export unless detection and response are fast enough to prevent harm. The control should be tested, not merely listed.
Exception expiration is critical. Temporary exceptions often become permanent when no one tracks them. Each exception should have an expiry date, review frequency, owner, conditions, and trigger for reapproval or closure. If the underlying project slips, the risk owner should explicitly renew or reject the exception with current information. Silent extension is poor governance.
Evidence Quality Checklist
Relevant: The evidence addresses the exact control, finding, asset, and period under review.
Complete: It includes enough context to support the conclusion without guessing.
Current: It reflects the time period or remediation state being claimed.
Authentic: The source is trustworthy and protected from inappropriate alteration.
Reproducible: Another qualified reviewer could understand how the conclusion was reached.
Traceable: It links to the requirement, finding, owner, approval, and validation result.
Evidence quality affects audit and legal defensibility. A screenshot without date, hostname, user, or source system may be easy to collect but weak. A system-generated report with scope, timestamp, query criteria, owner, and retention control is stronger. For high-impact findings, the organization may need change tickets, configuration exports, retest logs, approvals, and monitoring evidence.
Risk treatment options should remain clear. Remediate by fixing the weakness. Mitigate by reducing likelihood or impact through other controls. Transfer by shifting some financial or operational consequence through insurance or contract while recognizing risk remains. Avoid by stopping the risky activity. Accept by making an informed decision to live with residual risk. The chosen path should be documented.
Escalation prevents quiet drift. If a critical finding is overdue, the issue should move from the technical team to management and then to a risk committee if necessary. Repeated overdue items may indicate funding shortages, architectural debt, unclear ownership, or unrealistic standards. Escalation should focus on decision making, not blame. The goal is to make residual risk visible to the people authorized to act.
A mature program also learns from recurrence. If the same vulnerability appears after every release, the root cause may be weak secure coding practice or dependency management. If exceptions cluster around one platform, the standard may be misaligned or the platform needs replacement. If evidence is repeatedly rejected, control owners need clearer expectations and better tooling.
The CISSP answer often turns on accountability. Security identifies and communicates risk, but business owners own decisions that affect mission, customers, safety, and compliance. A closed finding without validation, an exception without expiry, or an acceptance without proper authority is not strong governance. It is a paper trail that may fail when tested.