# Feature - Update a compliance package with an import

**URL:** https://discussions.eramba.org/t/feature-update-a-compliance-package-with-an-import/262
**Category:** Forum - Software
**Created:** [May 5, 2017, 8:49am UTC](https://discussions.eramba.org/t/feature-update-a-compliance-package-with-an-import/262 "2017-05-05T08:49:51Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![njaehnert](https://discussions.eramba.org/letter_avatar_proxy/v4/letter/n/b5e925/32.png) [@njaehnert](https://discussions.eramba.org/u/njaehnert)
#### Post date: [May 5, 2017, 2:57pm UTC](https://discussions.eramba.org/t/feature-update-a-compliance-package-with-an-import/262/2 "2017-05-05T14:57:27Z")

</div>

This is a difficult one because for historical purposes, you may have been compliant with (using your example) HITRUST 8.0. Now, HITRUST has changed one of the controls and made it more strict, so in 8.1 you do not comply.

Whatever we decide to do in Eramba should definitely keep the historical/previous version for reference. I have a bunch of other thoughts/ideas around this topic but unfortunately have to run off to a meeting. Will try to put more down to paper and post them here later.

Thanks,

-Noah

---

_[View the full topic](https://discussions.eramba.org/t/feature-update-a-compliance-package-with-an-import/262)._