Documenti e schermate: rimuovere i dati sensibili prima della condivisione

Un rettangolo nero può nascondere informazioni senza eliminarle. Preparare una copia da condividere e verificare il file che riceverà il destinatario.

Postazione immaginaria di revisione documentale senza persone, con due cartelle nere, pannello illuminato e portatile chiuso. Illustrazione editoriale generata con IA

Sei controlli ripetibili

  1. Limitare il contenuto

    Definire ciò che serve al destinatario. Lavorare su una copia e conservare l’originale in uno spazio autorizzato.

  2. Individuare gli identificatori

    Controllare nomi, indirizzi, riferimenti, schede del browser, notifiche e nomi dei file, non solo il centro della schermata.

  3. Rimuovere il contenuto

    Applicare una vera rimozione nei PDF. Un oggetto sovrapposto o una riga nascosta in un foglio di calcolo non basta.

  4. Ispezionare i dati nascosti

    Controllare autore, commenti, revisioni e allegati con strumenti adatti al formato. Ripetere l’ispezione dopo l’esportazione.

  5. Verificare la copia finale

    Riaprire il file esportato. Cercare e provare a copiare il testo eliminato; controllare tutte le pagine e la leggibilità.

  6. Controllare l’accesso

    Verificare destinatari, permessi e durata. Provare il link senza autenticazione e registrare la versione approvata senza ripetere i dati rimossi.

Scheda di verifica

  • File e versione verificati
  • Tipi di dati rimossi
  • Test sul file esportato
  • Destinatari, permessi e verificatore

Metodo di lavoro, non attestazione di conformità. Adatta il perimetro e documenta le eccezioni.

Situazioni e controlli appropriati

Su schermi piccoli, scorrere la tabella orizzontalmente. Con la tastiera, portare il focus sulla tabella e usare le frecce.

SituazioneChe cosa indicaVerifica utile
Un rettangolo nero copre un nome, ma la ricerca trova il testo.La copertura visiva può conservare i dati sottostanti.Applicare una vera rimozione e controllare il file esportato.
L'anteprima è pulita, ma restano commenti o allegati.Ci sono informazioni oltre la pagina visibile.Ispezionare il sorgente e ogni esportazione da condividere.
Il collegamento funziona senza autenticazione.La diffusione può superare i destinatari previsti.Limitare l'accesso e provare il collegamento senza sessione.
Il documento cambia dopo l'approvazione.L'approvazione precedente riguarda un'altra versione.Ricontrollare la versione finale e identificare il file approvato.
Righe nascoste alimentano formule del file.Eliminarle può modificare i risultati conservati.Su una copia, mostrare le righe, esaminare le dipendenze e verificare i risultati dopo la pulizia.

Esempio fittizio

Un gruppo fittizio deve condividere una relazione e una schermata. Contengono il nome di un revisore e un riferimento interno inutili al destinatario.

Lavorare su una copia, eliminare dettagli inutili e dati nascosti, poi esportare. Un secondo revisore scarica la versione, cerca i termini rimossi e prova a copiare il testo. Il registro descrive le categorie rimosse senza riprodurre valori riservati.

Criteri di validazione

  • Destinatario, scopo e informazioni necessarie sono definiti.
  • Il file scaricato supera controlli di testo, dati nascosti e accesso adeguati al formato.
  • Versione approvata, revisore e condizioni di accesso sono registrati.
  • Valori e calcoli necessari restano coerenti dopo la rimozione delle informazioni inutili.

Domande pratiche

La sfocatura basta?

Non considerarla una garanzia. Rimuovere le informazioni dalla copia distribuita e verificare il risultato finale.

L’esportazione PDF elimina tutto?

No. Controllare contenuti e dati nascosti del file esportato; le funzioni dipendono dall’applicazione.

Bisogna cancellare l’originale?

Seguire la politica di conservazione autorizzata. Separare l’originale protetto dalla copia condivisibile.

Una ricerca senza risultati dimostra la rimozione?

No. Una scansione può mostrare dati senza testo ricercabile. Esamina anche immagini, tutte le pagine e gli elementi nascosti pertinenti della copia finale. Verifica che la ricerca trovi un termine conservato: se non funziona, può dare una falsa sicurezza.

La copia corretta sostituisce gli allegati precedenti?

Non automaticamente. Controlla messaggio, allegati, collegamenti condivisi e cronologia accessibile al destinatario. Identifica la versione approvata e rimuovi le copie precedenti che controlli. Una nuova versione non richiama i file già ricevuti.

Basta l'anteprima per approvare la rimozione?

No. Scaricare il file effettivamente condiviso e verificare contenuto, ricerca, copia del testo e dati nascosti pertinenti. L'anteprima può differire dall'esportazione.

Come conservare prove senza copiare dati sensibili?

Registrare categoria rimossa, controlli, versione e revisore. Non riprodurre i valori rimossi in schermate o ticket accessibili a molte persone.

Riferimenti ufficiali

Riferimenti: dati, usi e limiti

Documentazione consultata il .

Le note dettagliate di questa edizione sono disponibili in inglese.

Riferimenti: dati, usi e limiti
Fonte e finalitàDato o riferimento verificatoCome utilizzarloLimite da conservare
C2PA · Content Credentials

Describe and verify certain content provenance information.

C2PA specification 2.4 defines manifests, assertions and cryptographic binding mechanisms associated with media. Examine what the manifest asserts, who signed it and whether validation succeeds. Test preservation after transformations and distribution.

Approfondire il metodo →

Validated provenance does not establish the truth of a scene. Absence of a manifest does not demonstrate a fake.
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.

Approfondire il metodo →

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

Indicatori STIX e condivisione TLP

Le note dettagliate di questa edizione sono disponibili in inglese.

Check TLP scope before publishing an excerpt

A traceable note does not by itself grant permission to redistribute it. TLP markings, additional restrictions and intended recipients must accompany a redaction or publication decision.

  • AMBER+STRICT limits sharing to the organisation; AMBER’s scope for protecting clients does not apply by default.
  • GREEN excludes public channels; CLEAR does not remove copyright rules or separate restrictions.
  • Check the marking of each quoted field and obtain explicit source permission if the intended sharing exceeds the received scope.

Read the STIX, observations and TLP sharing reference →

Sources checked on · FIRST · TLP 2.0

PDF: oscuramento e diffusione

Le note dettagliate di questa edizione sono disponibili in inglese.

Check the delivered copy beyond its blacked-out areas

Redaction aims to remove excluded information from the copy given to the recipient. Review must cover the final file and its access paths: visual masking, a search returning no results or metadata cleanup alone does not cover the whole decision.

This is an editorial acceptance-review method, not a PDF analysis tool. The five versions and forty observations are fictional; this page uploads, sanitizes and certifies no files. Cited Adobe features concern Acrobat Pro. ICO guidance was published in a UK context and is marked under review; it is not presented as French legal validation.

Four operations and their boundaries

Four operations and their boundaries
OperationIntended outcomeRemaining checks
Mark an areaIdentify content for removal in the appropriate tool.A pending mark or overlaid rectangle is not an applied, saved redaction.
Apply redactionRemove targeted text or images from the copy using the intended function, then save.Hidden and embedded content needs separate inspection; the initial selection may be incomplete.
Sanitize hidden informationInspect and remove relevant metadata, comments, layers or embedded content.Check the saved copy and software limits. Do not assume PDF export removes every item from the source document.
Approve releaseBind a precisely identified version to recipients and documented checks.Links, attachments and accessible prior versions may expose other files. Review remains limited to its scope.

Eight surfaces to examine before handover

Eight surfaces to examine before handover
SurfaceReview questionUseful evidence and limit
Visible textWere intended passages actually removed from the saved copy?Review all pages and test copying the relevant text. A black appearance does not establish removal.
Images and OCR layerDoes information removed from text remain in an image, or vice versa?Inspect the image and text layer where present. A scan without searchable text may still display the information.
Comments and annotationsDo remarks, names or references remain accessible in review panels?Inventory relevant annotations and verify the cleaned version intended for sharing.
Metadata and propertiesDo author, title, keywords or custom properties reveal excluded information?Inspect relevant categories using a suitable tool. Removing a property does not establish absence of the value elsewhere.
Attachments and embedded objectsDoes an attached file or object contain another version of removed material?Review the inventory and every retained item. The visible page does not necessarily describe all embedded content.
Layers and non-visible objectsDoes the file contain elements omitted by an ordinary preview?Use available software controls and record uncovered areas. An absent warning is not a complete review.
Office source documentDo changes, embedded data or properties reappear in the export?Work on a copy; Document Inspector depends on format and cannot detect everything. Inspect the final PDF again.
Release containerDoes the message, shared folder or version history expose an old file?Check the file obtained by the intended recipient and accessible versions. Correcting one copy does not erase copies already received.

Forty observations without a security score

Fictional exercise: FICTIF-42 must be removed, while PUBLIC-ALPHA must remain present and searchable in these five test versions. No real confidential data is used. States describe acceptance observations already stipulated in the scenario; they are not calculated from a PDF.

SatisfactoryObserved failureNot checked
Forty observations without a security score
Scenario checkR01R02R03R04R05
Targeted areas renderedSatisfactorySatisfactorySatisfactorySatisfactorySatisfactory
Retained control PUBLIC-ALPHA foundSatisfactoryObserved failureSatisfactorySatisfactorySatisfactory
Removed term FICTIF-42 not foundObserved failureSatisfactorySatisfactorySatisfactorySatisfactory
Images and OCR reviewedNot checkedSatisfactorySatisfactorySatisfactorySatisfactory
Hidden content reviewedNot checkedSatisfactorySatisfactorySatisfactorySatisfactory
Delivered file = reviewed versionSatisfactorySatisfactorySatisfactoryObserved failureSatisfactory
Recipient access checkedNot checkedSatisfactorySatisfactorySatisfactorySatisfactory
Peer review closedNot checkedNot checkedSatisfactoryNot checkedNot checked

Interpret a negative search only with its limits and a suitable positive control. In R02, PUBLIC-ALPHA is not found: the expected search test fails even though FICTIF-42 is not found either. “Not checked” never counts as success; an average cannot compensate for a failure.

Five decisions bounded by the fictional dossier

Five decisions bounded by the fictional dossier
VersionCandidate copy / delivered fileScenario decision
R01training-report-R01.pdf / training-report-R01.pdfHold and correct
R02training-report-R02.pdf / training-report-R02.pdfHold and correct
R03training-report-R03.pdf / training-report-R03.pdfSubmit for release decision within the tested scope
R04training-report-R04.pdf / training-report-R02.pdfHold and correct
R05training-report-R05.pdf / training-report-R05.pdfReview still open
  • R01: the removed term is still found and several checks remain open.
  • R02: the positive control fails. No search result alone does not demonstrate redaction.
  • R03: the eight defined checks are satisfactory in this exercise. This guarantees neither exhaustive search nor absence of risks outside scope.
  • R04: R02 is delivered although R04 was reviewed. Acceptance does not transfer to the wrong file.
  • R05: defined technical checks are satisfactory; peer review is not closed. The decision remains open.

Eight review situations to explain

01 · Visible rectangle, text still copyable

Fictional situation: layout shows a black area but selection or extraction recovers the passage.

Decision: repeat redaction with a suitable function, apply it, save a copy and inspect the result. The signal shows removal has not been established; changing rectangle colour does not fix it.

02 · Negative search without a positive control

Fictional situation: neither the removed term nor the expected retained term can be found.

Decision: suspend the search conclusion. Check whether the tool and text layer suit this document, then add image inspection. The negative test alone does not establish removal.

03 · Search-clean scan, information visible in the image

Fictional situation: search cannot find a name on a scan with no usable text layer, but the image still shows it.

Decision: handle the information in its actual representation and review the final copy. Missing OCR is not proof of absent visible information.

04 · Comments removed, attachment overlooked

Fictional situation: the comments panel is empty; an embedded attachment still contains an old version.

Decision: examine the attachment and its purpose for the recipient, then correct the release copy. Passing comment review does not cover embedded objects.

05 · Metadata cleaned, name still visible on the page

Fictional situation: the author property is blank but a name remains in a footer.

Decision: revisit the visible-content inventory. Property cleanup and passage removal are separate checks; neither validates the other.

06 · Correct version approved, wrong attachment sent

Fictional situation: review concerns R04; the prepared message contains training-report-R02.pdf.

Decision: do not release the message as approved. Bind the final version to the attachment or file actually obtained by the recipient, then record a fresh check.

07 · Image conversion loses accessibility

Fictional situation: conversion removes useful text and makes the file difficult to read with assistive technology.

Decision: assess the method and produce a usable copy without reintroducing excluded information. Conversion is no universal guarantee; test its effect on readability, search and accessibility.

08 · Corrected copy, old version still accessible

Fictional situation: the corrected PDF is online but a previous version remains downloadable from the shared folder.

Decision: also address access and versions under your control, then assess prior disclosure. A new version does not automatically recall files already copied or received.

Six acceptance records without repeating removed values

  • Sharing purpose, recipients and information categories to remove or retain.
  • Reviewed-copy identity, date, tool, version and relevant processing settings.
  • Surfaces covered, positive and negative checks, results and coverage limits.
  • Corrected discrepancies and review of relevant hidden or embedded content.
  • Link between the reviewed copy, final attachment and versions accessible to the recipient.
  • Reviewer, decision, authorised scope and prior-copy follow-up under the applicable policy.

Forty cells, identifiers and decisions are a local teaching construction. Sources explain the checks; they attest to no file analysis performed here.

Product sources and methodological guidance

Sources reviewed on