Targeted phishing
Pretext built from OSINT on your company and team. Multi-touch sequences, custom landing pages, MFA prompt bypass. The kind real attackers run.
Phishing, vishing, and pretext campaigns against your workforce. We measure click rates, credential capture, and detection times, then turn the data into training that actually moves the next quarter's numbers.
Campaign types we run.
Pretext built from OSINT on your company and team. Multi-touch sequences, custom landing pages, MFA prompt bypass. The kind real attackers run.
Calls to your helpdesk, IT, or finance team using tailored pretext. Common targets: password reset, MFA reset, vendor invoice change.
SMS-based campaigns testing mobile-first workforces. Often combined with vishing as a two-channel pretext.
On request. Devices left in parking lots, mailrooms, or shared spaces; pretext visits to reception. Legal coverage required.
Pretext aimed at the C-suite or board. Higher difficulty, higher payoff for adversaries. Usually paired with vishing of the exec assistant.
Account takeover attempts against your IT support workflow. This is where most modern intrusions actually start.
How a social-engineering engagement runs.
What you get back.
By cohort: open rate, click rate, credential entry, MFA bypass success, report rate, time to detection. Industry benchmarks included.
Every pretext we used, with screenshots, copy, and call scripts. Use for tabletop training and detection-rule writing.
If we ran vishing, every call transcribed and classified. Patterns the helpdesk team should learn to spot.
Email-gateway rules, EDR signals, helpdesk verification checklists. Specific to the pretexts that worked.
Targeted curriculum based on what worked. We do not recommend annual click-through training.
On request, a follow-up campaign 90 days post-training. The only honest way to measure whether training worked.
When social engineering is the right test.
Modern intrusions often start with a phone call, not a click. Test the call workflow before the next attacker does.
Find out what it actually catches. The vendor demo is not the same as a real campaign against your users.
New hires onboard every week. Annual training does not catch up. Quarterly campaigns keep the baseline visible.
Cyber-insurance underwriters increasingly ask for phishing test results. SOC 2 and ISO 27001 reference social-engineering testing.
Social-engineering FAQ.
Not by us. We deliver anonymized metrics by cohort. Whether you tie click data to individual records is your HR and legal decision; we recommend against it.
No. The pretext form captures the act of entry. The data field is discarded server-side and logged as a hashed counter.
Yes. Social engineering campaigns produce detection signal. We compare what should have alerted against what your SOC saw.
Required before launch. We provide template authorization, but your legal team owns the final document.
90 days minimum. Sooner and the workforce remembers the pretext; the test no longer measures behavior change.
Most organizations measure click rates and call it done. We measure detection and response too. 30-minute scoping call to design the campaign.