Social engineering and trusted-person impersonation
V01 · reusable vector · version 1.0HIGH · proposed test impact
The attacker exploits a trusted role, urgency or a routine business process to obtain information or a decision. Public business context can make the approach plausible.
Attacker tools and payload types
A support pretext, call script or instruction is the payload; executable malware is not required.
The entries below are tools that can support assessment or emulate aspects of this vector in an authorised fixture. They are not claims that these exact products were used in every linked incident. Native platform availability and Armory installation are different from tested capability.
- Agent001 · native service; handoff is not automatic execution
- VoiceOps · native service; handoff is not automatic execution
Setoolkit/Wifiphisher are candidate Armory mappings where shown, not the default execution route. Their capabilities may exceed the agreed simulation. Select and review a harmless lab profile; the inert fixture/manual method is sufficient for the initial assessment.
Repository and operating guides
simulation-script.txt · RES-008 · published synthetic fixture in the assessment collection linked from the Repository.
Account Takeover/README.md · existing Repository reference; choose only relevant approved checks.
Read the selected tool’s guide for installation and operation rather than recreating it here. Pin the deployed version and reviewed configuration in the task record. Some local guides are autogenerated inventory notes and contain stale commands or broad prerequisite lists; they require validation before use. The official manuals linked above were checked during this review.
Reusable controlled test
Use a controller-reviewed role-play for specifically approved people and channels. Observe verification and reporting; do not request real credentials.
- Required permission
- Staff contact, each named person, channel, time window and permitted request.
- Parent supplies
- Scenario/risk ID; business question; exact targets; named permitted people; channel; current policy revision; tool/resource versions; limits; expected result and reviewer.
- Output
- One result per approved case, with run and target IDs, permission decision, evidence, actual outcome and coverage limits.
- Measure
- Independent verification and reporting / confirmed delivered approved interactions; channel failures separately. No client result has been collected here.
- Failure handling
- Blocked, not authorised, failed, inconclusive and not tested remain visible. A refused route cannot be replaced by another agent, channel or target without fresh applicable approval.
What the vector returns to the scenario
| Result | What it means |
|---|---|
| Control held | The evidenced attempted action was prevented under the tested conditions. This is not a universal security guarantee. |
| Control failed | Describe the exact observed boundary failure and its business consequence, without inflating it into a wider compromise. |
| Unknown / not tested | Record the missing capability, evidence, permission or coverage. Do not invent a score. |
Mitigation recommendations
Reduce likelihood: Improve independent verification and recovery processes, with role-specific practice.
Reduce impact: Use least privilege, strong identity controls and rapid reporting to prevent one interaction becoming wider access.
Define how a later retest would verify the recommendation; implementation assignments, scheduling and pricing are Part 2.