Skip to main content

Core path

Your path through this level

Progress saves in this browser and syncs after you sign in

Completed
0 of 5
You will be able to
  • Place controls more accurately by matching them to the function and reachability they govern.
  • Use logs, timings, and captures as complementary evidence rather than competing religions.
  • Explain segmentation, packet evidence, and incident notes with operational precision.
Optional
Full module map
Use this if you want the shape of the level before you start
Show
Place controls where they apply. A control that cannot help is theatre.
Open
Prerequisites
  • Comfort with earlier modules in this track
  • Ability to explain trade-offs and risks without jargon
Outcomes
  1. Explain controls that can actually work in your own words and apply it to a realistic scenario.
  2. Place controls where they apply. A control that cannot help is theatre.
  3. Check the assumption "Controls match failure modes" and explain what changes if it is false.
  4. Check the assumption "You can test controls" and explain what changes if it is false.
Practice
  • Solve a complex scenario with explicit assumptions and constraints
  • Write one mitigation plan and one fallback plan
Artefact and failure modes
  • A concise design or governance brief that can be reviewed by a team
  • Edge controls for app bugs. A firewall cannot fix broken access control inside your code.
  • Overtrusting segmentation. Segmentation helps. It does not replace identity and authorisation.
Observability matters when signals trigger action, not only dashboards.
Open
Prerequisites
  • Comfort with earlier modules in this track
  • Ability to explain trade-offs and risks without jargon
Outcomes
  1. Explain signals to action in your own words and apply it to a realistic scenario.
  2. Observability matters when signals trigger action, not only dashboards.
  3. Check the assumption "Signals are measurable" and explain what changes if it is false.
  4. Check the assumption "Response is defined" and explain what changes if it is false.
Practice
  • Solve a complex scenario with explicit assumptions and constraints
  • Write one mitigation plan and one fallback plan
Artefact and failure modes
  • A concise design or governance brief that can be reviewed by a team
  • Dashboards without action. A dashboard that nobody uses in decisions is decoration.
  • Alert fatigue. Too many alerts teach people to ignore them. Tune until alerts mean something.
Packet capture is evidence. Use it safely and ethically.
Open
Prerequisites
  • Comfort with earlier modules in this track
  • Ability to explain trade-offs and risks without jargon
Outcomes
  1. Explain capture to interpretation in your own words and apply it to a realistic scenario.
  2. Packet capture is evidence. Use it safely and ethically.
  3. Check the assumption "Ethical boundary is clear" and explain what changes if it is false.
  4. Check the assumption "Filters are deliberate" and explain what changes if it is false.
Practice
  • Solve a complex scenario with explicit assumptions and constraints
  • Write one mitigation plan and one fallback plan
Artefact and failure modes
  • A concise design or governance brief that can be reviewed by a team
  • Unsafe experimentation. Learning should not become exploitation. Keep practice safe.
  • Overinterpreting. One capture is one snapshot. Be careful about what you conclude.
Module 3.4Blast radius
Segmentation reduces blast radius. It does not eliminate compromise.
Open
Prerequisites
  • Comfort with earlier modules in this track
  • Ability to explain trade-offs and risks without jargon
Outcomes
  1. Explain blast radius in your own words and apply it to a realistic scenario.
  2. Segmentation reduces blast radius. It does not eliminate compromise.
  3. Check the assumption "Segmentation is enforced" and explain what changes if it is false.
  4. Check the assumption "High-risk paths are restricted" and explain what changes if it is false.
Practice
  • Solve a complex scenario with explicit assumptions and constraints
  • Write one mitigation plan and one fallback plan
Artefact and failure modes
  • A concise design or governance brief that can be reviewed by a team
  • Flat networks. Flat networks turn one compromise into many.
  • Hidden trust. If teams assume ‘internal is safe’, segmentation loses meaning.
Module 3.5Next action
The goal is a justified next action, not a clever guess.
Open
Prerequisites
  • Comfort with earlier modules in this track
  • Ability to explain trade-offs and risks without jargon
Outcomes
  1. Explain next action in your own words and apply it to a realistic scenario.
  2. The goal is a justified next action, not a clever guess.
  3. Check the assumption "You can justify" and explain what changes if it is false.
  4. Check the assumption "You can verify" and explain what changes if it is false.
Practice
  • Solve a complex scenario with explicit assumptions and constraints
  • Write one mitigation plan and one fallback plan
Artefact and failure modes
  • A concise design or governance brief that can be reviewed by a team
  • Random changes. Random changes can work once and teach you nothing.
  • No feedback. If you do not measure, you do not learn.
Optional
Planning and evidence
Objectives, timing, and CPD tracking
Show

If you want to start learning now, leave this closed. Come back when you want to plan your practice or keep evidence for CPD. This is guidance and it is not endorsed by awarding bodies. Standards mapping lives on the course overview page.

Learning objectives

What you will be able to do

  1. 1. Place controls more accurately by matching them to the function and reachability they govern.
    Layered failures need control mapping so you can defend decisions.
  2. 2. Use logs, timings, and captures as complementary evidence rather than competing religions.
    Monitoring signals show you where to look, not just that something broke.
  3. 3. Explain segmentation, packet evidence, and incident notes with operational precision.
    Packet captures must be safe and ethical, so we practise that properly.
What comes next
The summary gives you a fast practice loop before real incidents arrive.

What changes at this level

Level expectations

Each level is independent but clearly deeper than the last. This panel makes the jump explicit.

Assessment intent
Practice and Strategy

Operational reasoning, monitoring signals, and layer-aware security controls.

Style
scenario
25 questions
40 min timed
Pass standard
80%
Not externally certified
Evidence you can save (CPD friendly)
  • A security-by-layer map: control, what it prevents, what it detects, and how you test it.
  • A minimal monitoring plan: latency percentiles, loss, DNS success rate, TLS handshake failures, and application errors, plus the runbook links.
  • A short incident narrative written like an operator: timeline, hypothesis, evidence, action, and what you changed so it does not repeat.

CPD timing

Practice and strategy time breakdown

Defensible timing based on page content: reading, labs, checkpoints, and reflection.

Reading
15m
2,198 words × 1.3
Practice
30m
2 × 15m
Checkpoints
25m
5 × 5m
Reflection
40m
5 × 8m
Estimated total
2h 50m
Based on page content
Claimed hours
2h
Includes reattempts + capstone

CPD tracking

Fixed hours for this level are 2. Timed assessment time is included once on pass.

View in My CPD
Progress minutes
0.0 hours

Learning objectives

What you will be able to do

  1. 1. Place controls more accurately by matching them to the function and reachability they govern.
    Layered failures need control mapping so you can defend decisions.
  2. 2. Use logs, timings, and captures as complementary evidence rather than competing religions.
    Monitoring signals show you where to look, not just that something broke.
  3. 3. Explain segmentation, packet evidence, and incident notes with operational precision.
    Packet captures must be safe and ethical, so we practise that properly.
What comes next
The summary gives you a fast practice loop before real incidents arrive.

What changes at this level

Level expectations

Each level is independent but clearly deeper than the last. This panel makes the jump explicit.

Assessment intent
Practice and Strategy

Operational reasoning, monitoring signals, and layer-aware security controls.

Style
scenario
25 questions
40 min timed
Pass standard
80%
Not externally certified
Evidence you can save (CPD friendly)
  • A security-by-layer map: control, what it prevents, what it detects, and how you test it.
  • A minimal monitoring plan: latency percentiles, loss, DNS success rate, TLS handshake failures, and application errors, plus the runbook links.
  • A short incident narrative written like an operator: timeline, hypothesis, evidence, action, and what you changed so it does not repeat.

Learning contract

Practice & Strategy outcomes

About 2 hours

Read the explanation first, then use the tools to test the idea. Skip any tool that is not useful for your goal.

  1. Place controls more accurately by matching them to the function and reachability they govern.
  2. Use logs, timings, and captures as complementary evidence rather than competing religions.
  3. Explain segmentation, packet evidence, and incident notes with operational precision.
Loading content...

Next step

Practise this level, then take the timed assessment

I recommend you start with the practice assessment for Practice and Strategy. It is not timed and it helps you write a clear CPD reflection before the full assessment.

25

Questions

40

Minutes

80%

Pass mark

Practice assessment

Start the practice assessment for Practice and Strategy

It is designed for confidence and evidence, and you can retry as often as you need.

Full assessment

Network models Practice and Strategy assessment

This assessment is timed. It is free to take and you can retry as often as you need.

  • Detailed feedback on every question
  • Pass evidence recorded in your account on pass
  • Personalised recommendations on weak areas

Sign in to save progress and keep your pass record

You can complete the course while signed out, and your progress saves in this browser. Sign in before assessments so your pass record is attached to your account.

Courses and assessments are free. There is no paywall for the learning path, practice questions, or formal assessments.

During timed assessments, copy and the context menu are restricted to reduce casual cheating. Passed assessments are recorded in your account as evidence.