Evidence has a shelf life. Most systems treat it as permanent.
A penetration test report is compelling evidence in March and worthless in December. An access review from two org changes ago proves nothing. Govrly treats evidence as something requested, reviewed, linked, and eventually expired — not as a file that was uploaded once and never looked at again.
This page describes how we approach this work and how Govrly supports it. Where regulatory requirements are mentioned, confirm what applies to your organisation against the source documents published by the relevant authority.
What is evidence management?
From the compliance programmes we build and run in Saudi Arabia: in our work, Evidence management is the discipline of collecting, reviewing, and maintaining the artefacts that prove your controls actually operate. It is distinct from storing documents: evidence is requested from a named owner against a deadline, reviewed before it is accepted, linked to every requirement it satisfies, and given a validity period after which it must be collected again.
The difference between a document library and an evidence library is review and expiry. A folder of uploaded files tells you something was submitted. An evidence library tells you what was submitted, who provided it, who checked it, which requirements it supports, and whether it is still current today.
That last question is the one that decides assessments. Self-declared status without supporting evidence is the most common finding in Saudi regulatory assessments — and the second most common is evidence that exists but has aged past the point of meaning anything.
The evidence lifecycle
Five stages. Most tools implement only the second one, which is why evidence libraries decay so quietly.
From a named owner, with context explaining what is needed and a due date attached.
The owner supplies the artefact — a report, a log extract, a screenshot, a signed record.
Checked by someone other than the owner where possible. Until this happens it is a file, not evidence.
Attached to every requirement it satisfies, across every framework in scope.
A validity period triggers recollection before the artefact quietly stops proving anything.
Stage 3 and stage 5 are what separate an evidence library from a document dump. Without review, nobody has confirmed the artefact actually shows what it claims. Without expiry, the library slowly fills with material that was true once.
How long evidence stays valid
Different artefacts age at very different rates. Treating them all the same is why an assessor finds a three-year-old screenshot supporting a live control.
These are common practice, not regulatory rules. Your validity periods should follow your own risk assessment and any cadence your supervisor has communicated to you.
| Evidence type | Typical validity | Why it ages |
|---|---|---|
| Penetration test report | Annual | Tests a point-in-time state. Any material change to the environment invalidates the conclusion. |
| Access review record | Quarterly | Joiners, movers, and leavers change the picture continuously. |
| Vulnerability scan | Monthly | New vulnerabilities are published daily; last month's clean scan says nothing about today. |
| Approved policy | Annual review | Stable, but an unreviewed policy past its review date is itself a finding. |
| Awareness training records | Annual | New staff arrive continuously; last year's completion rate excludes them. |
| Backup restoration test | Periodic | Proves recovery worked on the systems as they existed on the test date. |
| Configuration baseline | On change | Valid until the configuration changes, which may be tomorrow. |
Collect once, satisfy many
One artefact, reviewed once, supporting a requirement in four frameworks at the same time.
Requested from the security lead with a due date, reviewed on receipt, and linked to every requirement it supports. Requested once — not four times by four different people.
Supports the applicable control within Cybersecurity Defense.
Evidences the relevant subdomain at its assessed maturity level.
Supports the domain at the entity's assigned compliance level.
Attached to the corresponding Statement of Applicability entry.
The saving compounds. In a programme carrying four frameworks, an organisation without shared evidence asks its security lead for the same report four times, in four formats, on four schedules — and gets four slightly different answers.
Where evidence collection goes wrong
- 01/07Evidence is collected in the weeks before an assessment
Assembled retrospectively from systems that have changed since. What gets submitted describes a state that no longer exists on the day it is read.
- 02/07Uploaded is treated as accepted
A file lands in a folder and the control is marked supported. Nobody checked whether the artefact actually shows what the control claims.
- 03/07The same artefact is requested repeatedly
Compliance asks in March, internal audit asks in June, the regulator asks in September — all for the same report, from the same overloaded person.
- 04/07Nothing expires
A screenshot from 2023 still sits against a live control. It was true once, and nothing in the system flagged that it stopped being true.
- 05/07Evidence lives where the requester left it
Some in a shared drive, some in an email thread, some in a ticketing system. Assembling a submission becomes an archaeology exercise.
- 06/07The owner has moved on
The only person who knows what an artefact was meant to prove has changed role, and the file has no context attached.
- 07/07Sensitive material is over-shared
Evidence often contains system detail, personal data, or findings. Collected into an uncontrolled folder, it becomes its own exposure.
Evidence management in Govrly
Evidence management is one layer. The control library, the risk register and audit lifecycle, privacy records, and vendor assessments are separate use cases drawing on the same underlying records — linked below rather than duplicated here.
Evidence is requested from a named person with an explanation of what is needed and why, and a due date that can be tracked and escalated rather than chased by email.
An artefact is reviewed before it counts as control support, with the reviewer distinct from the owner wherever the structure allows. Until then it is a file, not evidence.
Attached to every requirement it satisfies across every framework in scope, so it is collected once and counts everywhere.
Each item carries a validity period, so recollection is triggered before the artefact silently stops proving anything.
The full trail is preserved — requested by, provided by, reviewed by, and when — which is precisely what an assessor traces.
Because evidence is current and already linked, an assessment pack is compiled from approved records rather than built from scratch under deadline.
What actually counts as evidence
Assessors distinguish between three things that organisations often submit interchangeably.
Most programmes we assess are strong on design artefacts and weak on operating artefacts. That gap is the single most common reason a control scores lower than the team expected.
A statement that the control is in place. This is what a self-assessment spreadsheet contains, and on its own it carries almost no weight in an assessment.
A policy, a procedure, a configuration standard. It demonstrates the control was designed — not that it operates. Necessary but not sufficient.
A log extract, a completed review record, a test result, a ticket showing the process ran. It shows the control operated on a specific date, which is what an assessor is looking for.
Moving to continuous collection
- 01/07Start from your highest-value artefacts
The handful of items that support the most requirements — the penetration test, the access review, the training records. These deliver the most reuse for the least effort.
- 02/07Give every evidence item a named owner
The person who genuinely produces it, not the compliance manager who chases it. Chasing is a symptom of ownership sitting in the wrong place.
- 03/07Set a validity period on each type
Based on how quickly that artefact ages, not on a single uniform cadence for everything.
- 04/07Separate the reviewer from the owner
Wherever the structure allows it. Self-reviewed evidence is the weakest link in most collection processes.
- 05/07Link each artefact to every requirement it supports
Once, at review time. This is the step that stops the same request going out four times.
- 06/07Shift collection to the operating rhythm
Evidence produced as operations run, rather than assembled before a deadline. This is the whole point, and it takes a cycle or two to establish.
- 07/07Control access to the library itself
Evidence contains system detail and sometimes personal data. It needs the same access discipline as the systems it describes.
Evidence management — FAQs
The discipline of collecting, reviewing, and maintaining the artefacts that prove your controls actually operate. Evidence is requested from a named owner against a deadline, reviewed before it is accepted, linked to every requirement it satisfies, and given a validity period after which it must be collected again.
Assessors weigh three things differently. An assertion that a control is in place carries almost no weight alone. A design artefact — a policy, a procedure, a standard — shows the control was designed but not that it operates. An operating artefact — a log extract, a completed review record, a test result — shows the control actually ran on a specific date, and that is what an assessment is looking for.
It depends entirely on the artefact. A vulnerability scan ages within weeks, an access review within a quarter, a penetration test within a year, and a configuration baseline the moment the configuration changes. Applying one uniform cadence to everything is why assessors find aged artefacts supporting live controls. Validity periods should follow your own risk assessment and any cadence your supervisor has set.
Because an uploaded file is not evidence until someone has confirmed it shows what the control claims. Without a review step, a control can be marked supported by an artefact that is incomplete, out of scope, or from the wrong period — and nobody discovers that until an assessor does.
Yes, and this is where most of the effort saving comes from. A single penetration test report can support the NCA ECC control, the SAMA CSF subdomain, the CST CRF control, and the ISO 27001 Annex A entry at the same time — requested once from one owner, reviewed once, and linked to all four.
Review and expiry. A document library tells you a file was uploaded. An evidence library tells you what was submitted, who provided it, who checked it, which requirements it supports, and whether it is still current today. The last question is the one that decides assessments.
The person who genuinely produces it — the engineer who runs the scan, the manager who performs the access review — not the compliance manager who chases it. Persistent chasing is usually a symptom of ownership sitting with the wrong person.
Because the pack is assembled rather than manufactured. When evidence is already current, already reviewed, and already linked to requirements, preparing for an assessment becomes a compilation task instead of a collection round conducted under deadline across several departments.
No. Evidence management is collecting and maintaining the artefacts that show controls operate. Audit independently tests whether they genuinely do. Audit draws on the evidence library, which is why fieldwork can begin with testing rather than with a fresh document request.
Evidence often contains system detail, findings, and sometimes personal data, so the library needs the same access discipline as the systems it describes. Access is scoped by role and, for multi-entity organisations, isolated per entity so evidence never crosses an entity boundary.
Collect it once. Prove it whenever asked.
Requested from an owner, reviewed before it counts, linked to every requirement, and renewed before it goes stale.
