Control maintenance - Proof
Along with testing, implementation, freshness, and past due issues, proof is another important factor when determining the overall health of a control. There are several methods you can use to ensure that your proof is always up-to-date:
Reusing proof
If you manage more than one compliance framework, it's likely that the proof you need to support a control in Program A is the same proof you need to support the same control in Program B.
Rather than uploading the proof to two different frameworks (and having to maintain the same piece of proof, doubling your work) you can create a label with that piece of proof and link it to both controls. This way, if your proof changes, e.g. log files have been updated, you only need to update the proof in the label. See Labels.