Inherent risk is the level of risk that exists before any controls or other responses are applied. It describes how exposed an organization is by the nature of its activities, data, and systems. Inherent risk is the starting point for risk assessment, and it is compared with residual risk, which is what remains after controls.
Why Inherent Risk Matters
Rating risk before controls shows where protection matters most. A system that stores sensitive customer data usually has higher inherent risk than an internal wiki, even if both are well protected today. Knowing the inherent level helps teams decide how much control effort a risk deserves and whether a control is carrying more weight than expected.
Inherent Risk vs Residual Risk
| Term | Meaning | Example |
|---|---|---|
| Inherent risk | Risk before controls | Production database reachable from the internet |
| Control | A response that lowers the risk | Network restrictions, multi-factor authentication, logging |
| Residual risk | Risk after controls | A lower chance of unauthorized access |
The ratings are illustrative. Each organization defines its own scale, such as low, medium, and high, and its own way of combining likelihood and impact.
How It Is Estimated
- Identify the asset, process, or system in scope
- Describe the threat or event that could cause harm
- Estimate likelihood as if no controls existed
- Estimate impact on the business and customers
- Combine the two using your documented method
- Record the result in the risk register
How Auditors Typically See It
SOC 2 does not prescribe a formula for inherent risk. Auditors generally look for a documented risk assessment process, consistent ratings, and evidence that results influenced which controls were chosen. Whether your method meets your criteria is a decision for your auditor.
Common Mistakes
- Rating inherent risk after considering existing controls, which blurs it with residual risk
- Using different scales for different teams
- Leaving out the reasoning behind a rating
- Never revisiting ratings after major system or vendor 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)