Test the human layer
Social
Engineering
We test how your people and processes respond when someone asks for what they should not get. Phishing, phone pretexts to the help desk and physical entry attempts, all authorized and scoped in writing. You learn which requests worked, which were reported, and which process change closes the gap.
Authorized before attempted
Would someone
hand over the keys?
Every scenario is agreed in writing before it runs, with a trusted contact on your side who knows the plan. Pretexts are mapped to MITRE ATT&CK initial access techniques, and we report on process and controls, not on individual employees.
Phase 01 · Rules & pretexts
Agree what we will try and who knows.
Signed rules of engagement listing every channel, target group, pretext and off limits topic.
- Channels chosen with you: email, phone, SMS, physical entry.
- Pretexts approved in advance, with topics that stay off the table.
- A trusted contact named to confirm we are authorized if challenged.
Phase 02 · Research
Learn what an outsider can learn about you.
A short list of names, roles and processes a real attacker would build pretexts around.
- Public sources reviewed for staff roles, vendors and email formats.
- Help desk and reception procedures observed from the outside.
- Pretexts tailored to how your organization actually works.
Phase 03 · Phishing & vishing
Send the email and make the call.
Who opened, clicked, entered credentials or reported it, measured by group rather than by name.
- Phishing campaigns sent from infrastructure registered for the test.
- Calls to the help desk asking for password resets or MFA changes.
- Capture pages that record a password was entered, not the password.
Phase 04 · Physical entry
Walk in the way a visitor would.
Photos and notes showing how far we got, which doors held and who asked the right question.
- Tailgating and pretexted visits at the sites you approve.
- Badge and visitor processes tested at reception.
- An authorization letter carried on every attempt, with your trusted contact's number on it.
Phase 05 · Report & readout
Fix the process, not the person.
A report that names the process gaps and the control changes that close them.
- Results by channel and group, with the exact pretext used.
- Process fixes for help desk, reception and email controls.
- Material you can reuse in awareness training.
Agree what we will try and who knows.
Signed rules of engagement listing every channel, target group, pretext and off limits topic.
- Channels chosen with you: email, phone, SMS, physical entry.
- Pretexts approved in advance, with topics that stay off the table.
- A trusted contact named to confirm we are authorized if challenged.
Learn what an outsider can learn about you.
A short list of names, roles and processes a real attacker would build pretexts around.
- Public sources reviewed for staff roles, vendors and email formats.
- Help desk and reception procedures observed from the outside.
- Pretexts tailored to how your organization actually works.
Send the email and make the call.
Who opened, clicked, entered credentials or reported it, measured by group rather than by name.
- Phishing campaigns sent from infrastructure registered for the test.
- Calls to the help desk asking for password resets or MFA changes.
- Capture pages that record a password was entered, not the password.
Walk in the way a visitor would.
Photos and notes showing how far we got, which doors held and who asked the right question.
- Tailgating and pretexted visits at the sites you approve.
- Badge and visitor processes tested at reception.
- An authorization letter carried on every attempt, with your trusted contact's number on it.
Fix the process, not the person.
A report that names the process gaps and the control changes that close them.
- Results by channel and group, with the exact pretext used.
- Process fixes for help desk, reception and email controls.
- Material you can reuse in awareness training.
Key benefits
Find the request your team would grant.
Results are reported by group and process, not by name. Staff who were fooled are not singled out, and the fixes land on procedures and controls where they belong.
Phone pretexts aimed at password and MFA resets show whether identity checks hold under pressure. That one process decides whether a single call turns into access.
A click rate alone tells you little. We record who reported each attempt and how your team responded, so you see whether detection works as well as prevention.
What you get
What lands on
your desk.
Three handoffs that point at processes and controls, written so they can be shared without embarrassing anyone.
The document
The report
Each scenario as it ran: the pretext, the channel, what worked and what was reported, with redacted evidence and the process or control change that closes each gap.
The working file
The results tracker
One row per finding with channel, affected process, severity, status and an owner. Group level results sit alongside, so you can measure change when you test again.
The conversation
The readout
A session with the practitioner who ran the scenarios, for leadership and the teams that own the processes. We walk through what happened and agree which fixes come first.
Client case studies
Real engagements.
Documented outcomes.
In their words
"ForgePath has become a trusted security partner for YHB. Their team understands how a CPA firm operates and has helped us build a security program that’s both practical and sustainable."
In their words
"ForgePath has become a trusted security partner for YHB. Beyond helping us comply with FTC Safeguards requirements, they provide the governance, oversight, and guidance we rely on to protect our firm and our clients’ data. Their team understands how a CPA firm operates and has helped us build a security program that’s both practical and sustainable."
Trusted by industry leaders.
Fair questions
Asked by
HR and legal.
Straight answers from the practitioners who do the work. If yours is not here, ask us directly.
Not by default. Results are reported by group and process. If your policy calls for individual follow up, we agree that in writing during scoping. The aim is to fix procedures, not to punish the person who answered the phone.
Physical entry needs written approval from someone with authority over each site, including a landlord or building manager where they control access. Our practitioner carries that letter during every attempt, and your trusted contact can confirm it on the spot.
You decide. We avoid themes that cause real distress, such as layoffs, medical news or family emergencies, unless you approve them in writing. Every pretext is listed in the rules of engagement before anything is sent.
Yes. We recommend both review the rules of engagement before testing starts. They usually help pick the trusted contact, set how results are shared, and know whom to call if an employee reports something unusual.
No. This is a point in time test run by a senior practitioner with tailored pretexts. If you already run a training platform, our results show where it is working and where people still need help.
Ready?
Bring us
the problem.
One conversation with a senior practitioner who has carried this responsibility before. We will tell you what we would do, and whether it is us.








