Sixteen weeks on how attacks actually work, how defences are built around them, and where AI helps or quietly makes things worse. You finish able to read an incident and say what you would do next.
Security is one of the few fields where demand has outrun supply for a decade and shows no sign of correcting. These are public industry figures, not ours, and each one is sourced.
Figures describe the industry, not Brixgate outcomes. We are a new programme and we do not have placement statistics to quote yet. When we do, they will appear here with the same sourcing.
This is the shape of a common intrusion. Defenders do not think in tools, they think in timelines like this one, and by week sixteen you will read one the same way.
Addressed correctly, referencing a real project, sent from a domain one character different from a supplier's.
The password is now in somebody else's hands. No alarm has gone off anywhere.
Same account, a country nobody on the team is in, at a time that does not match their working pattern.
Reading mail, finding out who approves payments, learning the shape of the organisation. Nothing is broken yet.
Replies from finance get moved out of sight, so the real owner never sees the conversation happening in their name.
An invoice redirected, or a folder of client data copied out. This is the first moment anybody notices, and it is far too late.
Three of those six steps were catchable with things most organisations already own. Security work is mostly noticing, and noticing is a skill that can be taught from zero.
Most beginner courses start with policies and firewalls. We start with how things actually get broken into, because every defence worth building is a response to something specific.
You cannot defend a system you cannot describe. The unglamorous grounding, done properly.
The attacker's view. Taught so you recognise it, in a closed environment built for it.
The core of the job. Logs, signals and the judgement to tell a real event from noise.
Honestly. It is genuinely useful in some places and actively dangerous in others.
Worked end to end and written up the way a real team would need to read it, including what you could not determine.
Knowing what normal looks like so that unusual announces itself. This is the thing that takes sixteen weeks rather than six.
Where it genuinely speeds up security work, and where trusting it confidently gets people hurt.
Everything runs in a lab environment we provide. Nothing here is ever pointed at a system you do not own.
Cohorts are kept small on purpose. Dates below come straight from our scheduling system, so what you see here is what is actually open.
Cohorts are small on purpose. When the next Cyber Security intake opens, the waitlist hears before the site does.
We will email you the dates, the timetable and the pricing for the next Cyber Security cohort before any of it goes on the site.
If four months is more than you want to commit to right now, the shorter courses get you somewhere useful faster.