Published Updated

Keep each completed control test connected to the evidence actually reviewed. Governance, risk, and compliance (GRC) workflows record the test, its result, any finding, and the response. Records management carries the selected evidence through classification, access, retention, holds, and disposition. Those responsibilities can operate within one application or across connected systems.
The design question is how that connection survives change: a new export replaces the working file, a policy is revised, a finding closes, or the evidence reaches its retention date. A later reviewer should still be able to identify the selected records and understand the decision made from them.
GRC platforms can include document capabilities. For example, IBM OpenPages 9.2 documents version control and file locking for attachments. Assess the configured repository against the actual review and record-lifecycle requirements before adding another application.
If the current platform meets those requirements, preserve a clear path from the test to its evidence. A connected records application can fit when the organisation needs coordinated retention, holds, access, or disposition across evidence from several systems. The integration should make the chosen ownership visible to reviewers and records officers.
A reviewer needs the population, period, method, and documents used for the test. Record a checksum or stable version reference for file identity alongside the reviewer's assessment of scope and adequacy. Keep an explicit evidence selection when a folder or dashboard continues to change.
| Decision or link | What stays connected |
|---|---|
| Control and test run | Control ID, test period, assessed population, method or policy version, owner, and reviewer. |
| Source evidence | Record ID and version, originating system, generation time, query or export parameters, source identity, and file checksum where used. |
| Reviewed package | A list of the exact selected versions, completeness or access exceptions, review decision, and the record of who considered them. |
| Finding and follow-up | The original result, issue reference, remedial action, later validation evidence, and the authorised closure decision. |
| Record lifecycle | Classification, applicable retention rule and trigger, selected holds, disposition review, and documented follow-through. |
Use durable, authenticated references to the selected records. Temporary download links serve delivery and can expire; the presigned URL guide explains that separate access window. Make it possible to request the authorised version again using its record identity.
Capture the source and version references, review period, population, method, and missing items.
Retain the assessment, finding, reviewer decision, and any later validation as related records.
Keep access, retention, hold, and disposition decisions connected to the selected evidence.
A corrected export can become new evidence for a follow-up review. Retain the earlier export and result so the history explains why the finding was raised. Distinguish the original test outcome, the latest validation outcome, and the current remediation status.
The cyber risk register guide describes how those treatment and test records inform the separate risk decision. The evidence connection should support both the current summary and the assessment made at an earlier point in time.
Select file-retention controls according to the approved evidence policy. Amazon S3 Object Lock applies WORM retention to specified object versions. A new version can be created while an earlier version remains protected, so the reviewed package must identify the intended version.
Governance-mode protection includes a privileged bypass mechanism. Restrict and govern that authority as part of the deployment's access model. Keep application metadata, evidence selections, and review history under their own configured controls; the selected stored files and the current GRC status have different purposes.
Map hold scope to actual record identities and confirm the result in each relevant repository. The records officer needs to know which files are held, which retention periods still apply, and which records are eligible for disposition review. Closing a GRC task should trigger the agreed follow-up process, with a separate authorised decision for record disposal.
This fictional organisation requires quarterly privileged-access review under its own policy. Test TST-00041 covers a defined quarter and population, with a user export, manager attestations, and exception decisions. The retention rule and approval roles are chosen for the example; they are not universal audit requirements.
The review owner records the source system, export time, query scope, policy revision, and selected document versions. Package PKG-00041 links that evidence to the GRC test. A reviewer checks completeness and access before assessing the control.
The reviewer finds two unresolved privileged accounts and records a failed test with finding FND-00041. The package retains the export and decisions used for that result. A later policy release or refreshed export creates a new reference while the original selection stays identifiable.
The operations team removes the access and provides new implementation evidence. The appointed reviewer validates that change and records the follow-up outcome. The finding can then be resolved through its configured approval, while the original test remains a historical failed result.
An investigation requires preservation of the original review and related follow-up. The responsible officer identifies the affected records, applies the hold, and checks that the held scope is excluded from disposition selection. The case records the hold reference and any related repository actions.
When a normal retention date later arrives, the held records remain excluded. Other eligible records can enter the configured disposition review. After a hold is released, the officer still checks remaining retention and review requirements before authorising an action. A resolved GRC finding and retained evidence can therefore have different lifecycle states.
This preserves both the original exception and the work that resolved it. For the broader removal decision, see coordinating document deletion with connected search and systems.
For an application-access finding, use document-API tests to define allowed and denied requests. Retain the checked fixture, result and remediation evidence with the control test’s selected records.
A reviewable GRC result identifies the evidence considered and the decision made from it. Carry that connection through policy changes, remediation, retention, holds, and disposition so a current status can still be explained from its history.
The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.
Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.
For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.