Cyber security · 06
Red team & social engineering testing people, process and detection.
Attackers do not stick to one system. We run objective-based exercises across technology, people and process to see whether you would stop, or even notice, a determined attacker.
Overview
Most breaches start with a message, not an exploit. We test both.
A red team exercise starts with an objective, for example reaching the finance system or a customer database, and uses whatever realistic route gets there: phishing, a phone call, a weak service, a reused password.
Afterwards you get the full story of the attack, where you could have stopped it, and a clear list of changes to people, process and technology.
Standards & frameworks
- MITRE ATT&CK
- CREST-aligned
- PTES
- NCSC guidance
What we test
What's in scope.
And what we look for.
01 · People
Social engineering. Run carefully, with agreed rules and no blame.
Phishing campaigns
Realistic email campaigns measuring clicks, credential entry and reporting.
Pretexting
Phone and message-based attempts against help desks and staff.
MFA fatigue and reset abuse
Testing whether account recovery can be talked around.
Awareness findings
Patterns and recommendations, never individual blame.
02 · Adversary simulation
Red team. End-to-end attack against an agreed objective.
Initial access
Phishing, exposed services and credential attacks.
Persistence and movement
Moving through the environment as a real attacker would.
Detection testing
Whether your monitoring and SOC spot and respond to the activity.
Purple team debrief
Optional replay with your defenders to tune detection.
Process
How a test runs, start to finish.
- 1
Plan
Objectives, rules of engagement, legal approvals and a small trusted contact group.
- 2
Reconnaissance
Open-source research on your organisation, staff exposure and technology.
- 3
Execute
Controlled phishing, pretexting and technical attacks towards the objective.
- 4
Debrief
Attack narrative, timeline, detection gaps and prioritised changes.
Deliverables
What ships with
every exercise.
One report for two audiences: leadership gets the risk, engineers get the evidence and the fix.
Read the sample report →“Thank you for protecting MOD's systems and keeping us secure.”
A penetration test tries to find as many vulnerabilities as possible in a defined scope. A red team pursues one objective, by any realistic route, and also tests whether you detect and respond.
No. We report patterns and process gaps, not individuals. The aim is to improve controls and training, not blame people.
Everything is agreed in writing beforehand, with authorisation from the right people, defined limits and a contact who can stop the exercise at any time.
Yes. A standalone phishing or social engineering assessment is a common starting point before a full red team.
Scope your red team & social engineering.
Get a fixed quote.
A developer or security engineer reads every enquiry and replies, not a salesperson.
- Fixed quote after a short scoping call
- NDA available before you share details
- Remediation and retest on every security engagement