Study guide
5.7 Security Assessment Report (SAR) & Risk Findings Analysis
ISC2 Certified in Governance, Risk and Compliance CGRC
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
0.1 ISC2 CGRC Exam Structure, Logistics & Passing Strategy 0.2 NIST RMF 7-Step Lifecycle & GRC Architecture
2 Chapter 1: Security and Privacy Governance, Risk Management, and Compliance Program
1.1 Enterprise Governance & GRC Frameworks 1.2 Security and Privacy Objectives: CIA, Non-Repudiation and Privacy Concepts 1.3 Multi-Tier Risk Management & Assessment Methodologies 1.4 System Development Life Cycle and Information Life Cycle Management 1.5 Establishing and Operating the Compliance Program 1.6 Legal, Regulatory & Federal Compliance Drivers 1.7 Privacy Governance, Organizational Roles & ISC2 Code of Ethics
3 Chapter 2: Scope of the System
2.1 System Boundary Definition, Architectural Context & Types 2.2 Identifying Information Types with NIST SP 800-60 2.3 System Categorization Process & Impact Analysis (FIPS 199 / SP 800-60) 2.4 Impact and Risk Determination Under Non-Federal Frameworks 2.5 System Registration, Environment & Interconnection Agreements
4 Chapter 3: Selection and Approval of Framework, Security, and Privacy Controls
3.1 Control Catalogs & NIST SP 800-53 Rev. 5 Structure 3.2 Control Allocation & Inheritance Models 3.3 Control Tailoring, Scoping & Overlay Guidance 3.4 Data Handling and Marking Requirements 3.5 Documenting Control Selection and Securing Stakeholder Agreement 3.6 Continuous Monitoring Strategy & Control Selection Approval
5 Chapter 4: Implementation of Security and Privacy Controls
4.1 Developing the Implementation Strategy: Resourcing, Funding and Timeline 4.2 Identifying Control Types: Management, Operational, Technical and Functional Classes 4.3 System Security and Privacy Plan (SSP/SSPP) Development 4.4 Security Engineering Principles & Technical Control Implementation 4.5 Secure Baseline Configuration & System Hardening 4.6 Implementing Compensating and Alternate Controls 4.7 DevSecOps, SDLC Integration & Supply Chain Risk Management 4.8 Documenting Control Implementation: Policies, Procedures, Plans and Risk Registers
6 Chapter 5: Assessment/Audit of Security and Privacy Controls
5.1 Security Assessment Plan (SAP) & Assessor Independence 5.2 Assessment Methods, Objects & Depth/Coverage 5.3 Assessment Execution, Vulnerability Scanning & Testing 5.4 Preparing the Initial Assessment/Audit Report 5.5 Selecting Risk Responses: Avoid, Accept, Share, Mitigate, Transfer 5.6 Stakeholder Collaboration, Corrective Action and Reassessment 5.7 Security Assessment Report (SAR) & Risk Findings Analysis 5.8 Developing the Risk Response Plan: Prioritization and Resources
7 Chapter 6: System Compliance and Authorization
6.1 The Core Authorization Package & Supporting Artifacts 6.2 Plan of Action and Milestones (POA&M) Architecture & Management 6.3 System Risk Acceptance Criteria and Stakeholder Concurrence 6.4 Authorization Decision Process & Decision Types 6.5 Residual Risk Acceptance, Terms of Authorization & Continuous ATO 6.6 Documenting and Communicating the Compliance Decision
8 Chapter 7: Compliance Maintenance and Continuous Monitoring
7.1 Continuous Monitoring Strategy & Operations (NIST SP 800-137) 7.2 Configuration Management & Security Impact Analysis (NIST SP 800-128) 7.3 Incident Response and Contingency Activities in Sustained Compliance 7.4 Awareness, Training, Evidence Collection and Monitoring-Strategy Revision 7.5 Ongoing Remediation, POA&M Sustainment & Annual Reviews 7.6 Event-Driven Reauthorization & System Decommissioning
5.7 Security Assessment Report (SAR) & Risk Findings Analysis
Key Takeaways Explain This Topic AI
The Security Assessment Report (SAR) is the official deliverable of RMF Step 4 (Assess), documenting control effectiveness determinations ('Satisfied' vs. 'Other Than Satisfied') and contextualized risk ratings.
A control is determined to be 'Satisfied' only when evidence proves it is implemented correctly, operating as intended, and meeting required security outcomes; otherwise, it is recorded as 'Other Than Satisfied'.
Risk analysis per NIST SP 800-30 Rev. 1 synthesizes threat source capability, vulnerability exploitability (likelihood), and business/mission impact to determine qualitative risk levels.
Raw CVSS vulnerability scores must be contextualized into system risk ratings by accounting for existing compensating controls, architectural isolation, and operational environments.
The SAR serves as the empirical risk foundation for the Authorizing Official's (AO) authorization decision and directly populates the Plan of Action and Milestones (POA&M).
Last updated: August 2026
5.7 Security Assessment Report (SAR) & Risk Findings Analysis
The ultimate deliverable of RMF Step 4 (Assess) is the Security Assessment Report (SAR) (or Privacy Assessment Report [PAR]). The SAR consolidates the findings of the independent assessment team, provides an objective evaluation of control effectiveness, calculates contextual residual risk, and provides concrete recommendations.
Along with the System Security Plan (SSP) and the Plan of Action and Milestones (POA&M) , the SAR forms the tripartite Security Authorization Package submitted to the Authorizing Official (AO) in RMF Step 5 (Authorize) .
Analyzing Assessment Evidence: Satisfied vs. Other Than Satisfied
NIST SP 800-53A establishes a binary determination model for each assessed control objective: ┌─────────────────────────────────────────────────────────────────────────────┐
- │ CONTROL EFFECTIVENESS DETERMINATION │
- │ │
- │ ┌─────────────────────────────────┐ ┌─────────────────────────────────┐ │
- │ │ SATISFIED │ │ OTHER THAN SATISFIED │ │
- │ │ • Control implemented correctly │ │ • Control missing or incomplete │ │
- │ │ • Operating as intended │ │ • Misconfigured or failing │ │
- │ │ • Produces expected outcome │ │ • Lacks verifiable evidence │ │
- │ │ • Corroborated across evidence │ │ • Constitutes a formal DEFICIENCY│ │
- │ └─────────────────────────────────┘ └─────────────────────────────────┘ │
- └─────────────────────────────────────────────────────────────────────────────┘
- 1. Satisfied
Criteria: The assessment evidence demonstrates that the control or control enhancement is implemented exactly as specified in the SSP, complies with NIST SP 800-53 baselines, operates reliably across all operational scenarios, and produces the desired security outcome.
Action: No deficiency recorded; control is marked compliant.
2. Other Than Satisfied (Finding / Deficiency)
Criteria: The assessment reveals that the control is not implemented, partially implemented, misconfigured, failing to operate as intended, bypassed by operational workarounds, or lacks sufficient verifiable evidence.
Action: The assessor must document a formal Finding (Deficiency) in the SAR detailing the exact control gap, affected system components, potential threat exploits, likelihood, impact, and remediation recommendations.
Risk Findings Analysis and Scoring (NIST SP 800-30 Rev. 1)
A critical responsibility of the Security Control Assessor is contextualizing technical deficiencies into organizational risk. A raw technical vulnerability does not automatically equate to high organizational risk without considering threat exposure and mitigating factors. ┌─────────────────────────────────────────────────────────────────────────────┐
- │ RISK LEVEL DETERMINATION MATRIX │
- │ │
- │ LIKELIHOOD ▲ │
- │ Very High │ Low Moderate High VERY HIGH │
- │ High │ Low Moderate High HIGH │
- │ Moderate │ Low Moderate Moderate HIGH │
- │ Low │ Very Low Low Moderate MODERATE │
- │ Very Low │ Very Low Very Low Low LOW │
- │ └──────────────────────────────────────────────────────────► │
- │ Very Low Low Moderate High / Very High │
- │ IMPACT │
- └─────────────────────────────────────────────────────────────────────────────┘
- The Risk Formulation Chain
Risk is assessed by evaluating the interplay between four core factors per NIST SP 800-30 Rev. 1: R i s k = f ( Threat Likelihood , Impact Magnitude ) \mathbf{Risk} = f(\text{Threat Likelihood}, \text{Impact Magnitude}) Risk = f ( Threat Likelihood , Impact Magnitude )
Threat Event & Source: Identify the threat actor (adversarial cybercriminal, insider, system fault, natural disaster) capable of targeting the deficiency.
Vulnerability & Predisposing Conditions: The specific technical flaw (e.g., missing CVE patch) or operational circumstance (e.g., system hosted in an unmonitored server room) that facilitates exploitation.
Likelihood of Occurrence: Evaluated based on:
Threat Initiation / Capability: Adversary skill, motivation, and resource level.
Vulnerability Exploitability & Visibility: Ease of discovery and execution.
Existing Mitigations: Effectiveness of defense-in-depth safeguards.
Qualitative ratings: Very Low, Low, Moderate, High, Very High .
Magnitude of Impact: Evaluated based on the adverse consequence to organizational operations, mission capabilities, assets, individuals, or the Nation if the confidentiality, integrity, or availability (CIA) of the system is compromised:
Qualitative ratings: Very Low, Low, Moderate, High, Very High .
Raw CVSS Severity vs. Contextualized System Risk
Assessment Factor Raw Technical Severity (CVSS) Contextualized System Risk (SAR)
Focus Universal, intrinsic severity of a software flaw in isolation. Real-world risk to the specific organization within its operational environment.
Context Considered Constant across the world; assumes direct reachability and exploitation. Incorporates network segmentation, air-gaps, firewalls, compensating controls, and data sensitivity.
Example CVE-2024-XXXX with CVSS Base Score 9.8 (Critical) (Remote Code Execution in web server). System is completely isolated in an air-gapped SCIF with no external network connectivity; contextualized risk is downgraded to Low / Moderate .
- Governing Standard FIRST CVSS v3.1 / v4.0 NIST SP 800-30 Rev. 1 / SP 800-37 Rev. 2
- Structure of the Security Assessment Report (SAR)
A compliant SAR must follow a standardized structure to enable executive review by the AO and technical remediation by the system owner. ┌─────────────────────────────────────────────────────────────────────────────┐
- │ SECURITY ASSESSMENT REPORT (SAR) │
- │ │
- │ ┌───────────────────────────────────────────────────────────────────────┐ │
- │ │ 1. Executive Summary: High-level risk posture, summary table of │ │
- │ │ Satisfied vs. Other-Than-Satisfied controls, overall risk recommendation│
- │ ├───────────────────────────────────────────────────────────────────────┤ │
- │ │ 2. Assessment Methodology & Scope: Systems tested, tools used, │ │
- │ │ sampling criteria, assessment methods (Examine, Interview, Test) │ │
- │ ├───────────────────────────────────────────────────────────────────────┤ │
- │ │ 3. Detailed Findings & Deficiencies: Per-control analysis: │ │
- │ │ • Control ID & Name (e.g., IA-2(1)) • Finding Description │ │
- │ │ • Evidence Artifact Ref • Likelihood & Impact │ │
- │ │ • Contextual Risk Rating (High/Med) • Assessor Recommendations │ │
- │ ├───────────────────────────────────────────────────────────────────────┤ │
- │ │ 4. Initial Remediation Actions: Fixes applied during testing window │ │
- │ ├───────────────────────────────────────────────────────────────────────┤ │
- │ │ 5. Assessor Independence & Sign-Off: Lead SCA signature & credentials │ │
- │ └───────────────────────────────────────────────────────────────────────┘ │
- └─────────────────────────────────────────────────────────────────────────────┘
- Detailed Breakdown of SAR Sections
Executive Summary: Written specifically for the Authorizing Official (AO), Chief Information Security Officer (CISO), and Risk Executive (Function). Provides a concise, non-technical overview of the system's risk posture, highlights critical operational risks, and offers an informed recommendation regarding authorization.
Assessment Scope and Methodology: Documents the exact authorization boundary, testing dates, assessor credentials, scanning tools utilized (including tool version numbers and plugin feed dates), and the depth/coverage parameters applied.
Summary of Findings Table: An aggregated matrix categorizing control status across all NIST SP 800-53 control families (e.g., AC, AU, CM, IA, SC, SI), detailing the count of Satisfied vs. Other Than Satisfied controls.
Detailed Findings and Vulnerability Disclosures: Each deficiency is given an individual record detailing:
Control Identifier: (e.g., AC-2(3): Account Management | Inactive Accounts ).
Deficiency Summary: Plain-language description of the operational failure.
Evidence Reference: Exact file names, scan output snippets, log timestamps, or interview transcripts.
Root Cause Analysis: Why the failure occurred (e.g., lack of automated script, insufficient staffing, lack of training).
Likelihood, Impact, and Risk Rating: Justified qualitative scores per NIST SP 800-30.
Assessor Remediation Recommendations: Concrete technical or administrative steps to resolve the finding.
Initial Remediation Actions (RMF Task A-6): Documents any corrective actions immediately implemented by the system engineering team during the assessment window (e.g., patching a service and passing an immediate rescan), updating the finding status accordingly before report finalization.
Assessor Sign-Off and Handoff to RMF Step 5
Once the SAR is finalized:
Lead Assessor Sign-Off: The Lead SCA signs the document, certifying that the assessment was executed independently, objectively, and in compliance with the approved SAP.
Delivery to System Owner (ISO / ISSO): The ISO reviews the SAR findings and immediately drafts the Plan of Action and Milestones (POA&M) , defining milestones, assigned resources, and scheduled completion dates for every "Other Than Satisfied" finding.
Submission to Authorizing Official (AO): The complete Authorization Package (SSP, SAR, and POA&M) is formally submitted to the AO to drive the Step 5 authorization decision (ATO, ATO with Conditions, or DATO).