Evidence

Keeping a redaction audit trail

If a requester complains, your notes are the case you put to the ICO. Write down the decision, the reason and the decision maker as it happens.

Last reviewed against Information Commissioner's Office, GOV.UK and DLA Piper. Sources

A tall server rack with rows of lights

Why record

Defending a choice later

On other people's data, the ICO wants you able to defend each choice, and so to note what you decided, why, and whether you tried for consent or deliberately did not [1]. Exemptions carry the same expectation: reasons on file, ready to be explained [3].

What to log

Five entries per request

A request file should show:

  1. 1

    The date received and the deadline you worked out [4].
  2. 2

    What was searched, and any limit applied to the search.
  3. 3

    Each item withheld or redacted, with the ground relied on.
  4. 4

    The prejudice identified, where the exemption depends on it [3].
  5. 5

    Who reviewed the pack, and when it went out.

The ICO also looks for notes of any clarification exchange, including the dates you asked and the date the person replied [4].

Prejudice

Be specific

Some exemptions turn on prejudice. For those the ICO wants three things written down: the particular prejudice, a clear link from disclosure to that prejudice, and why the harm would be real and substantial [3]. A bare note saying "exempt" falls well short.

A useful test

Imagine a colleague who never saw the request reading your note. Would they reach the same decision? If not, add the missing reasoning.

A wireless signal above a padlock

Where it lives

One place, one owner

Keep the log beside the request file rather than in personal notebooks or inboxes. Name one person who checks that every closed request has a complete entry. A log that only some staff complete tells you little when a complaint arrives.

A cloud with a vault dial at its centre

Retention

Decide how long to keep it

No page consulted for this guide sets a retention period for these notes. Set one in your own policy, write it down, and keep the log for as long as a complaint about the response might reasonably arrive.

A person holding two chain links apart

Next

Add the review step

An audit trail is easier to keep when a second reader signs off each pack. See the review workflow.

How CyPro can help

Need a hand getting ready?

Reading the rules is one job. Mapping them to your organisation, closing the gaps and showing the evidence are several more. CyPro's consultants can take any of them off your plate.

Security lead advising a board

Fractional CISO for the board

A senior security lead who advises the board on what to fix first, what to accept and what to tell customers, and owns the decision record.

More on cypro.co.uk
Penetration tester probing an application for weaknesses

Penetration testing

A focused test of your systems and the controls around them, so you know they hold before an attacker finds out for you.

More on cypro.co.uk
Cyber security consultants planning hardening work

Hardening and segmentation

Our consultants put the controls in place that limit the damage when something is missed: firewall rules, network isolation and tighter admin access.

More on cypro.co.uk
Security analysts monitoring systems around the clock

24/7 security monitoring

Our SOC analysts watch your systems day and night for the signs of an attack in progress: unexpected processes, new outbound connections, logins that do not fit.

More on cypro.co.uk
Incident responders containing an attack

Incident response

If you may already be compromised, our responders contain it, preserve the evidence, find out what was touched and get you running again safely.

More on cypro.co.uk
Scanner checking internet-facing systems for weaknesses

Vulnerability scanning

Find every internet-facing system you run, including the forgotten ones, and see which are still on a vulnerable build.

See the scanning service
Rocket launching from a cloud

Get ready

Need to know what this means for you?

A disclosure that leaks, or a redaction you cannot explain, becomes a complaint to the ICO. A GDPR consultant can review your disclosure workflow, exemption log and release checks before a request tests them.