Residual risk is the level of risk that remains after an organization applies controls or other responses to an identified risk. Inherent risk is the level before any response. Residual risk is what is left.
In simple terms, if a risk starts out high and your controls reduce it, the part that still exists is the residual risk. Leadership decides whether that remaining level is acceptable.
Why Residual Risk Matters
- It shows whether controls reduced a risk enough to stay within the organization's tolerance
- It supports a documented decision to accept, reduce further, transfer, or avoid a risk
- It helps prioritize which gaps need attention first
- It gives auditors a record that risk decisions were reviewed, not just listed
Inherent Risk vs Residual Risk
| Term | Meaning | Example |
|---|---|---|
| Inherent risk | Risk before controls | Customer data stored in a cloud database |
| Control | A response that lowers the risk | Encryption, access limits, and monitoring |
| Residual risk | Risk after controls | A smaller chance of exposure from a misconfiguration or stolen credential |
The ratings above are illustrative. Each organization defines its own scale, such as low, medium, and high, in its risk assessment method.
How It Fits Into Risk Management
- Identify the risk and rate its inherent level
- Choose a risk treatment
- Apply controls and estimate the level that remains
- Record the result in the risk register
- Have the right owner accept the remaining risk or request further action
How Auditors Typically See It
SOC 2 does not require a specific residual risk formula. Auditors generally look for evidence that risks were identified, responses were chosen, and decisions were reviewed by someone with authority. Whether your approach meets your criteria is a decision for your auditor.
Common Mistakes
- Rating residual risk without recording how the rating was reached
- Accepting a risk without a named approver or review date
- Assuming a control lowers risk without any evidence it operates
- Never updating residual ratings after incidents or system changes
How AuditFlo.co Helps
AuditFlo.co helps teams keep audit-period evidence collection records, such as control evidence from connected systems. It does not rate your risks, does not issue SOC 2 reports, does not certify compliance, and does not replace auditors.
Sources
- NIST SP 800-30 Rev. 1, Guide for Conducting Risk Assessments
- ISO 31000, Risk management guidelines
- AICPA, Trust Services Criteria (risk assessment criteria, CC3 series)