Conducting Social Engineering Pretext Call
Overview
A pretext call (vishing) is a social engineering technique where an attacker impersonates a trusted authority figure over the phone to manipulate targets into divulging sensitive information, performing actions, or granting access. In red team engagements, pretext calls test the human element of security controls, measuring employee adherence to verification procedures and security awareness training effectiveness. MITRE ATT&CK maps this to T1566.004 (Phishing for Information: Voice) and T1598 (Phishing for Information).
When to Use
- When conducting security assessments that involve conducting social engineering pretext call
- When following incident response procedures for related security events
- When performing scheduled security testing or auditing activities
- When validating security controls through hands-on testing
Prerequisites
- Written authorization specifying social engineering scope and boundaries
- List of approved target employees (usually provided by client)
- OSINT research on targets and organization
- Spoofed caller ID capability (authorized for testing)
- Call recording equipment (with legal consent as required)
- Pretext scenarios approved by client
MITRE ATT&CK Mapping
| Technique ID |
Name |
Tactic |
| T1566.004 |
Phishing: Voice |
Initial Access |
| T1598 |
Phishing for Information |
Reconnaissance |
| T1598.003 |
Phishing for Information: Spearphishing Voice |
Reconnaissance |
| T1589 |
Gather Victim Identity Information |
Reconnaissance |
| T1591 |
Gather Victim Org Information |
Reconnaissance |
Phase 1: OSINT and Target Research
# LinkedIn employee enumeration
theHarvester -d targetcorp.com -b linkedin -l 200
# Company org chart and employee roles
# Review LinkedIn, corporate website "About Us" / "Team" pages
# Technology stack identification
# Check job postings for technology references (VPN vendor, email, helpdesk tool)
# Phone system identification
# Call main line, note IVR options, department names, extension patterns
Key intelligence to gather:
- Internal helpdesk phone number and procedures
- IT department names and staff
- VPN/remote access vendor (Cisco AnyConnect, Fortinet, Pulse Secure)
- Corporate email format (first.last, flast, etc.)
- Recent events (mergers, office moves, system upgrades)
- Employee names, titles, departments
Phase 2: Pretext Development
Common Pretext Scenarios
IT Helpdesk Impersonation (Most Effective):
"Hi, this is [name] from the IT Service Desk. We're migrating everyone to the new VPN client this week, and I see your account hasn't been updated yet. I need to verify your current credentials to ensure the migration goes smoothly. Can you confirm your username and current password?"
Vendor/Contractor:
"Hi, I'm [name] from [known vendor]. We're doing an emergency patch deployment for [product] and I need remote access to your system. Could you help me connect via TeamViewer?"
Executive Assistant (Authority):
"This is [name] calling on behalf of [CFO name]. [He/She] needs an urgent wire transfer processed for a deal that's closing today. I'll email you the details, but we need this done in the next hour."
Building/Facilities:
"Hi, this is [name] from facilities management. We're updating the badge access system this weekend. I need to confirm your employee ID and current badge number so your access isn't interrupted."
Pretext Checklist
Phase 3: Call Execution
Call Structure
- Introduction (10 seconds): State name, department, reason for calling
- Building rapport (30 seconds): Reference something real (recent event, shared context)
- Authority establishment (20 seconds): Reference manager name, ticket number, urgency
- Information request (30 seconds): Ask for the target information naturally
- Handling objections: If challenged, respond calmly with prepared answers
- Closing (10 seconds): Thank them, leave no suspicion
Objection Handling
| Objection |
Response |
| "Can I call you back?" |
"Of course, call the main helpdesk line and ask for [name]. But this needs to be done by EOD." |
| "I need to verify this" |
"Absolutely, I appreciate your diligence. You can check with [manager name]." |
| "I was told never to give passwords" |
"You're right, and normally we wouldn't ask. This is a special case because [reason]. I can have my manager call you." |
| "What's your employee ID?" |
Pivot: "It's [made-up ID]. Listen, I have 50 more people to call today. Can we just get this done?" |
| "I'll email IT instead" |
"Sure, but the system migration happens tonight. If it's not done by then..." |
Phase 4: Data Collection and Metrics
Track the following for each call:
| Metric |
Description |
| Target Name |
Employee called |
| Department |
Target's department |
| Date/Time |
When call was made |
| Duration |
Length of call |
| Pretext Used |
Which scenario |
| Information Obtained |
What was disclosed |
| Credential Disclosed |
Yes/No (and type) |
| Verification Attempted |
Did target try to verify caller? |
| Reported to Security |
Did target report the call? |
| Social Engineering Score |
1-5 susceptibility rating |
Phase 5: Reporting
Success Metrics
| Metric |
Target |
Result |
| Credential Disclosure Rate |
<10% |
XX% |
| Sensitive Info Disclosure Rate |
<20% |
XX% |
| Verification Rate |
>80% |
XX% |
| Security Reporting Rate |
>50% |
XX% |
Ethical and Legal Considerations
- Always obtain written authorization before conducting vishing tests
- Never use threatening language or create genuine fear
- Document consent and legal requirements for call recording
- Protect disclosed credentials - immediately report to client
- Debrief targets after the engagement if client approves
- Never publicly identify specific employees who failed
- Comply with telecommunications laws in your jurisdiction
References
- Verizon DBIR 2025: 74% of breaches involve human element
- MITRE ATT&CK T1598: https://attack.mitre.org/techniques/T1598/
- Social Engineering Penetration Testing by Gavin Watson (Syngress)
- The Art of Deception by Kevin Mitnick (Wiley)
- NIST SP 800-50: Building an Information Technology Security Awareness and Training Program
1---
2name: conducting-social-engineering-pretext-call
3description: Plan and execute authorized vishing (voice phishing) pretext calls to
4 assess employee susceptibility to social engineering and evaluate security awareness
5 controls.
6domain: cybersecurity
7subdomain: red-teaming
8tags:
9- social-engineering
10- vishing
11- pretext-call
12- security-awareness
13- red-team
14- phishing
15- human-risk
16version: '1.0'
17author: mahipal
18license: Apache-2.0
19atlas_techniques:
20- AML.T0088
21- AML.T0052
22nist_ai_rmf:
23- GOVERN-6.2
24- MAP-5.2
25d3fend_techniques:
26- File Metadata Consistency Validation
27- Application Protocol Command Analysis
28- Identifier Analysis
29- Content Format Conversion
30- Message Analysis
31nist_csf:
32- ID.RA-01
33- GV.OV-02
34- DE.AE-07
35mitre_attack:
36- T1598.004
37- T1566.004
38- T1589
39- T1591
40- T1598
41source: https://github.com/mukul975/Anthropic-Cybersecurity-Skills
42source_commit: 04450304b12645cb2b974ab96d28c0664758a88d
43metadata:
44 source: https://skillmd.com/skills/yanacuti1121/conducting-social-engineering-pretext-call
45---
46
47# Conducting Social Engineering Pretext Call
48
49## Overview
50
51A pretext call (vishing) is a social engineering technique where an attacker impersonates a trusted authority figure over the phone to manipulate targets into divulging sensitive information, performing actions, or granting access. In red team engagements, pretext calls test the human element of security controls, measuring employee adherence to verification procedures and security awareness training effectiveness. MITRE ATT&CK maps this to T1566.004 (Phishing for Information: Voice) and T1598 (Phishing for Information).
52
53
54## When to Use
55
56- When conducting security assessments that involve conducting social engineering pretext call
57- When following incident response procedures for related security events
58- When performing scheduled security testing or auditing activities
59- When validating security controls through hands-on testing
60
61## Prerequisites
62
63- Written authorization specifying social engineering scope and boundaries
64- List of approved target employees (usually provided by client)
65- OSINT research on targets and organization
66- Spoofed caller ID capability (authorized for testing)
67- Call recording equipment (with legal consent as required)
68- Pretext scenarios approved by client
69
70## MITRE ATT&CK Mapping
71
72| Technique ID | Name | Tactic |
73|---|---|---|
74| T1566.004 | Phishing: Voice | Initial Access |
75| T1598 | Phishing for Information | Reconnaissance |
76| T1598.003 | Phishing for Information: Spearphishing Voice | Reconnaissance |
77| T1589 | Gather Victim Identity Information | Reconnaissance |
78| T1591 | Gather Victim Org Information | Reconnaissance |
79
80## Phase 1: OSINT and Target Research
81
82```bash
83# LinkedIn employee enumeration
84theHarvester -d targetcorp.com -b linkedin -l 200
85
86# Company org chart and employee roles
87# Review LinkedIn, corporate website "About Us" / "Team" pages
88
89# Technology stack identification
90# Check job postings for technology references (VPN vendor, email, helpdesk tool)
91
92# Phone system identification
93# Call main line, note IVR options, department names, extension patterns
94```
95
96Key intelligence to gather:
97- Internal helpdesk phone number and procedures
98- IT department names and staff
99- VPN/remote access vendor (Cisco AnyConnect, Fortinet, Pulse Secure)
100- Corporate email format (first.last, flast, etc.)
101- Recent events (mergers, office moves, system upgrades)
102- Employee names, titles, departments
103
104## Phase 2: Pretext Development
105
106### Common Pretext Scenarios
107
108**IT Helpdesk Impersonation (Most Effective):**
109> "Hi, this is [name] from the IT Service Desk. We're migrating everyone to the new VPN client this week, and I see your account hasn't been updated yet. I need to verify your current credentials to ensure the migration goes smoothly. Can you confirm your username and current password?"
110
111**Vendor/Contractor:**
112> "Hi, I'm [name] from [known vendor]. We're doing an emergency patch deployment for [product] and I need remote access to your system. Could you help me connect via TeamViewer?"
113
114**Executive Assistant (Authority):**
115> "This is [name] calling on behalf of [CFO name]. [He/She] needs an urgent wire transfer processed for a deal that's closing today. I'll email you the details, but we need this done in the next hour."
116
117**Building/Facilities:**
118> "Hi, this is [name] from facilities management. We're updating the badge access system this weekend. I need to confirm your employee ID and current badge number so your access isn't interrupted."
119
120### Pretext Checklist
121
122- [ ] Is the pretext believable for this organization?
123- [ ] Does it create appropriate urgency without being threatening?
124- [ ] Does it align with OSINT findings (real dept names, real systems)?
125- [ ] Does it have a plausible reason for requesting information?
126- [ ] Is there a fallback if the target pushes back?
127- [ ] Has the client approved this specific pretext?
128
129## Phase 3: Call Execution
130
131### Call Structure
132
1331. **Introduction** (10 seconds): State name, department, reason for calling
1342. **Building rapport** (30 seconds): Reference something real (recent event, shared context)
1353. **Authority establishment** (20 seconds): Reference manager name, ticket number, urgency
1364. **Information request** (30 seconds): Ask for the target information naturally
1375. **Handling objections**: If challenged, respond calmly with prepared answers
1386. **Closing** (10 seconds): Thank them, leave no suspicion
139
140### Objection Handling
141
142| Objection | Response |
143|---|---|
144| "Can I call you back?" | "Of course, call the main helpdesk line and ask for [name]. But this needs to be done by EOD." |
145| "I need to verify this" | "Absolutely, I appreciate your diligence. You can check with [manager name]." |
146| "I was told never to give passwords" | "You're right, and normally we wouldn't ask. This is a special case because [reason]. I can have my manager call you." |
147| "What's your employee ID?" | Pivot: "It's [made-up ID]. Listen, I have 50 more people to call today. Can we just get this done?" |
148| "I'll email IT instead" | "Sure, but the system migration happens tonight. If it's not done by then..." |
149
150## Phase 4: Data Collection and Metrics
151
152Track the following for each call:
153
154| Metric | Description |
155|---|---|
156| Target Name | Employee called |
157| Department | Target's department |
158| Date/Time | When call was made |
159| Duration | Length of call |
160| Pretext Used | Which scenario |
161| Information Obtained | What was disclosed |
162| Credential Disclosed | Yes/No (and type) |
163| Verification Attempted | Did target try to verify caller? |
164| Reported to Security | Did target report the call? |
165| Social Engineering Score | 1-5 susceptibility rating |
166
167## Phase 5: Reporting
168
169### Success Metrics
170
171| Metric | Target | Result |
172|---|---|---|
173| Credential Disclosure Rate | <10% | XX% |
174| Sensitive Info Disclosure Rate | <20% | XX% |
175| Verification Rate | >80% | XX% |
176| Security Reporting Rate | >50% | XX% |
177
178## Ethical and Legal Considerations
179
1801. **Always obtain written authorization** before conducting vishing tests
1812. **Never use threatening language** or create genuine fear
1823. **Document consent** and legal requirements for call recording
1834. **Protect disclosed credentials** - immediately report to client
1845. **Debrief targets** after the engagement if client approves
1856. **Never publicly identify** specific employees who failed
1867. **Comply with telecommunications laws** in your jurisdiction
187
188## References
189
190- Verizon DBIR 2025: 74% of breaches involve human element
191- MITRE ATT&CK T1598: https://attack.mitre.org/techniques/T1598/
192- Social Engineering Penetration Testing by Gavin Watson (Syngress)
193- The Art of Deception by Kevin Mitnick (Wiley)
194- NIST SP 800-50: Building an Information Technology Security Awareness and Training Program