Offensive Security Training
Hands-on training from an attacker's perspective
Learn how attackers work, so you can see for yourself what is exposed and where the weak points are.
From penetration testing, bug hunting and reversing to embedded, industrial and AI systems: topics fitted to your technology, worked through hands-on in a controlled lab.
Can our team look at our systems the way an attacker would?
A record of how far each participant got, and the next step for each person and team.
Reviewed
When it fits
- You want developers to see first-hand why reported vulnerabilities matter
Finding problems like the ones in their reports for themselves, in a lab, gets the point across faster than being told why they matter.
- New security hires need to be working fast
We pick only the topics their systems and duties call for, and get them hands-on quickly. The lab record shows what they can now do.
- You want your security team to see systems as an attacker does
Topics fitted to the technology you run, so the team learns together what an attacker would see and where it is weak.
- You are taking on a new field, such as AI or industrial systems
You want people to understand, hands-on and in advance, what attackers go after in a field newly in their care, such as AI services, plant equipment or connected devices.
The SAFE SQUARE approach
Free to try, in a controlled lab
Practice takes place in a controlled lab built to resemble the real thing, so people can try different approaches and hit dead ends for themselves.
Exercises fitted to your stack
Exercises are prepared around the languages, frameworks, cloud and equipment you use, so what people practise carries straight into their work.
An eye for it, not a list of techniques
Rather than memorising techniques, participants learn to find for themselves which clue leads to the next.
Topics
Topics are set to fit your technology and the work your people do. Here are some we often cover.
- Penetration testing
Find and verify real attack paths across web, mobile, API and cloud environments.
- Bug hunting and vulnerability research
Learn to search for unknown vulnerabilities systematically and reproduce them.
- Reversing and malware analysis
Analyse binaries and malware to understand how they behave and what risk they carry.
- IoT, embedded systems and firmware
Work on weaknesses in device firmware and hardware interfaces.
- ICS, OT and SCADA security
Understand how industrial control systems are built and where they can be attacked.
- AI and LLM red teaming
Hands-on work with the misuse of models and AI services, bypassing their safeguards, and data risks.
EXPLOIT Offensive Engineering
We research ways to analyse and verify vulnerabilities and their impact from an attacker's perspective.
Levels and formats
Security staff, developers and newcomers each start at their own level, in the format that fits the goal. Length, group size and difficulty are designed with you, around who takes part and what they need to achieve.
- Workshop
A short session focused on one topic.
- Bootcamp
An immersive course that works through several topics in order.
- One-to-one
Close guidance around an individual's goals.
- Team course
Raising a whole team's level together.
How it runs
Agree goals and level
We agree who takes part, at what level, and what they should be able to do afterwards, then choose the topics and format to fit your technology.
Prepare the lab
We prepare exercises fitted to your technology, and a controlled lab to work in.
Teach and practise
We work through real cases, then participants practise hands-on and work past sticking points with the instructor.
Review and write up
After each exercise we go over what went well and what to strengthen, then write up the practice records and next steps.
What you receive
Records and a next step, so the learning carries on.
Practice records
What was covered and how far each person and team got.
Expert debrief
What went well and what to strengthen, from both the attacker's and the defender's point of view.
Next-step recommendations
The next course or exercise that fits each person and team.
A two-day web and API workshop for a development team
Participants: eight back-end developers · Exercise: a practice service built on the same framework as theirs
| Topic | Result | Record |
|---|---|---|
| Login and session handling | Done | All eight found the weakness and explained what made it dangerous. |
| Per-user access checks | Done | Six found it on their own; two found it after a hint. |
| File upload handling | Partly | The weakness was found, but not followed through to its real impact. |
| Connections to outside services | Not yet | Nobody finished in time; it is taken up again in the next course. |
- Debrief
- The access-check issues are now understood well enough to use in real code reviews. Uploads and outside connections need more work on the underlying principles.
- Next step
- A one-day workshop on uploads and outside connections follows, and the two team leads take one-to-one sessions to sharpen how they review code.