Redact evidence by removing anything that identifies other customers, individuals, internal systems or credentials, while keeping what proves the control: the setting, the date and the result. Work on a copy, have a second person check it, and keep the unredacted original in your register.
What to remove
| Item | Why |
|---|---|
| Other customers' names and data | Confidentiality to them |
| Employee personal details | Privacy |
| Internal hostnames, IP addresses, account IDs | Reveals your layout |
| Tokens, keys, passwords, secrets in configs | Direct risk |
| Internal ticket links and URLs | Reveals tooling and may leak |
| Email addresses of staff | Phishing targets |
What to keep
Keep the control name, the setting value, the timestamps, the tool or source name where it is safe, and any counts a reviewer needs. If you black out too much, the evidence stops proving anything and the customer will ask for another version.
Steps
- Work on a copy. Never edit the original.
- Remove items from the table above, using true removal, not a black box over text that remains in the file.
- For PDFs and images, export to a flattened version and test that the hidden text cannot be selected.
- Check metadata: author names, file paths, comments and tracked changes.
- Have a second person review against the checklist before sending.
- Record who redacted, who checked, the date and the recipient.
- Store both versions in the register, with the original marked internal only.
Common mistakes
- A black rectangle over text that can still be copied.
- A screenshot with a browser tab showing another customer's name.
- An export with a hidden sheet or column in a spreadsheet.
- A log excerpt containing a token in a URL query string.
- Sharing the same file with a second customer without a fresh check.
If you find a secret in evidence you were about to share, treat it as a security event: rotate it and note it in your records. That step is separate from redaction.
Choosing a format
Prefer a fresh export or summary to a heavily edited original. If a system can produce a filtered report, use it. A purpose built extract with only the needed fields is safer than redacting a full dump.
Sharing with care
Send through your usual secure channel, apply any NDA terms, and label the document with the recipient and date. Where the customer needs it only for review, use a link that expires and can be revoked, and note the expiry in the register. This is a business control, not legal advice.
Where Safeguard fits
Safeguard's compliance and evidence automation lets you keep a controlled original and a dated shared version side by side, and the free scan at https://gold.safeguard.sh/scan gives a result you can share without internal detail.
Quick check
Is a black box over text enough?
Not always. Flatten the file and confirm the text cannot be selected or recovered.
Should we keep the original?
Yes, marked internal only, so you can prove what the redacted copy was derived from.
Last reviewed: 19 October 2026.
