Establishing risk appetite is key to effective risk management

Mandy Pote, Director, Cyber Risk Services, Coalfire

The mission of an enterprise risk management program is to respond to and monitor risks to the enterprise’s operations and objectives. In order to properly respond to and monitor risks, the enterprise must establish risk appetite thresholds. Well-established and well-communicated risk appetite thresholds will ensure that risks are mitigated consistently at all levels of the organization.

Often, the terms “risk appetite” and “risk tolerance” are used interchangeably. However, these terms, while closely related, are distinct:

  • Risk Appetite – High-level statement(s) that determines the amount of risk an organization is willing to accept
    Example: Will not accept risks that could result in a data breach
  • Risk Tolerance – Typically quantifiable, sets the boundaries that the organization is willing to stray from risk appetite
    Example: Will not accept risks that could result in a data breach of more than 1,000 customer records

In response to findings from a risk assessment, risk owners can make educated risk decisions, utilizing the enterprise’s risk appetite and tolerance as guardrails. Consider two risk assessment findings in the examples below:

  1. One million unencrypted customer records are stored on the open network share drive
  2. Hundreds of unencrypted marketing materials are stored in a SaaS storage provider

Since both scenarios include a potential risk of data breach, the risk owner will want to ensure that the risk response actions align with the organization’s goals and objectives. By considering the enterprise’s risk tolerance statement, “will not accept risks that could result in a data breach of more than 1,000 customer records,” only the first risk is not within the threshold. Therefore, the first risk should be mitigated until it is within the bounds of the organization’s risk tolerance level.

One of the key challenges is always enforcing and communicating risk appetite across the entire enterprise. First, management must develop risk appetite statements that are relevant to business processes and systems. This will allow business unit leaders to effectively execute and enforce risk appetite statements within risk management processes. Second, management should ensure that risk appetite strategy is consistently reflected in organizational communications, such as business goals, metrics reporting, etc. Business unit leaders will be more likely to implement risk mitigation activities into daily processes if they receive reliable and informative communication from leadership.

In conclusion, establishing enterprise risk appetite statements ensures that business unit leaders throughout the enterprise are operating against the same metrics and goals. Risk appetite and supporting risk tolerance statements should serve as guidelines for both strategic and tactical decision making throughout the risk management lifecycle.

Mandy Pote


Mandy Pote — Director, Cyber Risk Services, Coalfire

Recent Posts

Post Topics



Accounting Agency AICPA Assessment assessments ASV audit AWS AWS Certified Cloud Practitioner AWS Certs AWS Summit bitcoin Black Hat Black Hat 2017 blockchain Blueborne Breach BSides BSidesLV Burp BYOD California Consumer Privacy Act careers CCPA Chertoff CISO cloud CMMC CoalfireOne Compliance Covid-19 credit cards C-Store Culture Cyber cyber attacks Cyber Engineering cyber incident Cyber Risk cyber threats cyberchrime cyberinsurance cybersecurity danger Dangers Data DDoS DevOps DevSecOps DFARS DFARS 7012 diacap diarmf Digital Forensics DoD DRG DSS e-banking Education encryption engineering ePHI Equifax Europe EU-US Privacy Shield federal FedRAMP financial services FISMA Foglight forensics Gartner Report GDPR Google Cloud NEXT '18 government GRC hack hacker hacking Halloween Health Healthcare heartbleed Higher Education HIMSS HIPAA HITECH HITRUST HITRUST CSF Horror Incident Response interview IoT ISO IT JAB JSON keylogging Kubernetes Vulnerability labs LAN law firms leadership legal legislation merchant mobile NESA News NH-ISAC NIST NIST 800-171 NIST SP 800-171 NotPetya NRF NYCCR O365 OCR of P2PE PA DSS PA-DSS password passwords Payments PCI PCI DSS penetration Penetration Testing pentesting Petya/NotPetya PHI Phishing Phising policy POODLE PowerShell Presidential Executive Order Privacy program Ransomware Retail Risk RSA RSA 2019 Safe Harbor Scanning Scans scary security security. SOC SOC 2 social social engineering Spectre Splunk Spooky Spraying Attack SSAE State Stories Story test Testing theft Virtualization Visa vulnerability Vulnerability management web Wifi women XSS