A familiar appearance is a weak foundation for trust.
Generative tools can make impersonation more persuasive: polished supplier emails, plausible documents and synthetic voices or video can all borrow the outward signs of a trusted business. Impersonation also happens without AI. A convincing communication is not evidence of its origin.
The risk is practical: new bank details arrive in an existing conversation; a quotation total changes; an adviser’s branding appears on a document they never sent. Checking spelling and recognising the logo cannot settle those questions.
Set up verification and approval processes before a sensitive instruction arrives. For payments, independently confirm changes through a previously established contact route. Do not rely on a telephone number supplied in the suspicious message.
What a cryptographic check actually tells you.
- Fingerprint the content. A cryptographic hash represents the exact bytes of a protected message or file. A changed file produces a different fingerprint.
- Sign the evidence. A digital signature binds the evidence to a signing key. We Secure Data’s documented protocol uses ECDSA P-256 and SHA-256.
- Trust the right public key. Obtain or validate the organisation’s key through an independently trusted route. A key bundled with a file can check a signature, but cannot by itself prove which business owns it.
- Check both signature and content. Verify the signature and compare the file with the signed fingerprint. A mismatch means the checked content does not match that evidence; it does not identify who changed it.
In supported We Secure Data certified-sending workflows, recipients can check the recorded sender and protected content. Senders can retain evidence of the exact version they shared. Exported evidence bundles support independent checks without the original We Secure Data account; supported offline workflows require the relevant evidence, files and trusted public key.
Read the verification protocol or explore We Secure Data provenance and identity binding.
Put the proof to work in your business.
- Establish the trusted business key. Confirm that the public key belongs to the organisation you intend to deal with, and keep signing keys secure.
- Check the exact content. A matching signature confirms the content matches the signed evidence under that key. Use that record alongside your business approval process when acting on financial or contractual instructions.
- Make certified sending your standard. Send important messages and files through the We Secure Data certified workflow so recipients receive evidence they can check.
- Bring security controls together. Combine verifiable evidence with encryption, access control, multi-factor authentication and payment approvals.
Build verification into your existing security and payment approval processes. The FBI’s business email compromise guidance explains additional precautions.
Start with the exchanges where mistakes matter most.
Choose one workflow: supplier instructions, client financial documents, contract versions or sensitive adviser correspondence. Establish the trusted organisation key and show recipients how to verify the evidence before relying on it.
We Secure Data’s web application supports secure exchange. Professional and Business plans add supported Outlook and Windows/macOS desktop workflows; Outlook setup is required. Professional and Business also include We Secure Data for Gmail: create protected content and insert a secure link into your Gmail draft. Explore the Gmail add-on. You can retain your existing email infrastructure.
Hosted plans begin at £39/month for two users, excluding applicable VAT. Company registration is currently through early access. Compare plans and entitlements, follow an actual desktop send or register your interest.
Keep the proof when the content travels.
Use the supported Certified Forward workflow when another recipient needs the original certified content and applicable evidence. A normal email forward is not equivalent. Explore evidence export and Certified Forward.