Action plan

An action plan for redaction

Work through the steps in order: write the procedure, add a check, record decisions, then fix delivery. Each step maps to ICO guidance.

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

A tangled green line leading to an arrow

Order of work

Why this sequence

Start with the procedure, because every later step hangs from it. After the Birmingham incident the ICO recommended a standard operating procedure, a corporate redaction policy and a check by someone other than the author [9]. Those three recommendations are a sound first backlog for any team.

A hooded figure holding up three masks

First week

Look at a real case

Take one past response and walk it through the steps below. Gaps show up quickly when you have an actual pack in front of you. Note what was missing: a written reason, a second reader, a safe format.

Then

Make it routine

Once the gaps are listed, assign each an owner and a date. The review workflow and the audit trail pages give the detail behind steps two and three.

Keep it small

A one page procedure that people follow beats a long policy that nobody opens. The ICO's spreadsheet checklist is a numbered list of discrete steps, split into what you must, should and could do [6].

What to do

Eight steps, in order

  1. Step 1

    Write a redaction procedure and name an owner[9]

    State who redacts, who approves, which tool is used and where the result is saved. After the Birmingham case the ICO recommended a standard operating procedure and a corporate redaction policy.

    Who: Data protection lead

  2. Step 2

    Add an independent check before release[9]

    Have someone other than the author check each pack before it goes out. The ICO made the same recommendation to Birmingham Children's Trust.

    Who: Team leaders

  3. Step 3

    Apply the three questions to other people's data[1]

    Ask whether you can comply without identifying them, whether they have consented, and whether disclosure is reasonable without consent. Record the answer.

    Who: Whoever prepares the response

  4. Step 4

    Stop using hidden rows and read-only flags as protection[6]

    The ICO lists hiding rows, columns or worksheets as an ineffective way to conceal data in a spreadsheet. Convert to a simpler format and check what remains.

    Who: Analysts and IT

  5. Step 5

    Redact on a copy and save a new file[12]

    The ICO's advice for small organisations is to save a computer redaction as a new file. Keep the original untouched and send only the new file.

    Who: Request handlers

  6. Step 6

    Log every exemption with its reason[3]

    Record the exemption, the prejudice you identified and why it applies. The ICO says you must be able to justify the decision if a complaint follows.

    Who: Data protection lead

  7. Step 7

    Choose a secure delivery method and check the address[2]

    Encrypt the pack and send the access code separately, or use special delivery or a courier for hard copies. Check the email or postal address before you send.

    Who: Request handlers

  8. Step 8

    Diary the deadline and any clarification request[4]

    Count one month from receipt. Note the date you ask for clarification, because the clock pauses only for that reason.

    Who: Request handlers

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.