DocumentaciónHelp

Verify a file's integrity

Use the file's digital hash to check that the stored evidence is exactly the same as what was uploaded.

On this page

When you upload evidence, SofIA Governance calculates its digital hash (SHA-256): a unique code that changes if even one character of the file is modified. Verifying integrity means recalculating that hash on the stored file and comparing it with the original. This way you can show an auditor that the document hasn't been altered since it was uploaded.

Before you start

  • Any role can verify integrity, including Read only.

  • The document must have a recorded hash. In the repository, only documents that have one show the fingerprint button.

Steps

  1. Go to ISMS → Evidence.

  2. Find the document.

  3. Press the fingerprint button (Verify integrity (SHA-256 hash)).

You can also verify each version of a document from the Versions tab of its page, in ISMS → Documents and policies. See Upload a version.

What the result means

Message

What it means

What to do

"…" is intact.

The stored file is identical to the one uploaded.

Nothing: the evidence is reliable.

The hash of "…" does not match: the file was altered.

The stored file is no longer the same as the one uploaded.

Don't use it as evidence. Notify your CISO or Argunis immediately, upload the document again from a trusted copy and withdraw the altered one.

Evidence has no recorded hash.

The document was uploaded before SofIA Governance recorded hashes, so there is nothing to compare against. You may see this when verifying a version from Documents and policies.

If it is important evidence, upload it again so it gets a hash and withdraw the old one.

The original is in long-term archive storage.

The original was moved to long-term storage and can't be read for comparison.

Ask your CISO or Argunis to retrieve it if you need to verify it.

The file is not available.

The storage didn't deliver the file at that moment.

Try again in a few minutes. If it persists, notify your CISO or Argunis.

A hash that doesn't match is a security incident: someone or something modified a file that should have remained intact. Treat it as such. See Incidents.

Why the file can't be changed

For the hash to serve as proof, the original file stays fixed from the moment it is uploaded. You can edit its name, description, validity and status, but not replace the file. If there is a new version, it is uploaded as another document.

The hash also accompanies the evidence when you download it and when you generate the standard's audit package, which includes the originals with their hashes so the auditor can check them independently. See Generate the audit package.

Related

Search SofIA Governance

Type at least 2 characters to search SofIA Governance.

↑↓ to navigate · Enter to open · Esc to close