Risk treatment is the process of deciding how to respond to an identified risk. Common responses are to reduce it, accept it, transfer it, or avoid it, and the decision is recorded along with an owner.
Risk treatment comes after a risk assessment. The assessment finds and rates risks. Treatment decides what to do about them, and the outcome is usually tracked in a risk register.
In simple terms, risk treatment answers:
- What will we do about this risk?
- Who owns the decision?
- How will we know the response worked?
The Four Common Responses
| Response | Meaning | Example |
|---|---|---|
| Reduce (mitigate) | Add or strengthen controls | Require multi-factor authentication for admin accounts |
| Accept | Knowingly keep the risk | A low-impact risk where the cost of a control outweighs the benefit |
| Transfer (share) | Move part of the impact to another party | Cyber insurance or a contract term with a vendor |
| Avoid | Stop the activity that creates the risk | Discontinue a risky feature or retire a system |
Different frameworks use slightly different names. ISO/IEC 27001 uses a risk treatment plan, and NIST uses risk response.
Why Risk Treatment Matters
- It turns a list of risks into decisions and actions
- It shows that leadership reviewed and approved the remaining risk
- It links risks to the controls meant to reduce them
- It gives an audit trail for risks that were accepted
Example Evidence
| Activity | Example evidence |
|---|---|
| Decision | Register entry showing the chosen response |
| Approval | Sign-off from the risk owner or management |
| Implementation | Tickets for new controls and completion dates |
| Review | Dated register updates showing reassessment |
How Auditors Typically See It
SOC 2 criteria on risk assessment ask how an organization identifies and responds to risks to its objectives. Auditors commonly look for evidence that risks were evaluated, that a response was chosen, and that management reviewed the result. The specific format is your choice.
Common Mistakes
- Listing risks without recording a decision
- Accepting a risk with no named approver
- Never revisiting accepted risks
- Treating a vendor contract as a complete transfer of responsibility
How AuditFlo.co Helps
AuditFlo.co helps teams retain audit-period evidence collection records, such as tickets that show control work from connected systems. It does not decide how you treat a risk, does not issue SOC 2 reports, does not certify compliance, and does not replace auditors.
Sources
- ISO/IEC 27005, Information security risk management
- NIST SP 800-30 Rev. 1, Guide for Conducting Risk Assessments
- AICPA, Trust Services Criteria (2017, with revised points of focus 2022): criteria CC3.1 to CC3.4