# Question: Where to track exceptions that apply to multiple modules

**URL:** https://discussions.eramba.org/t/question-where-to-track-exceptions-that-apply-to-multiple-modules/1477
**Category:** Forum - Software
**Created:** [March 27, 2020, 10:10pm UTC](https://discussions.eramba.org/t/question-where-to-track-exceptions-that-apply-to-multiple-modules/1477 "2020-03-27T22:10:27Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![matthew.dovie](https://discussions.eramba.org/user_avatar/discussions.eramba.org/matthew.dovie/32/1021_2.png) [@matthew.dovie](https://discussions.eramba.org/u/matthew.dovie)
#### Post date: [March 27, 2020, 10:10pm UTC](https://discussions.eramba.org/t/question-where-to-track-exceptions-that-apply-to-multiple-modules/1477/1 "2020-03-27T22:10:27Z")

</div>

Since exceptions are tracked separately in each module, I’m wondering where others log their exceptions that are applicable to all modules.

Example: I have a risk of _unsupported operating system_, I could log the exception in the risk module that I have applications that do not support the latest OS version, or I could track this at the security policy stating that we must patch and keep our systems up-to-date. I could also track this at the control level for either a patch management or vulnerability management control, and finally, I could also track this at the compliance item, specifically thinking ISO (managing technical vulnerabilities). Ideally, I would track all exceptions in one module and then have the ability to map the exception within each module back to the parent, but my methodology has been to look at the highest level and apply the exception there. In this case that would be at the policy level. What are you guys doing?

---

<div class="post-metadata">

### Author: ![sge](https://discussions.eramba.org/user_avatar/discussions.eramba.org/sge/32/1380_2.png) [@sge](https://discussions.eramba.org/u/sge)
#### Post date: [March 28, 2020, 9:09am UTC](https://discussions.eramba.org/t/question-where-to-track-exceptions-that-apply-to-multiple-modules/1477/2 "2020-03-28T09:09:43Z")

</div>

I would register this exemption in the policy module only.  
As I see it is a policy (telling you keep things updated) the only thing you really are making an exemption of.  
When doing asset risk management on the asset you find it vulnerably and will for sure make a control ensuring to update the asset.  
And if possible relate all together with filters
