Splitting Control Implementations and Evidence Tasks
You can split control implementations and evidence tasks when a single record no longer meets the needs of multiple frameworks, business units, or owners. Splitting allows you to create distinct records with tailored language, ownership, or evidence requirements.
To split control implementations
In some cases, you may have a control implementation that is linked to many different inventories. Use the split control implementation flow to split the single control implementation (and evidence) into individual control implementations, one for each inventory linked to the shared control.
To split evidence tasks
In some cases, you may have evidence tasks linked to many different inventories. Use the split evidence tasks flow to split the single evidence task into different evidence task implementations that you can manage separately. When evidence tasks are split, each inventory maintains its own evidence implementation.
- Adding inventories
-
When a related inventory is added, a new evidence implementation is created. If an evidence implementation already exists for that inventory, it is reused and linked.
- Removing inventories
-
When the related inventory is removed, the link between the control implementation and the evidence implementation for that inventory is removed. If no other control implementations are using that evidence, it can be deleted.