Managing the Evidence Repository (IT Controls Assurance)
The Evidence Repository allows users to manage evidence records after initiating their testing procedures. You can create evidence records automatically or manually.
To automatically create evidence records, you must allow the Primary Controls or Control Procedures Automatic Evidence Collection Data Feeds to run on Primary Controls or Control Procedures records. For more information, see Creating Primary Controls (Controls Assurance Program Management) and Creating Control Procedures (Controls Assurance Program Management).
You can manually create evidence records and attach related controls through the Evidence Repository application.
Here are the tasks to manage the Evidence Repository:
-
Manually create evidence by providing the contributors and read-only users, and associate Primary Control records to the Evidence Repository.
-
Submit or reassign evidence by uploading evidence files, reviewing the record, and either submitting for review or reassigning the record.
-
Review evidence and either approve and publish the record or request more information.
-
Modify existing evidence. Only record owners or users with contributor permissions can modify existing Evidence Repository records.
When you re-initiate the workflow process for an Evidence Repository record, Archer checks out the record and creates an archived point-in-time version of the document in the Version History section. While the record is checked out, other users cannot modify it. When the user has completed their edits, they must submit the record for review. The record then cycles through the advanced workflow again.
Download the source file of the diagram here: IT Controls Assurance Evidence Repository Diagram
