Skip to content
A PRACTICAL GUIDE TO VERIFIABLE BUSINESS COMMUNICATION

AI business impersonation:
how to verify genuine messages and files.

When a logo, voice or writing style can be copied, the useful question changes from “Does this look right?” to “What evidence can I check?”

Cryptographic signatures turn that question into a check your recipients can perform. See how signed evidence, trusted business keys and familiar workflows bring confidence to important exchanges.

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.

  1. Fingerprint the content. A cryptographic hash represents the exact bytes of a protected message or file. A changed file produces a different fingerprint.
  2. 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.
  3. 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.
  4. 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.

TRY A REAL SIGNATURE CHECK

One quotation. Two versions.
Only one matches the proof.

Change the total and run the check. Your browser uses the same ECDSA verification implementation served by the We Secure Data application.

ILLUSTRATIVE DATA · DEMONSTRATION KEY

Northstar Design → Harbour & Co.

Quotation QT-1042 · 24 October 2026
Recorded sender: alex@northstar.example

Design and delivery services

Quotation total£4,800.00
Choose the content to check
INDEPENDENT CONTENT CHECK

Check the evidence yourself.

The original quotation is signed under a fixed demonstration public key. The altered version is checked against that same signature.

No check run yet.
What is actually checked?

Your browser checks an ECDSA P-256 / SHA-256 signature over the exact quotation text. This working example uses illustrative data and a demonstration key. See the complete product evidence workflow →

For a business exchange, check the signature against your supplier’s trusted public key. Learn how organisation identity and verification work →

Download the public test evidence (JSON)
THE THREAT IS REAL. GET AHEAD OF IT.

The cyber threat landscape is changing. Build stronger foundations for trust.

From rapidly evolving software threats to convincing business impersonation, the case for stronger digital trust is clear. Give your customers evidence they can check.

Current security guidance21–23 October 2026

Software risk is moving faster

The UK NCSC urged action on critical PHP flaws. The Dutch NCSC’s later update said exploitation was complex and large-scale successful exploitation had not been confirmed. Reuters reported concerns about AI accelerating vulnerability discovery.

Digital trust needs to keep pace with the threat. Give important business communications a stronger foundation: checkable evidence of their recorded origin and exact content.
Historical fraud caseReported February 2024

A familiar face was not reliable proof

An official Macao Judiciary Police warning described a Hong Kong employee deceived by a video meeting impersonating finance colleagues, including a CFO. The reported transfers totalled about HK$200 million.

Recognising a face, voice or logo is no longer enough. Make independently verifiable evidence part of the way your business communicates.
Alleged business email compromise9 June 2025

Supplier correspondence redirected a payment

US prosecutors described an alleged scheme in which a manufacturer’s email identity was impersonated and a buyer was given fraudulent payment instructions.

Make sensitive supplier instructions verifiable. Check the recorded sender and exact content against signed evidence before approving a payment change.

Sources reviewed 24 October 2026. Dates distinguish current guidance from earlier cases. Follow the linked source for subsequent updates.

DON’T WAIT FOR THE FIRST CONVINCING FAKE

Make important exchanges verifiable.

Start with familiar workflows. Give customers evidence they can check.

A copied logo cannot copy your company’s signing key.

A copied logo or convincing email address cannot create a valid signature under the expected company’s key without use of its private signing key. The practical protection depends on authenticating the public key, keeping the signing process uncompromised and actually checking the signature and covered content.

How company signing keys work →