Evidence, evidence requests and Proof Seal
Upload proof, ask colleagues or suppliers for it, and seal it so anyone can verify it hasn't changed.
Upload evidence
Upload files from a control in an assessment, or from Evidence. Each file gets a SHA-256 fingerprint and is linked to the fingerprint of the previous file, forming a chain. If anyone changed a stored file, the fingerprints would no longer match.
Good evidence is specific and dated: a signed policy, a log export, a screenshot of a setting, a test report, minutes of a review meeting.
Ask a colleague for evidence
Use Evidence requests to ask a member of your workspace for a document by a due date, linked to a system and control. They get an email and see the request in V77 Trust. For documents from suppliers, use the vendor questionnaire.
Proof Seal
Proof Seal adds an independent timestamp from a trusted timestamping authority (RFC 3161) to a set of evidence fingerprints. An auditor, regulator or customer can verify that the evidence existed at that time and hasn't changed since, without having to trust V77 Trust.
Don't upload passwords, API keys or unnecessary personal data as evidence. Redact screenshots before uploading.