iso27diy-corp/Corpus/Various/Assessing reputational risks.md

15 lines
No EOL
1.2 KiB
Markdown
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

From a [LinkedIn post](https://www.linkedin.com/feed/update/urn:li:activity:7272490322453028864/) by [Mads Bundgaard Nielsen](https://www.linkedin.com/in/mbundgaard/)
1. Perform a Stakeholder analysis, mapping them on two dimensions:
a) Strategic importance: Stakeholder can influence path to strategic objectives
b) Incident sensitivity: Negative reaction is influenced by your incidents.
- Note the important and sensitive stakeholders.
2. Identify events that can impact your reputation with important stakeholders: breach, service disruption, delays, budget exceedance, ransomware, fraud, etc.
- Bear in mind: Not all event types evoke the same reaction from the same stakeholder.
3. List the possible impact from negative reactions (see notes for examples); Ask yourself “what would I see, if my reputation with `stakeholder` was diminished?”. 1-3 tangible metrics will probably immediately pop up, and if not, its probably not an important stakeholder after all.
4. Identify levers: What actions (preemptive or reactive) are you able to take or plan? Probably only a handful. The good news is that your levers almost certainly mitigate >90% of the negative reputation outcomes.
![](../ISMS/Reputation%20Risk%20Analysis.jpeg)