Social engineering uses human interaction as part of an attempt to obtain information, influence a decision or gain access. The technique can appear in a phone call, an office conversation, a delivery interaction or a request for help. NIST describes social engineering as deception used to make a person reveal sensitive information, obtain unauthorized access or commit fraud by building trust.
This article looks at workplace scenarios such as pretexting, impersonation, baiting and tailgating. It does not repeat the general email and fake-link guidance covered in the site's phishing articles, or the payment-redirection focus of its Business Email Compromise article.
Why a believable story can be a security control failure
People are trained to be helpful, responsive and respectful of authority. An attacker may exploit those habits by creating a plausible reason to skip an ordinary check. The request can sound routine: help a colleague who has lost access, let a contractor through a door, confirm a staff member's role or share a small piece of internal information.
The key question is not whether the person sounds confident. It is whether the request follows a process that the organization has approved.
Pretexting: a story designed to earn cooperation
Pretexting means presenting a fabricated or misleading situation to make a request appear legitimate. A caller might claim to be from technical support and say that a device needs urgent attention. Someone in a shared office might say that a manager asked for a staff directory or a temporary access code.
The story can include real details collected from public profiles, event schedules or earlier conversations. Familiar names and accurate background details may make a request feel credible, but they do not prove the person's identity or authority.
Verification habit
Pause the request, then contact the relevant person or department through a number, directory or service channel already held in the organization's trusted records. Do not use contact details supplied only by the requester.
Impersonation: claiming a role that carries authority
An impersonator may act like an executive, technician, supplier, auditor, courier or new employee. The purpose is to make another person believe that the request is normal for that role. Some requests are designed to take advantage of hierarchy: a junior employee may feel uncomfortable challenging a person who claims to be senior.
Organizations can reduce this pressure by defining repeatable checks for sensitive actions. For example, staff-directory verification can confirm employment, ticketing systems can confirm support work, and approved request records can show who authorized a change. A job title or branded clothing should not replace those checks.
Baiting and quid pro quo: an attractive offer or promised help
Baiting offers something that is meant to tempt a person into an unsafe action. A familiar example is an unknown storage device left where someone may pick it up and connect it to a work computer. Other scenarios can involve free files, gifts, discounts or access to something desirable.
Quid pro quo uses an exchange: an individual offers a service or benefit in return for information, access or an action. A caller might offer to fix a problem in exchange for a password or ask to use an employee's logged-in computer to complete a task.
The practical rule is simple: do not connect unknown devices, install unapproved software, reveal credentials or bypass normal service procedures to receive an unsolicited benefit. Route technical help through the organization's approved support process.
Tailgating: entering a restricted area behind an authorized person
Tailgating is a physical access tactic in which someone follows an authorized person through a controlled entrance without completing the required check. The person may carry boxes, appear to be in a hurry or say that they forgot a badge. A friendly employee may hold the door open to be polite.
Physical access can expose computers, paperwork, network equipment, meeting rooms and conversations. A visitor who reaches an unattended workstation may have opportunities that a remote attacker does not.
Follow the building's visitor and access policy. Do not let an unknown person use your badge or pass through a secured door solely because they appear familiar. Direct visitors to reception or the approved check-in point. Staff should challenge an unexpected entry politely and use security staff when a situation feels unsafe.
Information gathering can make later requests more convincing
Small details can help someone construct a believable story: team names, office locations, project terminology, supplier relationships or the names of people who are away. This is sometimes called social mining or reconnaissance. A detail may be harmless on its own but useful when combined with other information.
Staff should follow the organization's rules for discussing internal work in public spaces, sharing documents and publishing operational details. This is not a call to hide ordinary professional information; it is a reminder to consider whether a detail helps an unknown person impersonate a colleague or bypass a process.
Build controls around the decision, not the person's confidence
- Use known channels: verify unusual requests through an established directory, help desk or approval system.
- Protect credentials: no colleague, contractor or support person should need another user's password or one-time authentication code.
- Make visitor rules consistent: use reception, badges, escorts and designated access routes according to site policy.
- Separate duties: sensitive changes should have an approval path that does not depend on one person's verbal instruction.
- Keep reporting simple: give staff a clear way to report suspicious conversations, attempted entry or unusual requests without blame.
- Practise realistic scenarios: train employees on what to say and where to escalate, not only on lists of threat names.
Worked example: an unexpected support visit
Imagine someone arrives at a small office and says that a network outage has been reported. The visitor wears a generic company-style shirt and asks to enter the communications room to inspect a router. The office receptionist does not recognize the visitor.
A safe response is to keep the visitor in the public area, request identification according to site policy, contact the named service provider using a number already in the vendor record and confirm that a work order exists. The employee should not escort the person into a restricted room until the visit is verified and approved. If the story cannot be confirmed, the employee should follow the site's escalation process.
The important control is the independent check. A convincing explanation is not evidence that the person is authorized.
What to do after a suspicious interaction
Do not conceal an accidental disclosure or an unauthorized entry. Report what happened promptly through the organization's security, facilities or incident-response channel. Include the time, place, request, people involved and any information or access provided. Follow instructions about changing exposed credentials, checking devices, reviewing access logs or preserving relevant records.
Do not confront a person if doing so could create a physical safety risk. Follow local workplace procedures and contact site security or emergency services when there is an immediate threat.
Frequently asked questions
Is social engineering always a digital attack?
No. It can involve conversations, phone calls, physical access or a mix of channels. The common feature is deception used to influence a person's action or disclosure.
Is it rude to challenge someone who says they work for IT?
Following a consistent verification process is a normal security responsibility, not a personal accusation. A legitimate worker should be able to use the organization's approved identity and work-order checks.
Should employees let someone follow them through a secured door?
They should follow the site's access policy rather than make assumptions based on appearance or urgency. Visitors should use the approved check-in process.
Key takeaway
Workplace social engineering succeeds when a story, favour or claimed role persuades someone to skip a check. Clear verification channels, visitor procedures, credential boundaries and blame-free reporting make it easier for employees to pause and respond consistently.
Sources and further reading
- NIST Computer Security Resource Center: Social Engineering glossary.
- NIST SP 800-53 Revision 5: Security and Privacy Controls for Information Systems and Organizations, including awareness and training controls addressing social engineering.
- NIST SP 800-171 Revision 3: Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations, including examples such as pretexting, impersonation, baiting and tailgating.
This article provides general awareness information. Follow the access, visitor and incident-reporting procedures set by your organization.