SOC Investigation Report
A simulated EDR alert flags unusual activity on an office laptop during a training shift. All logs and assets are provided samples; no real systems or accounts are involved.
Objective: Triage the alert using the supplied evidence and write a defensive investigation report that separates facts from assumptions and explains the chosen next step.
Inputs, deliverables and rubric
Skills: Alert triage · Log correlation · Evidence handling · Clear reporting
Inputs: Sample EDR alert export · Redacted login and process logs · Mock asset inventory extract
Deliverables: Investigation timeline · Findings with confidence notes · Containment options with rationale
Rubric: Distinguishes observed facts from assumptions · References specific evidence for each claim · Explains why escalation or closure was chosen · Avoids destructive actions and states limitations
how edr detects suspicious activityhow a security alert becomes an incidentwhy verification mattershow weprotect creates incidents
Vulnerability Prioritization Report
A sample scan lists findings across office and production-like lab assets. Generic scores alone do not reflect the business role of each system.
Objective: Rank the findings using asset role, exposure and compensating controls, then explain the reasoning behind the proposed remediation queue.
Inputs, deliverables and rubric
Skills: CVE and CVSS literacy · Asset context · Risk ranking · Stakeholder communication
Inputs: Sample vulnerability scan extract · Mock asset inventory with business roles · List of existing controls
Deliverables: Prioritised remediation queue · Context notes per finding · Short explanation of deferred items
Rubric: Explains why a high generic score is not automatically the top priority · Uses asset and exposure context consistently · Names assumptions and missing data · Proposes verification steps without making real-world changes
what is a cvehow a vulnerability becomes riskwhy cvss is not enoughhow weprotect prioritizes risk
Incident Response Plan
A tabletop exercise describes a suspected account compromise in a training environment with a defined change-approval process.
Objective: Draft a proportionate response plan covering scope, containment options, communication, recovery and verification.
Inputs, deliverables and rubric
Skills: Incident lifecycle · Containment planning · Change control · Documentation
Inputs: Exercise scenario brief · Mock asset and owner list · Sample change-request template
Deliverables: Response plan with stages and owners · Containment option comparison · Verification and closure criteria
Rubric: Defines scope from available evidence · Respects approval and availability constraints · Includes rollback and verification steps · Clearly labels the exercise as simulated
how a security alert becomes an incidenthow containment workshow remediation workswhy verification matters
Zero Trust Access Design
A training organisation wants to reduce lateral movement between lab segments without disrupting normal work.
Objective: Design a defensive access model using identity verification, least privilege, device health and segmentation.
Inputs, deliverables and rubric
Skills: Zero Trust principles · Least privilege · Segmentation · Diagram communication
Inputs: Mock network diagram · Sample role list · Example access requests
Deliverables: Access design diagram · Policy summary per role · Rationale and trade-off notes
Rubric: Checks identity and device signals before granting access · Limits access to what each role actually needs · Explains how segmentation reduces the blast radius · Does not present the design as a deployed production system
what happens when you log inwhat is zero trusthow a cyberattack travelshow attackers move laterally
Cloud Security Review
A sample cloud service diagram shows an API, a workload and log sources with a shared-responsibility boundary.
Objective: Review the design for defensive gaps and document questions, evidence needs and proportionate recommendations.
Inputs, deliverables and rubric
Skills: Web delivery basics · API authentication · Shared responsibility · Evidence-based review
Inputs: Sample architecture diagram · Mock API request and response examples · Redacted log samples
Deliverables: Review findings with severity rationale · Question list for the service owner · Recommendations with verification steps
Rubric: Maps data flows and trust boundaries clearly · Identifies authentication and exposure questions · Respects shared-responsibility boundaries · Does not claim access to real cloud accounts
how a web request travelshow apis connect applicationshow edr detects suspicious activityhow a vulnerability becomes risk
Manufacturing Cyber Risk Assessment
A fictional plant has IT and OT segments, and a finding on a production-support server raises availability and safety questions.
Objective: Assess the risk in business terms and propose approval-gated handling that respects maintenance windows.
Inputs, deliverables and rubric
Skills: IT and OT distinction · Business impact · Safety awareness · Risk communication
Inputs: Mock plant asset list · Sample finding with a CVSS score · Maintenance-window policy extract
Deliverables: Risk assessment narrative · Impact statement for operations · Containment options with approval gates
Rubric: Explains why IT and OT priorities differ · Never recommends an automatic shutdown · Includes human approval and rollback planning · States clearly that the plant is fictional
how a vulnerability becomes riskit vs othow a cyberattack can affect productionwhy you should not automatically shut down othow approval gated containment works
IAM Access Review
A simulated directory export includes role assignments and a few stale accounts for a mock organisation.
Objective: Review access against job need, propose least-privilege adjustments and document the review outcome.
Inputs, deliverables and rubric
Skills: RBAC · Least privilege · Account lifecycle · MFA awareness
Inputs: Mock user and role export · Sample job-role descriptions · Example MFA policy
Deliverables: Access review workbook · Recommended changes with justification · Exceptions and follow-up list
Rubric: Compares access with stated job responsibilities · Flags stale or excessive access without naming real people · Considers MFA and recovery controls · Keeps change proposals subject to approval
what happens when you log inhow password attacks workhow mfa protects an accountwhat is zero trust
Security Dashboard
A training team needs one view that distinguishes raw findings from contextual risk and verified closure.
Objective: Specify a dashboard that shows ownership, priority rationale and verification status without implying false precision.
Inputs, deliverables and rubric
Skills: Risk visualisation · Metric literacy · Ownership tracking · Plain-language reporting
Inputs: Sample risk and incident records · Field definitions from the curriculum · Mock stakeholder questions
Deliverables: Dashboard layout specification · Field and status definitions · Notes on what the numbers do not show
Rubric: Separates generic scores from contextual priority · Makes owner and status visible · Avoids invented or misleading percentages · Explains the limitations of the underlying data
how weprotect detects riskhow weprotect prioritizes riskhow weprotect creates incidentshow weprotect verifies remediation
Threat Model
A sample web application handles login and an API, and the team wants a defensive view of where controls interrupt an attack path.
Objective: Produce a high-level threat model describing assets, trust boundaries, defensive pressure points and mitigations.
Inputs, deliverables and rubric
Skills: Attack-chain literacy · Trust boundaries · Control mapping · Defensive documentation
Inputs: Sample data-flow diagram · Mock asset list · Curriculum attack-stage descriptions
Deliverables: Threat model diagram · Control gap notes · Prioritised defensive recommendations
Rubric: Stays at a defensive level without exploitable detail · Identifies identity and endpoint control points · Links mitigations to specific stages of the scenario · States assumptions and scope clearly
how apis connect applicationshow a cyberattack travelshow phishing leads to account takeoverhow ransomware spreadshow attackers move laterally
Security Policy
A training organisation needs a short, readable policy covering authentication, change approval and incident reporting.
Objective: Draft a policy section that non-technical staff can understand and that aligns with documented controls.
Inputs, deliverables and rubric
Skills: Policy writing · Governance basics · Plain-language communication · Control alignment
Inputs: Mock organisational context · Existing control summaries · Sample incident-reporting workflow
Deliverables: Policy draft section · Glossary of terms · Review and approval checklist
Rubric: Uses clear, non-alarmist language · Defines roles and reporting paths · Does not claim legal or compliance certification · Includes review dates and ownership fields
how mfa protects an accounthow a security alert becomes an incidenthow remediation workshow weprotect creates incidents
GRC Risk Register
A simulated governance exercise needs a register that tracks risks, owners, approvals, evidence and closure.
Objective: Build a risk register that records decisions transparently and supports evidence-based review.
Inputs, deliverables and rubric
Skills: Risk documentation · Ownership assignment · Evidence tracking · Reporting
Inputs: Mock risk statements · Sample approval records · Example verification evidence descriptions
Deliverables: Risk register template with sample rows · Evidence checklist · Status summary for stakeholders
Rubric: Each risk has a named owner and defined status · Evidence is described rather than assumed · Shows approval and verification steps · Does not imply real organisational authority
how containment workshow remediation workswhy verification mattershow weprotect creates incidentshow weprotect verifies remediation