--- name: conducting-social-engineering-pretext-call-72bf029981a1 description: Plan and execute authorized vishing (voice phishing) pretext calls to assess employee susceptibility to social engineering and evaluate security awareness controls. domain: cybersecurity subdomain: red-teaming tags: - social-engineering - vishing - pretext-call - security-awareness - red-team - phishing - human-risk version: '1.0' author: mahipal license: Apache-2.0 atlas_techniques: - AML.T0088 - AML.T0052 nist_ai_rmf: - GOVERN-6.2 - MAP-5.2 d3fend_techniques: - File Metadata Consistency Validation - Application Protocol Command Analysis - Identifier Analysis - Content Format Conversion - Message Analysis nist_csf: - ID.RA-01 - GV.OV-02 - DE.AE-07 mitre_attack: - T1598.004 - T1566.004 - T1589 - T1591 - T1598 mitre_f3: version: '1.1' tactics: - reconnaissance - initial-access - stealth techniques: - id: T1598 name: Phishing for Information tactic: reconnaissance source: attack - id: F1034 name: Interactive Voice Response Mapping tactic: reconnaissance source: f3 - id: F1029 name: Gather Customer Information tactic: reconnaissance source: f3 - id: F1032 name: Impersonate Official tactic: initial-access source: f3 - id: F1040 name: Phone Number Spoofing tactic: stealth source: f3 - id: F1040.002 name: 'Phone Number Spoofing: Official Phone Number Spoofing' tactic: stealth source: f3 --- # 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 ```bash # 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 - [ ] Is the pretext believable for this organization? - [ ] Does it create appropriate urgency without being threatening? - [ ] Does it align with OSINT findings (real dept names, real systems)? - [ ] Does it have a plausible reason for requesting information? - [ ] Is there a fallback if the target pushes back? - [ ] Has the client approved this specific pretext? ## Phase 3: Call Execution ### Call Structure 1. **Introduction** (10 seconds): State name, department, reason for calling 2. **Building rapport** (30 seconds): Reference something real (recent event, shared context) 3. **Authority establishment** (20 seconds): Reference manager name, ticket number, urgency 4. **Information request** (30 seconds): Ask for the target information naturally 5. **Handling objections**: If challenged, respond calmly with prepared answers 6. **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 1. **Always obtain written authorization** before conducting vishing tests 2. **Never use threatening language** or create genuine fear 3. **Document consent** and legal requirements for call recording 4. **Protect disclosed credentials** - immediately report to client 5. **Debrief targets** after the engagement if client approves 6. **Never publicly identify** specific employees who failed 7. **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 --- Source attribution: hironow Original project: https://github.com/hironow/cyber/blob/20efb3a6a2a9e7ebbde38ed32325979866110540/.agents/skills/conducting-social-engineering-pretext-call/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to the Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by the Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding any notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. Please do not remove or change the license header comment from a contributed file except when necessary. Copyright 2026 mukul975 Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: hironow Original project: https://github.com/hironow/cyber/blob/20efb3a6a2a9e7ebbde38ed32325979866110540/.agents/skills/conducting-social-engineering-pretext-call/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering, Marketing, Sales Roles: Customer Success Manager, PR & Communications, Security Engineer Specialties: Specialty not specified Tools: Tool not specified Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 4db888b69a51dde16bec0912df98d5c8bdb8836431d9f264d63cb37861f3f820