Social Engineering & Phishing
We Don't Break in.
We Get Invited.
Phishing, phone, and physical social engineering tests from Red Siege consultants that measure how easily your people and processes can be talked out of access.
Your People Are Part of the Attack Surface
Email filters and MFA have made phishing harder, but attackers adapt. They message staff on Microsoft Teams, pose as IT on the phone, or walk in with the morning crowd. Red Siege consultants research your organization the way an attacker would, then test your people and processes with realistic phishing, phone calls, and, if you want it, physical entry. The point is to find where a process can be bypassed, which teams need more support, and what to change so the next request gets verified.
Targeted Phishing
Realistic emails, and messages through channels like Microsoft Teams, that test whether your users spot a threat and report it.
Vishing and Help Desk
Calls that pose as employees to your help desk, or as IT to your employees, to test whether identity checks hold up.
Physical Entry
Optional on-site tests of whether someone can talk, tailgate, or badge their way into your building.
Fixes, Not Blame
Findings tied to the process that failed, not the employee, with fixes like call-back checks before account changes.
Our Approach
How We Test Your People and Processes
Every engagement follows the same four steps, scaled to your organization and the methods in scope.
-
Start with what would hurt
We start by asking which data, systems, or processes would hurt most if an attacker talked their way in, and which methods are in scope: phishing, phone calls, or physical entry. We agree on pretexts that feel real without threatening anyone’s job, and for physical tests, a signed authorization letter with contacts who can vouch for us at any hour.
-
Research you like an attacker
Using open-source intelligence such as LinkedIn, we build the target list an attacker would: new hires, less technical departments, or a cross-section you choose. Pretexts come from your own news, events, and vendors. We also check whether SPF, DKIM, and DMARC are set up so a spoofed message can’t pass as internal.
-
Test the people and the process
Broad phishing shows who clicks, who enters credentials or runs a file, and who reports it. Slower, targeted campaigns also test your email filters and how fast your security team blocks us. Phone calls test your help desk and the teams an attacker would try next. Physical tests check whether someone can walk in and plug in a device.
-
Report what held and what didn’t
An executive summary, results reported by role and department rather than by name, findings tied to the process that failed, positive findings for what your team did well, short- and long-term recommendations, and a validation section for each finding so your team can confirm the fix.
Training Helps. Process Holds the Line.
In one Red Siege engagement, a well-trained help desk never broke protocol, no matter the ruse. The way in was a different support line, which handed over the employee ID numbers the help desk used to verify callers. Testing only your strongest team tells you little. We test the whole path an attacker would take, so you know which processes hold,
because an attacker only needs one person to say yes.
Get Offensive Now
“The people element is very exploitable, and it’s something that works for us almost all the time.”
Details on Social Engineering & Phishing
In the SiegeCast Effective Phishing Pretexts, Senior Security Consultants Corey Overstreet and Jason Downey walk through how they build a phishing campaign: who they target first, the deadlines and follow-ups that get a reply, lookalike domains and links too long to read, cloned login pages, and why they avoid pretexts that threaten anyone’s job. Watch it to see what your users are up against.
Watch the SiegeCast