CPD

Network models artefact templates and rubrics

These templates are designed to be quick, defensible, and easy to explain. Use the rubric to check quality. Keep the output as CPD evidence.

Export CPD evidenceBack to course

How to use this

Practical, not perfection
  1. Pick the tier you are studying and copy the template into your notes.
  2. Complete it for one real example (work, a side project, or a safe fictional scenario).
  3. Use the rubric to tighten it until it is defensible.
  4. Paste a short reflection into your CPD record: what you assumed, what evidence you would keep, and what you would do next.

Foundations. Encapsulation storyboard

Template + rubric + example

Template

Rubric (what “good enough” looks like)

  • Layering is correct and uses concrete protocol terms.
  • Evidence is identified (what you would log/measure/keep).

Worked example (short)

Example (short):
Flow: HTTPS request.
Evidence: curl -v, DNS output, tcpdump filter (safe environment).

Applied. Troubleshooting worksheet

Template + rubric + example

Template

Rubric (what “good enough” looks like)

  • Hypotheses are ordered and evidence-based.
  • Next actions are concrete and realistic.
  • Evidence is identified (what you would log/measure/keep).

Worked example (short)

Example (short):
Symptom: site loads slowly.
Evidence: DNS timing, TLS handshake time, RTT.

Practice. Security by layer map

Template + rubric + example

Template

Rubric (what “good enough” looks like)

  • Controls are placed where they actually work.
  • Trade-offs are stated, not implied.
  • Evidence is identified (what you would log/measure/keep).

Worked example (short)

Example (short):
L7: authz checks; L4: rate limits; L3: segmentation.