Documentos e capturas: remover dados sensíveis antes da partilha
Um retângulo preto pode ocultar informação sem a remover. Preparar uma cópia para partilha e verificar o ficheiro que o destinatário receberá.
Seis verificações reproduzíveis
Assinale apenas as verificações realizadas no âmbito escolhido. Este acompanhamento é um lembrete, não um resultado de auditoria. A ferramenta não transmite as suas escolhas.
-
Limitar o conteúdo
Definir o que o destinatário precisa de compreender. Trabalhar numa cópia e guardar o original num espaço autorizado.
-
Identificar referências
Rever nomes, endereços, referências, separadores do navegador, notificações e nomes de ficheiro, não apenas o centro da captura.
-
Remover o conteúdo real
Aplicar uma remoção efetiva nos PDF. Um objeto sobreposto ou uma linha oculta numa folha de cálculo não basta.
-
Inspecionar dados ocultos
Verificar autor, comentários, revisões e anexos com ferramentas adequadas. Repetir a inspeção depois de exportar.
-
Verificar a cópia final
Reabrir o ficheiro exportado. Pesquisar e tentar copiar o texto removido; verificar todas as páginas e a legibilidade.
-
Controlar a partilha
Verificar destinatários, permissões e duração. Testar a ligação sem sessão e registar a versão aprovada sem repetir os dados retirados.
Ficha de revisão
- Ficheiro e versão verificados
- Tipos de dados removidos
- Testes no ficheiro exportado
- Destinatários, permissões e revisor
Método de trabalho, não declaração de conformidade. Adapte o âmbito e documente as exceções.
Situações e verificações adequadas
Em ecrãs pequenos, desloque a tabela horizontalmente. Com o teclado, coloque o foco na tabela e use as setas.
| Situação | O que indica | Verificação útil |
|---|---|---|
| Um retângulo preto tapa um nome, mas a pesquisa encontra o texto. | A ocultação visual pode manter os dados originais. | Aplicar uma remoção efetiva e testar o ficheiro exportado. |
| A pré-visualização está limpa, mas restam comentários ou anexos. | Há informação fora da página visível. | Inspecionar o original e cada exportação a partilhar. |
| A ligação funciona sem autenticação. | A divulgação pode ultrapassar os destinatários previstos. | Restringir o acesso e testar sem sessão iniciada. |
| O documento mudou após a aprovação. | A aprovação anterior refere-se a outra versão. | Rever a versão final e identificar o ficheiro aprovado. |
| Linhas ocultas alimentam fórmulas do livro. | Apagá-las pode alterar os resultados preservados. | Numa cópia, mostrar as linhas, analisar dependências e verificar os resultados após a limpeza. |
Exemplo fictício
Uma equipa fictícia pretende partilhar um relatório e uma captura de ecrã. Contêm o nome de um revisor e uma referência interna desnecessários para o destinatário.
Trabalhar numa cópia, remover detalhes desnecessários e dados ocultos, depois exportar. Outro revisor descarrega essa versão, procura termos removidos e testa a cópia de texto. O registo descreve categorias removidas sem reproduzir valores confidenciais.
Critérios de validação
- Destinatário, finalidade e informação necessária estão definidos.
- A versão descarregada passa verificações de texto, dados ocultos e acesso adequadas ao formato.
- Versão aprovada, revisor e condições de acesso estão registados.
- Os valores e cálculos necessários mantêm-se coerentes após remover informação desnecessária.
Perguntas práticas
Desfocar é suficiente?
Não considerar uma garantia. Remover a informação da cópia distribuída e verificar o resultado final.
Exportar para PDF elimina tudo?
Não. Verificar conteúdo e dados ocultos do ficheiro exportado; as funções dependem da aplicação.
É preciso apagar o original?
Seguir a política de conservação autorizada. Separar o original protegido da cópia partilhável.
Uma pesquisa sem resultados prova a remoção?
Não. Uma digitalização pode mostrar dados sem texto pesquisável. Inspecione também imagens, todas as páginas e elementos ocultos relevantes da cópia final. Confirme que a pesquisa encontra um termo mantido: uma pesquisa que não funciona pode dar uma falsa segurança.
Uma cópia corrigida substitui anexos anteriores?
Não automaticamente. Verifique a mensagem, os anexos, os links partilhados e o histórico acessível ao destinatário. Identifique a versão aprovada e remova as cópias antigas que controla. Uma nova versão não recupera ficheiros já recebidos.
A pré-visualização basta para aprovar a remoção?
Não. Descarregue o ficheiro efetivamente partilhado e verifique conteúdo, pesquisa, cópia de texto e dados ocultos pertinentes. A pré-visualização pode diferir da exportação.
Como guardar provas sem copiar dados sensíveis?
Registe a categoria removida, verificações, versão e revisor. Evite reproduzir valores removidos em capturas ou pedidos amplamente acessíveis.
Referências oficiais
Referências: dados, usos e limites
Documentação consultada em .
As notas detalhadas desta edição estão disponíveis em inglês.
| Fonte e finalidade | Dado ou referência verificada | Como utilizar | Limite a preservar |
|---|---|---|---|
| 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. | 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. | Using the framework alone does not determine compliance with applicable law. Processing context and jurisdiction still need examination. |
Indicadores STIX e partilha TLP
As notas detalhadas desta edição estão disponíveis em inglês.
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: expurgo e divulgação
As notas detalhadas desta edição estão disponíveis em inglês.
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
| Operation | Intended outcome | Remaining checks |
|---|---|---|
| Mark an area | Identify content for removal in the appropriate tool. | A pending mark or overlaid rectangle is not an applied, saved redaction. |
| Apply redaction | Remove 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 information | Inspect 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 release | Bind 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
| Surface | Review question | Useful evidence and limit |
|---|---|---|
| Visible text | Were 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 layer | Does 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 annotations | Do remarks, names or references remain accessible in review panels? | Inventory relevant annotations and verify the cleaned version intended for sharing. |
| Metadata and properties | Do 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 objects | Does 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 objects | Does 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 document | Do 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 container | Does 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.
| Scenario check | R01 | R02 | R03 | R04 | R05 |
|---|---|---|---|---|---|
| Targeted areas rendered | Satisfactory | Satisfactory | Satisfactory | Satisfactory | Satisfactory |
| Retained control PUBLIC-ALPHA found | Satisfactory | Observed failure | Satisfactory | Satisfactory | Satisfactory |
| Removed term FICTIF-42 not found | Observed failure | Satisfactory | Satisfactory | Satisfactory | Satisfactory |
| Images and OCR reviewed | Not checked | Satisfactory | Satisfactory | Satisfactory | Satisfactory |
| Hidden content reviewed | Not checked | Satisfactory | Satisfactory | Satisfactory | Satisfactory |
| Delivered file = reviewed version | Satisfactory | Satisfactory | Satisfactory | Observed failure | Satisfactory |
| Recipient access checked | Not checked | Satisfactory | Satisfactory | Satisfactory | Satisfactory |
| Peer review closed | Not checked | Not checked | Satisfactory | Not checked | Not 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
| Version | Candidate copy / delivered file | Scenario decision |
|---|---|---|
| R01 | training-report-R01.pdf / training-report-R01.pdf | Hold and correct |
| R02 | training-report-R02.pdf / training-report-R02.pdf | Hold and correct |
| R03 | training-report-R03.pdf / training-report-R03.pdf | Submit for release decision within the tested scope |
| R04 | training-report-R04.pdf / training-report-R02.pdf | Hold and correct |
| R05 | training-report-R05.pdf / training-report-R05.pdf | Review 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
- Adobe · Redacting and sanitizing PDFs · Acrobat Pro · updated 2026-10-22
Redaction · Sanitization · Redaction limitations - Adobe · Redact sensitive content · Acrobat Pro · updated 2026-08-31
Mark content · Apply · sanitize option · save the resulting file - Adobe · Sanitize PDFs · Acrobat Pro · updated 2026-10-22
Hidden metadata, comments and layers · selective removal · save - ICO · Avoid accidental breaches when redacting · Published 2025-07-31 · guidance under review · checked 2026-10-22
Electronic documents · copies · peer review · PDFs and images - ICO · Hidden information in documents · Published 2025-07-31 · guidance under review · checked 2026-10-22
Metadata · embedded objects · markup · inspection-tool limitations - Microsoft · Document Inspector · Living documentation · checked 2026-10-22
Inspect a copy · hidden data · limits vary by Office format
Sources reviewed on
