Social engineering is the practice of persuading people to reveal secrets or perform unsafe actions that software controls would otherwise block.
Urgency, fear, authority, and a wish to be helpful are the usual levers, often backed by a few real details.
How it works
The request is aimed at a person who can approve, pay, or click, rather than at a bug in code.
A convincing story can succeed even when filters would have stopped a file.
Defenders answer with habits and with process, because the decision happens in a conversation.
Verification on a channel the organization already trusts breaks the attacker's script.
Concrete examples
- A caller pretends to be the help desk and asks an employee to read aloud a one time code.
- A message claims a package is held and pushes the reader toward a fake sign in page.
- A visitor follows a polite employee through a door that should have stayed closed.
Protective measures
- Confirm unusual requests on a phone number or portal you already trust.
- Slow down when a message demands secrecy or immediate payment.
- Give staff a blame free way to report odd requests the same day.
- Require a second person to approve changes to bank accounts and access rights.