Skip to main content
← Browse the editorial archive

Social engineering: requests and reporting

This article is part of Certifyd’s historical security editorial archive. It was revised in October 2026 to remove unsupported claims and earlier product promises. It is not a specification of currently available Certifyd features.

Review the action and approval route

Pressure and apparent authority can make a request difficult to question. Give staff an established route to confirm payments, account changes and sensitive disclosures, plus a way to report concerns.

The NCSC phishing guidance combines technical controls, reporting and response. A broad survey's “human element” category should not be relabelled as the percentage of all breaches caused by social engineering.

Avoid false certainty

This article does not substantiate its earlier percentages or unnamed loss cases. A cryptographic system has a defined scope and implementation; it does not make every social-engineering attack impossible.

Certifyd's current workforce records support evidence and review actions. They do not authenticate every request or remove the need for controlled approvals and incident response.

Book a demo