Now active in
🇳🇬 Nigeria 🇬🇧 United Kingdom 🇺🇸 United States 🇰🇪 Kenya 🇿🇦 South Africa and 99 other countries
Cohort 02 · Applications open

AI in
Cybersecurity

Attackers already use AI. Four weeks, live, to make sure defenders do it better, threat analysis, detection pipelines, and the judgement to know when a model is wrong.

8Live classes
4Weeks, end to end
1Security workflow you ship
VerifiedField certificate
Duration
4 weeks
Format
Live, online
Timezone
Africa / Lagos
Outcome
Expert Practitioner Certificate
01What you'll walk away with

Six things you'll own
by the final week

Not topics you sat through: artefacts and habits you can show a hiring manager or apply to Monday's sprint.

01
A prompting system for threat work

Structure that gets usable intelligence out of a model instead of confident-sounding noise you then have to disprove.

02
A triage playbook you can defend

How to put AI in front of your alert queue without letting it quietly close the one incident that mattered.

03
A working detection pipeline

Built, tuned, and measured, with the false-positive rate written down and defended in front of your cohort.

04
A red-team mental model

What AI makes cheap for an attacker: phishing at scale, recon, and payloads that read as ordinary traffic.

05
A policy for AI in the SOC

What never goes into a model, client data, live IOCs, credentials, and how to stay inside that line under pressure.

06
A 30-day hardening plan

The three changes worth making at your own organisation first, written for your stack, not a generic checklist.

02Curriculum · 8 classes over 4 weeks

Four weeks.
One lifecycle.

Each week closes a loop. You finish with something that runs, not notes you'll never reopen.

Week 01
01
Classes 1–2

Foundations, and where AI actually helps in security

How these systems behave in a security context, what they are reliably good at, and the data you must never hand them. Ends with prompting that produces intelligence you can act on.

  • How LLMs behave in security contexts
  • Prompting for threat analysis and intel
  • AI-driven threat intelligence platforms
  • Data-security limits of AI in a SOC
  • What to never put in a prompt
  • Reading model output like an analyst
Week 02
02
Classes 3–4

Attack and defence, both sides of the same tooling

The week the threat model changes. You use the same AI tooling an attacker would, then build the detection that catches it.

  • AI-assisted penetration testing
  • SIEM triage and alert-noise reduction
  • Automated vulnerability scanning
  • Ethical recon with AI tooling
  • Building a detection pipeline
  • Phishing and social engineering at scale
Week 03
03
Classes 5–6

Operational toolkit: response, compliance, governance

Moving from experiments to things that survive an audit and a 3am incident. Playbooks, automation, and the paper trail that makes them defensible.

  • AI-integrated incident response playbooks
  • Compliance automation dashboards
  • Custom detection model prototyping
  • GRC workflow automation
  • Evidence and audit trails
  • When automation must hand back to a human
Week 04
04
Classes 7–8

Capstone build and live defence

You ship a working AI-powered security workflow and then justify every decision to a practitioner and your peers. Anyone can wire up a model. Few can defend the thresholds they set.

  • Build a live AI security workflow
  • Tune and measure false positives
  • Write the operating playbook
  • Peer assessment round
  • Live defence to your cohort
  • Expert Practitioner Certificate
03How the sprint runs

Run as an operation,
not a lecture series

Four weeks shaped like the incident lifecycle you already work in: assess, detect, respond, then prove it held.

Phase 01 · Assess

Establish the baseline

Before any tooling, you map what you are actually defending and where AI has no business being. Most people leave this session with a shorter list of things to automate than they arrived with.

Phase 02 · Detect

Build the detection

Live sessions against alert data that behaves like yours: noisy, incomplete, occasionally misleading. You tune thresholds and learn what a model quietly gets wrong.

Analyst working in a security operations room
Phase 03 · Respond

Rehearse the response

Playbooks tested under time pressure with your cohort, including the handback rule: the point at which automation must stop and a human takes the decision.

Two engineers reviewing a threat dashboard
Phase 04 · Prove

Defend it, then certify

A live capstone defence where you justify every threshold you set, followed by a field-verified Expert Practitioner Certificate any employer can check.

04Tools & platforms

The stack you'll actually work in

Model-agnostic by design. You learn to choose, not to depend.

Claude
OpenAI
Gemini
GitHub Copilot
Cursor
Perplexity
n8n
Notion
Midjourney
DeepSeek
Mistral
Ollama
LangChain
Your own
stack

Tools our practitioners build with. Brixgate is not affiliated with these companies.

05Fit check

Worth being honest
about who this suits

We'd rather you self-select out now than sit through four weeks that weren't built for you.

This is for you if…
  • You work in security already, SOC, blue team, GRC, or infrastructure with security on your plate.
  • You have at least a year of hands-on professional experience.
  • You've tried AI tools for security work and suspect you're using them shallowly.
  • You want to cut alert noise without losing the alert that mattered.
  • You're comfortable having your detection logic reviewed in front of peers.
This isn't for you if…
  • You're new to security. Get grounding in fundamentals first.
  • You want a passive, watch-at-2x course. Nothing here is pre-recorded.
  • You're looking for an offensive-security certification. This is not an OSCP substitute.
  • You already build detection models full time. This will be too foundational.
  • You can't spare a few hours a week for four weeks.
Not sure where you land? Take the 90-second check
06The sprint & your practitioner

From assessment
to certificate

Four moves, one practitioner, no filler in between.

Week 0
Field assessment

We map where you actually are so the sprint starts at the right altitude, not at the beginning of a syllabus.

Week 1
Placed in a cohort

A small group of engineers with the same problems, led by a practitioner who has shipped AI-assisted code in production.

Weeks 2–4
Build every week

Live sessions and something to ship between each one. Reviewed by peers and the practitioner, not auto-graded.

End of sprint
Defend & certify

Live capstone defence, then a field-verified certificate any employer can check.

·Who's teaching it
Francis Ayomide Adedeji
Francis Ayomide Adedeji
AI Engineer & Educator · AI-Native Software Engineer
20+ live sessions delivered

Francis has spent years designing, deploying and teaching AI systems across education, fintech and enterprise environments. He works on agentic AI workflows, RAG architectures and developer enablement, building the tools that close the gap between AI research and production engineering.

Core expertise
Agentic AIRAG SystemsPythonn8nLangChain
07Upcoming start dates

Pick a cohort

Groups stay small on purpose. When a cohort fills, it closes.

Loading…Fetching cohorts
08Alumni

What changed
for them

Specific outcomes from engineers who finished the sprint.

I cut our triage backlog roughly in half in the first fortnight after the programme, not by automating everything, but by working out which alerts a model should never be allowed to close.
SA
Security Analyst
Brixgate alumnus · Cohort 01
The attack week genuinely changed how I think. Seeing how cheap convincing phishing has become made me rewrite our whole awareness programme the following month.
SE
Security Engineer
Brixgate alumnus · Cohort 01
I left with a detection pipeline, a written playbook and a false-positive rate I could actually defend to my head of security. That last part is what got me taken seriously.
IR
Incident Responder
Brixgate alumnus · Cohort 01
09Why it pays off

What the fee
actually buys

AI-native engineers ship faster, review smarter and negotiate better. You leave with the workflows, the judgement and an artefact that proves both.

1×

attacker using AI is enough to change your threat model. Most organisations have not adjusted theirs

Brixgate practitioner briefing
4 wks

from where you are now to a defended capstone and a verifiable certificate

Brixgate programme length
0

live classes, every one taught by a practitioner who has run this in production

Programme structure
This programme
  • Live sessions with a working practitioner
  • Small cohort: your work actually gets reviewed
  • A deployed capstone you can show in interviews
  • Field-verified certificate, checkable by employers
  • Peers you keep after the four weeks end
A self-paced video course
  • Pre-recorded, filmed before the last model shipped
  • Nobody reads your code or tells you it's wrong
  • A completion badge, not evidence of judgement
  • Most people stop around lesson four
  • No one to ask when you're stuck at 11pm
10Investment

One fee. Everything included.

No upsells, no locked modules. Scholarship places are applied automatically at checkout.

Loading pricing…
Paying for a team? Talk to us about seats
11FAQ

Questions people
actually ask

Still unsure? Message us on WhatsApp and a human will answer.

Be First In Line

Ready to Start?
Join the Waitlist.

Drop your details below and we'll notify you the moment enrolment opens, plus you'll get early access before we announce publicly.

✓ First access before public launch
✓ Exclusive early-bird pricing
✓ No commitment, just your spot in the queue

Ready to Become an AI-Native
Software Engineer?

Cohort 1 opens June 22, 2026. Seats are limited. Apply in under 2 minutes, no essays, no references required.

Apply Now Validate Your Level First
↑