Vulcan’s risk algorithm intelligently incorporates different contextual attributes to produce a dynamic risk score for each vulnerability instance in your environment.
However, sometimes assets or vulnerabilities might occur under specific special circumstances, which would require you to manually determine their risk score, a vulnerability that would otherwise pose Critical risk, could be manually brought down to a Low if the asset it affects has a compensating control such as a firewall on it which would mitigate the vulnerability.
Manually editing risk
To manually edit a vulnerability instance's risk, follow these steps:
- Navigate to the vulnerability in question.
- Click the Assets tab
- Select the affected assets you want to change the risk for
- Click Edit risk for X assets
- In the Edit Risk popup, enter the risk score you want to apply to the affected assets.
- Optionally, you may add a comment detailing why you made the change.
- Click Save
- You've manually edited risk!
(3) - The assets tab with some affected assets selected:
(5) - The assets tab with some affected assets selected:
(8) - Risk edited!
Reverting manual edits
At any point, you may choose to revert any manual edits you made. When a vulnerability affects assets for which the risk score has been edited, the Revet X edits buttons appears.
Clicking the button will revert all the changes in the current view to their original, calculated risk.
- Changes might take a few minutes to be reflected system-wide.
- Changing the risk score will affect SLAs. It might cause a breaching vulnerability to become compliant or vice-versa.
- By default, all roles can edit risk scores. If you want to restrict this functionality, see Role Based Access Control.