Executing Phishing Simulation Campaign
Overview
Cybersecurity skill for executing phishing simulation campaign. Follows industry best practices and security standards.
When to Use
Trigger phrases:
"executing phishing simulation campaign"
"Executes authorized phishing simulation campaigns to assess an organization's su"
Measuring employee susceptibility to phishing attacks as part of a security awareness program
Testing the effectiveness of email security controls (secure email gateway, DMARC, SPF, DKIM)
Conducting the social engineering component of a red team exercise to gain initial access
Establishing a baseline for phishing susceptibility before deploying security awareness training
Validating that incident response procedures work when employees report suspicious emails
Do not use without explicit written authorization from the organization's leadership, for actual credential theft beyond the authorized scope, for targeting individuals personally rather than professionally, or for sending phishing emails that could cause psychological harm or legal liability.
When NOT to Use
- When you lack proper authorization for testing
- For production systems without change management
- When the task requires legal or compliance expertise beyond technical scope
Prerequisites
- Written authorization from executive leadership specifying the campaign scope, target groups, and escalation procedures
- Coordination with the IT/security team to whitelist the sending infrastructure (or test whether it bypasses controls, depending on scope)
- GoPhish or equivalent phishing platform configured with a sending domain, SMTP relay, and landing page infrastructure
- Phishing domain registered and configured with SPF, DKIM, and DMARC records to maximize deliverability
- Employee email list from HR, organized by department for targeted campaigns
- Incident response team briefed on the campaign timeline and escalation procedures
Workflow
# Example: IOC detection
import re
IOC_PATTERNS = {
"ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
"domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
"hash_md5": r"\b[a-f0-9]{32}\b",
"hash_sha256": r"\b[a-f0-9]{64}\b",
}
def extract_iocs(text: str) -> dict:
return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}
- Define Objectives — Clarify the goals and scope for phishing simulation campaign.
- Gather Resources — Collect tools, data, and access needed for phishing simulation campaign.
- Execute Process — Carry out phishing simulation campaign operations methodically.
- Verify Quality — Check results against acceptance criteria.
- Document Outcomes — Record findings, decisions, and next steps.
Tools
- Analysis Platform — Data processing and visualization
- Collaboration Tools — Team coordination and knowledge sharing
Process
- Reconnaissance — Gather target information, identify attack surface, enumerate services
- Analysis/Exploitation — Execute the technique, analyze results, document findings
- Reporting — Document IOCs, write findings, provide remediation recommendations
Verification
Anti-Rationalization Table
| Rationalization |
Reality |
| "We are too small to be targeted" |
Automated attacks target everyone. Size does not matter. |
| "Security slows us down" |
A breach slows you down 100x more. Build security in from the start. |
| "We will fix it after launch" |
Vulnerabilities in production are exploited within hours. Fix before deploy. |
1---2name: executing-phishing-simulation-campaign3description: Use when executes authorized phishing simulation campaigns to assess4 an organization's susceptibility to email-based social engineering attacks. The5 tester designs realistic phishing scenarios, builds credential harvesting infrastructure,6 sends targeted phishing emails, and tracks open rates, click-through rates, and7 credential submission rates to measure human security awareness. Use when working8 with executing phishing simulation campaign.9domain: cybersecurity10tags:11- phishing-simulation12- social-engineering13- GoPhish14- email-security15- security-awareness16subdomain: penetration-testing17version: 1.0.018author: oyi7719license: Apache-2.020nist_csf:21- ID.RA-0122- ID.RA-0623- GV.OV-0224- DE.AE-0725category: cybersecurity26metadata:27 source: https://skillmd.com/skills/oyi77/executing-phishing-simulation-campaign28---2930# Executing Phishing Simulation Campaign3132## Overview3334Cybersecurity skill for executing phishing simulation campaign. Follows industry best practices and security standards.3536## When to Use37**Trigger phrases:**38- "executing phishing simulation campaign"39- "Executes authorized phishing simulation campaigns to assess an organization's su"404142- Measuring employee susceptibility to phishing attacks as part of a security awareness program43- Testing the effectiveness of email security controls (secure email gateway, DMARC, SPF, DKIM)44- Conducting the social engineering component of a red team exercise to gain initial access45- Establishing a baseline for phishing susceptibility before deploying security awareness training46- Validating that incident response procedures work when employees report suspicious emails4748**Do not use** without explicit written authorization from the organization's leadership, for actual credential theft beyond the authorized scope, for targeting individuals personally rather than professionally, or for sending phishing emails that could cause psychological harm or legal liability.495051## When NOT to Use5253- When you lack proper authorization for testing54- For production systems without change management55- When the task requires legal or compliance expertise beyond technical scope565758## Prerequisites5960- Written authorization from executive leadership specifying the campaign scope, target groups, and escalation procedures61- Coordination with the IT/security team to whitelist the sending infrastructure (or test whether it bypasses controls, depending on scope)62- GoPhish or equivalent phishing platform configured with a sending domain, SMTP relay, and landing page infrastructure63- Phishing domain registered and configured with SPF, DKIM, and DMARC records to maximize deliverability64- Employee email list from HR, organized by department for targeted campaigns65- Incident response team briefed on the campaign timeline and escalation procedures6667## Workflow6869```python70# Example: IOC detection71import re7273IOC_PATTERNS = {74 "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",75 "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",76 "hash_md5": r"\b[a-f0-9]{32}\b",77 "hash_sha256": r"\b[a-f0-9]{64}\b",78}7980def extract_iocs(text: str) -> dict:81 return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}82```83841. **Define Objectives** — Clarify the goals and scope for phishing simulation campaign.852. **Gather Resources** — Collect tools, data, and access needed for phishing simulation campaign.863. **Execute Process** — Carry out phishing simulation campaign operations methodically.874. **Verify Quality** — Check results against acceptance criteria.885. **Document Outcomes** — Record findings, decisions, and next steps.8990## Tools9192- **Analysis Platform** — Data processing and visualization93- **Collaboration Tools** — Team coordination and knowledge sharing949596## Process97981. **Reconnaissance** — Gather target information, identify attack surface, enumerate services991. **Analysis/Exploitation** — Execute the technique, analyze results, document findings1001. **Reporting** — Document IOCs, write findings, provide remediation recommendations101102## Verification103104- [ ] All phishing simulation campaign procedures executed completely and documented105- [ ] Findings validated against multiple data sources106- [ ] False positives identified and filtered107- [ ] Results documented with evidence and timestamps108- [ ] Recommendations provided with risk-based prioritization109110## Anti-Rationalization Table111112| Rationalization | Reality |113|---|---|114| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |115| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |116| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |