InfoSec-Specific Executive Development for CISOs and Aspiring Security Leaders.
Live Faculty-led instruction and interactive labs to build you and your team's InfoSec skills
Describing and documenting an enterprise’s risk appetite is complicated, because usually it can only be done in qualitative or subjective terms. A common measure of risk appetite can be what the enterprise decides to spend to mitigate risks.
That said, some key principles can be documented and serve as guidance to organizational units as they try to decide how to allocate resources against the enterprise’s key information security risks. This piece explains how to use a risk register
to document leadership’s approach to risk and create an effective enterprise risk appetite statement.
This begins with the general topic of risk management, which is key to how the enterprise organizes and runs an information security program. Often, organizations create a risk management program and use that program to help establish where they need
to focus their information security resources. Typical risk management programs focus on:
Constructing a risk appetite from the risk register is relatively straightforward. Specifically, the highest risks from the risk register represent the risks the enterprise determined warrant the most attention. And, most importantly, those highest risks
already reflect substantive input from the executives, so they are well-aligned with leadership strategies and goals.
A risk appetite can be discerned simply by considering what you plan to do or want to do and measuring it against the highest risks to determine whether it moves the needle on them. Clearly, if the matter being considered makes one or more of the highest
risks worse, the executives could be more amenable to spending resources to mitigate that effect.
In looking at this through the optics of a risk appetite statement, an example of a typical statement boils down to:
The approach outlined above has one nuance: It does not fully consider the benefits of accepting a risk even if it is high. It simply focuses on addressing all the worst risks in the risk register and avoiding any actions that may exacerbate them.
However, there may be situations when a proposed action has such significant business benefits it is worth pursuing, even in the face of having to accept very high risk in the process. Typically, in every case where a proposed business plan or action
engenders very high risk, the business decides to take actions to mitigate that risk to bring it down to tolerable levels. But, that does not necessarily mean that such a situation may never happen. One option is to address it in a risk appetite statement
is to add a fourth paragraph. An example of which may read something similar to the following:
"Where a proposed action or activity makes the worst risks worse or elevates a lower-level risk to a high-risk category, and suitable mitigations are unavailable, ineffective, or prohibitively expensive, the impact of accepting the risk shall be measured
against the business benefits expected to result from the proposed action or activity. In rare cases, the latter may outweigh the former, but such a judgment shall only be rendered by senior executive leadership."
Finally, the enterprise may have some risks it wishes to declare “inviolate.” That is, the enterprise is unwilling to accept any actions that may worsen them. Examples can include regulatory risks, i.e., risks associated with a regulator citing
the enterprise for quality of care, protection of patient data under the Health Insurance Portability and Accountability Act (HIPAA) and so on.
Another example could be risks associated with violating the Payment Card Industry Data Security Standard (PCI-DSS) because that could imperil the use of credit cards for payment. The enterprise should list such risks and could include a final paragraph
in the risk appetite statement to cover them:
It is critically important the enterprise risk register truly reflect the full input of executive leadership or else the risk appetite statements cited above will have no real effect. Leadership must be fully committed to the risk register, and that can
only happen if they have a key hand in its formulation. InfoSec leaders should be able to trace risk register contents back to the areas of concern or worries the executives expressed, or you could run the risk of the contents possibly being dismissed
as just an academic exercise.
Although reasonable efforts will be made to ensure the completeness and accuracy of the information contained in our blog posts, no liability can be accepted by IANS or our Faculty members for the results of any actions taken by individuals or firms in connection with such information, opinions, or advice.
October 19, 2021
By IANS Faculty
Continuous compliance requires continuous monitoring and validation of controls in the environment, as well as integration with governance, risk management and compliance tools and platforms. Understand the processes, tools, stakeholders and focus required for a best practice continuous compliance program.
October 14, 2021
Learn how the DDoS threat is evolving and get a step-by-step playbook to ensure your organization is protected against DDoS attacks and has a response plan in place.
October 12, 2021
Uncertain how to secure your M365 environment? Our Faculty identify and explain the five primary areas of M365 that will provide the best security return-on-investment with the least user experience impacts.