Home › Resources › Glossary › Evidence Reuse

Resources · Glossary

What is evidence reuse? One record for several frameworks

In shortEvidence reuse is the practice of collecting a piece of audit evidence once and using it for every requirement it genuinely satisfies, across controls, frameworks and audits. It depends on framework mapping and on storing evidence against the control. Reuse is valid only when the evidence fits each requirement and each audit's period.

What does evidence reuse mean?

An organisation with ISO 27001, SOC 2 and a customer audit is often asked for the same access review three times. Reuse means supplying it once, attached to the control, and letting each audit draw on it.

The limit is fit. Each audit has its own period and its own wording. Evidence that satisfies one may only partly satisfy another.

When is reusing evidence valid?

Same controlIt proves the same thing

Both requirements are met by the same control operating.

Right datesIt covers each period

The record falls inside each audit's period, or enough records exist to cover it.

Still trueIt is current

The system or process has not changed since the evidence was produced.

What does evidence reuse look like?

One quarterly access review used three times.

UseWhy it fits
ISO 27001 surveillance auditShows Annex A 5.18 operating in the quarter sampled
SOC 2 Type 2 examinationOne of four quarterly reviews in the period; the other three are also needed
Customer security questionnaireAnswers the question on periodic access review
Not reusable forA requirement about privileged access monitoring, which is a different control

This is an illustration written for this page, not a customer record.

What do frameworks say about evidence and periods?

FrameworkWhereWhat it asks for
ISO 27001Clause 7.5Documented information is controlled and available as evidence where and when needed.
SOC 2Type 2 reportEvidence must show the control operating throughout the examination period.
NIST CSF 2.0Informative referencesPublished mappings show where one outcome corresponds to requirements elsewhere.
ISO 27001Clause 9.2Each audit has its own scope and criteria, which decide what evidence is relevant.

References are to the current editions listed under Sources. Check the edition your auditor is using.

Where does evidence reuse go wrong?

01

Out of period

Last year's record is offered for this year's audit.

Instead: check dates against each audit's period.

02

Stretched to fit

Evidence for one control is offered for a different one.

Instead: reuse only where the same control is being tested.

03

Copies everywhere

The file is duplicated for each audit and versions drift.

Instead: store it once and link it.

How does QULDEX handle this?

Multi-Framework Audit Engine

One control and one piece of evidence count towards every framework they apply to.

See the module

Evidence Reuse: common questions

Will auditors accept reused evidence?

Yes, when it is relevant to the requirement they are testing and falls within their audit period. They judge each item on its merits.

Does evidence reuse need special software?

No, but it needs each record to be linked to a control and each control to be mapped to requirements. That is hard to maintain in folders and spreadsheets.

Can evidence from an internal audit be reused externally?

The underlying records can. The internal auditor's conclusions are useful context, but an external auditor reaches their own.

Ask each control owner once

Controls, evidence, findings and corrective actions in one audit workspace.

Schedule
Book a Demo