Sensitive document published by mistake: verify removal

Removing a link does not necessarily remove the file. Check direct access, served copies and search results separately.

Empty OSINT desk with maps, monitors and an intelligence dossier AI-generated editorial illustration

Six repeatable checks

  1. Scope the exposure

    Record URLs, variants, formats and the known exposure period. Keep restricted evidence without spreading the document further.

  2. Close access at the source

    Remove the file or enforce real authorisation. Test the direct URL while signed out, including the origin storage.

  3. Review served copies

    Check CDNs, thumbnails, exports and older versions. Purge caches you control, then repeat an anonymous request.

  4. Handle exposed secrets

    If credentials were included, have their owner revoke or replace them. Deleting the document does not revoke access.

  5. Address search results

    Google's temporary removal complements source removal. robots.txt and noindex do not protect confidential files from direct access.

  6. Close with evidence

    Record HTTP results, anonymous access responses and remaining actions. Assign an owner to each external copy outside your control.

Review record to retain

  • Identified URLs and variants
  • Anonymous access after removal
  • Caches and secrets addressed
  • Owners and follow-up checks

This is a working method, not a statement of compliance. Adapt the scope and document exceptions.

Situations and suitable checks

On a small screen, scroll the table horizontally. With a keyboard, focus the table and use the arrow keys.

SituationWhat it indicatesUseful verification
The menu link is gone, but the file still downloads.The source remains accessible.Remove or protect direct access to the file.
The source is withdrawn, but a CDN copy or thumbnail still responds.A controlled copy remains available.Address relevant copies and caches, then retest while signed out.
A search result remains after the source is withdrawn.Search-engine state differs from server state.Verify removal at the source, then use the appropriate search-engine procedure.
The search result is gone, but the file is still public.Reduced visibility does not protect the document.Restrict actual access independently of indexing.
Google accepts a temporary removal.It lasts about six months and does not remove the source.Maintain permanent source measures and schedule a check before temporary removal expires.

Fictional example

In this fictional example, an internal PDF is mistakenly placed in a public directory. Removing its link from a page does not block its direct URL.

The owner inventories URLs and variants, removes or protects the source and addresses controlled copies. Each URL is tested while signed out. If credentials were exposed, their owner handles revocation. Known external copies and follow-up actions are recorded without promising universal erasure.

Acceptance criteria

  • Direct URLs tested while signed out no longer deliver confidential content.
  • Responsible owners have addressed controlled copies and any exposed credentials.
  • Remaining external copies, responsible parties and follow-up actions are documented.
  • A named owner maintains source protection and the temporary-removal review date.

Practical questions

Does removal from Google prove the file is gone?

No. The tool affects Google Search, not the source file or other search engines.

Is a 200 status always acceptable?

Inspect the response body: an error page with status 200 does not establish correct removal. Check actual access and status.

Can every copy be guaranteed to disappear?

No. Identify limits, contact relevant owners and document what remains outside your control.

Should temporary links be checked?

Yes: a signed link that remains valid may grant access. Inventory known links without spreading their tokens; ask the storage owner to check validity and blocking options. A link disappearing from a page does not establish revocation.

Is one anonymous access refusal enough to close the case?

It establishes the result of that request, for that URL at that time. Also check variants, older versions and accounts that should no longer have access. Distinguish completed checks, copies outside your control and actions still assigned to an owner.

What should be monitored after withdrawal?

Retest exact URLs, variants and relevant caches while signed out. Check the returned content, not just the HTTP status. Keep evidence that does not reproduce the sensitive document.

When can a corrected version be published?

After authorization and checks of its content, attachments and access. That approval covers the new version; it does not prove that every old copy has disappeared.

Official references

Incident, vulnerability or data breach: find the right contact

A CSIRT serves a defined constituency: an organisation, sector or community. Its country and FIRST membership do not establish your eligibility, its availability or the services it offers. Check all three on its official website.

  1. Establish the facts
  2. Check the constituency
  3. Confirm the official channel

Incident on your system

Contact the internal team or provider named in your response plan. Look for a CSIRT covering your organisation when external coordination is needed.

Check who it serves, reporting procedures and operating hours; a public form does not guarantee an immediate response.

Find a CSIRT

Flaw in a third-party product

Check the supplier’s disclosure policy or product security incident response team (PSIRT). The /.well-known/security.txt file may specify a contact, policy and encryption details.

Check the domain, Expires field and policy scope. security.txt does not authorise testing; agree on a channel before sending sensitive evidence.

Understand disclosure

Personal data involved

Involve the data controller and data protection officer, if appointed, alongside the technical response team.

Technical assistance and any regulatory notification are separate processes. Have the applicable authority, conditions and deadlines determined for your situation.

Explore data governance
Prepare a useful first contact

This checklist prepares a conversation; it measures neither incident severity nor resolution. Selections stay on this page and are not sent.

References: FIRST, RFC 9116 and CNIL (French framework). FIRST · CSIRT Services Framework 2.1RFC 9116 · security.txtCNIL · Violations de données personnelles

References: data, uses and limitations

Documentation reviewed on .

References: data, uses and limitations
Source and purposeVerified data or benchmarkHow to use itLimitation to retain
NIST · SP 800-61 Rev. 3

Prepare incident response within cybersecurity risk management.

Revision 3 was published in April 2025 and supersedes Revision 2. It is a CSF 2.0 Community Profile. Rehearse containment decisions, evidence preservation, communication and recovery. Compare planned actions with evidence produced during the exercise.

Explore the method →

Reading the guide does not validate a local plan. Contacts, emergency access and dependencies need local testing.
NIST · Privacy Framework

Examine risks to people arising from data processing.

The Privacy Framework is a voluntary privacy risk-management tool. It is distinct from a universal legal compliance checklist. Describe actual processing: data, purposes, recipients, access and retention. Compare documents, settings and deletion or retrieval tests.

Explore the method →

Using the framework alone does not determine compliance with applicable law. Processing context and jurisdiction still need examination.

PDF: redaction and release

A redacted copy does not close publication removal

Bind the correction to the delivered copy, active links and accessible versions. Sanitizing a new PDF does not recall a previous attachment or a copy already received.

  • Check the final version from the intended recipient’s perspective.
  • Inventory relevant comments, attachments and hidden information.
  • Record old versions and removal measures that are actually possible.

See surfaces and the pre-sharing review matrix →

Sources reviewed on · Adobe · Redacting and sanitizing PDFs · Adobe · Redact sensitive content · Adobe · Sanitize PDFs · ICO · Avoid accidental breaches when redacting · ICO · Hidden information in documents · Microsoft · Document Inspector