We.ProtectAcademy

Learn to protect what matters

Portfolio projects

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

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

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

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

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

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

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

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

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

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

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

Capstones

SOC Analyst Capstone

A multi-day simulated SOC shift provides sample alerts, logs and handover notes for a training team.

Stages and deliverables
  1. Review the handover note and prioritise the sample alert queue
  2. Enrich each alert with supplied log and asset context
  3. Decide triage outcomes and document the rationale
  4. Escalate a genuine incident with a clear handoff
  5. Verify closure evidence and write a shift summary

Deliverables: Triage log · Investigation notes · Escalation pack · Shift summary

GRC Capstone

A mock governance review asks you to trace a finding from detection to verified closure and explain the decisions recorded along the way.

Stages and deliverables
  1. Map the finding to a clear risk statement
  2. Assign an owner and identify decision points
  3. Collect described evidence for each stage
  4. Review approval and closure criteria
  5. Present a plain-language summary for stakeholders

Deliverables: Risk record · Evidence matrix · Decision log · Stakeholder summary

Cloud Security Capstone

A sample cloud service diagram and redacted logs require a defensive review of web delivery, API authentication and workload signals.

Stages and deliverables
  1. Map request and data flows
  2. Identify trust boundaries and shared-responsibility items
  3. Review sample logs for defensive signals
  4. Draft proportionate recommendations
  5. Define verification checks for any change

Deliverables: Data-flow map · Findings register · Recommendation brief · Verification checklist

IAM Capstone

A simulated identity environment presents login signals, role assignments and an MFA policy to review.

Stages and deliverables
  1. Review authentication patterns in the sample data
  2. Check role assignments against stated job needs
  3. Assess MFA and recovery controls
  4. Propose least-privilege changes
  5. Document approval and verification needs

Deliverables: Access review workbook · MFA assessment · Change proposals · Verification plan

Incident Response Capstone

A tabletop incident unfolds across detection, scoped containment, remediation and verified closure in a training-only environment.

Stages and deliverables
  1. Declare and scope the incident from available evidence
  2. Compare containment options against stated constraints
  3. Plan remediation through the sample change-control process
  4. Capture verification evidence
  5. Write lessons learned from the exercise

Deliverables: Incident timeline · Containment decision record · Remediation plan · Closure and lessons-learned report

Manufacturing Security Capstone

A fictional production line reports a security finding that could affect availability and safety.

Stages and deliverables
  1. Distinguish IT from OT impact
  2. Assess business and safety context
  3. Prepare approval-gated containment options
  4. Schedule action within a maintenance window
  5. Verify both security and process health

Deliverables: Impact assessment · Approval request · Containment and rollback plan · Verification notes

Job simulations

SOC Shift

A full training shift in a simulated SOC with sample alerts, logs and handover notes.

Tasks
  • Review the handover note and open items
  • Prioritise the sample alert queue
  • Enrich selected alerts with log and asset context
  • Escalate a documented incident with a clear owner
  • Record verification evidence and write the shift summary
Day in the life
  • 09:00 — Start of shift: review handover notes and open incidents.
  • 09:15 — Prioritise the overnight alert queue using available context.
  • 10:00 — Enrich the highest-priority alert with sample logs and asset records.
  • 11:00 — Decide triage outcomes and document the reasoning.
  • 13:00 — Hand off an escalated incident with evidence and a named next step.
  • 15:00 — Review responses and check verification evidence.
  • 16:30 — Close verified items and write the end-of-shift summary.

Suspicious Login

A sample login record shows a successful sign-in from an unusual location for a mock user.

Tasks
  • Collect context such as time, device, location and known behaviour
  • Check MFA and recovery events in the sample data
  • Decide whether to escalate, reset or close, with rationale
  • Document findings and the next step

Endpoint Alert

A simulated EDR alert reports unusual process activity on a lab workstation.

Tasks
  • Read the alert details and related process events
  • Separate observed facts from assumptions
  • Recommend a proportionate, documented response
  • State what evidence would confirm or rule out concern

Critical Vulnerability

A sample scan reports a high-scoring finding on a production-support asset in a fictional environment.

Tasks
  • Validate the finding against the mock asset inventory
  • Add exposure, business role and compensating controls
  • Propose a remediation path through sample change control
  • Define verification criteria for closure

Identity Investigation

A mock account has several failed logins followed by a success and a role change.

Tasks
  • Reconstruct the sequence from sample identity logs
  • Check role assignments against the expected job
  • Assess MFA and recovery signals
  • Write a concise investigation note with recommendations

Cloud Misconfiguration

A sample cloud diagram shows an API endpoint with ambiguous caller authentication and broad logging gaps.

Tasks
  • Map the request path and trust boundary
  • List questions for the service owner
  • Identify defensive recommendations without real account access
  • Describe how a change would be verified in a lab

Risk Assessment

A fictional business asks for a risk view of two identical findings on different assets.

Tasks
  • Describe each asset's business role
  • Apply exposure and impact context to both findings
  • Rank the findings with stated assumptions
  • Summarise the reasoning for a non-technical reader

Access Review

A simulated directory export includes stale accounts and broad role membership.

Tasks
  • Compare roles with the supplied job descriptions
  • Flag stale or excessive access
  • Propose least-privilege adjustments and note approval needs
  • Record exceptions and follow-up owners

Incident Escalation

A triage item appears to meet the training escalation threshold and needs a clean handoff.

Tasks
  • Summarise the evidence in a short brief
  • State the reason for escalation
  • Define the receiving owner and the immediate next step
  • Note open questions and evidence gaps

Manufacturing Production Risk

A fictional plant reports a finding on a production-support server with a tight maintenance window.

Tasks
  • Assess IT versus OT impact and safety considerations
  • Prepare containment options with approval gates
  • Plan action within the maintenance window with rollback
  • Define security and process verification checks

Executive Communication

Leadership requests a one-page update on a simulated risk and the proposed response.

Tasks
  • Summarise the situation in plain language
  • Explain priority reasoning without jargon or invented numbers
  • Present options, owners and decision points
  • State limitations and what is not yet known

Client Security Review

A mock client asks for a defensive review of a sample architecture and supporting documents.

Tasks
  • Clarify the scope and the client's concerns
  • Review provided diagrams and redacted evidence
  • Write findings with rationale and verification steps
  • Keep the tone neutral and avoid unsupported claims

Interview practice

Behavioral

  • Tell me about a time you had to learn an unfamiliar topic quickly.

    Use STAR — Situation, Task, Action, Result — and be truthful: a training lab, course project or simulation is a valid example when labelled honestly. Focus on your steps and what changed.

  • Describe a time you disagreed with a teammate about a decision.

    Good answers show listening, evidence-based reasoning and a respectful outcome. STAR keeps the story clear; do not claim paid work experience you do not have.

  • How do you handle a task when you are unsure of the answer?

    Look for honest uncertainty, a plan to verify with trusted sources, and clear communication about limits. A simulated example framed with STAR works well.

SOC

  • How would you decide whether an alert deserves escalation?

    Good answers mention gathering context, comparing with baselines, using evidence and following defined escalation criteria.

  • What do you record when you triage an alert?

    Look for timestamps, sources, observed facts versus assumptions, actions taken, the owner and the next step.

  • How do you avoid alert fatigue in a busy queue?

    Good answers discuss context-led tuning, prioritisation and documenting why items were closed.

Networking

  • Why does HTTPS matter when a browser talks to a server?

    Good answers cover encryption in transit and server identity, and note that it does not by itself prove the user is authorised.

  • What is DNS and why is it useful to understand in security?

    Look for name-to-address mapping and the idea that domain names can appear in phishing or suspicious connections.

  • How does network segmentation help contain an incident?

    Good answers explain boundaries that limit reach between devices so one compromised machine cannot access everything.

Incident Response

  • What is the difference between containment and remediation?

    Containment limits further harm; remediation removes the root cause. Good answers keep the two distinct and mention approval.

  • Why is verification a separate step after a fix?

    Look for fresh evidence compared with the original finding before closure, rather than trusting a completion claim.

  • When might you avoid an automatic shutdown of a system?

    Good answers raise availability, safety and approval gates, especially in production or operational technology contexts.

Cloud

  • What does shared responsibility mean in cloud security?

    Good answers explain that provider and customer each own different controls, and that the boundary depends on the service.

  • Why do API authentication and rate limits matter?

    Look for caller identity, limiting abuse and validating inputs, without going into exploit detail.

  • How would you review a cloud misconfiguration safely in a lab?

    Good answers use sample diagrams and redacted logs, document evidence and never touch real accounts.

IAM

  • How does MFA change the outcome when a password is stolen?

    Good answers explain the second factor and note that recovery controls and phishing-resistant methods also matter.

  • What does least privilege mean in practice?

    Look for granting only the access a role needs, reviewing it regularly and removing stale access.

  • How would you investigate an unusual login pattern?

    Good answers gather context such as time, device, location and known user behaviour before deciding next steps.

Vulnerability Management

  • Why is a high CVSS score not automatically the top priority?

    Good answers add asset role, exposure, compensating controls and business impact.

  • What context would you add to a scanner finding?

    Look for asset inventory, business owner, reachability, patch availability and existing controls.

  • How do you confirm that a vulnerability fix worked?

    Good answers describe a re-scan or fresh telemetry plus documented closure criteria.

GRC

  • What belongs in a risk register?

    Look for a clear risk statement, owner, status, decision or approval record, evidence and closure criteria.

  • Why is evidence preferred over assurance?

    Good answers explain that recorded proof supports review and accountability, while a claim alone does not.

  • How would you explain risk to a non-technical stakeholder?

    Look for plain language, business impact and clear options without jargon or invented numbers.

Manufacturing

  • How do OT priorities differ from IT priorities?

    Good answers put availability and physical safety first and note that a routine reboot can be disruptive.

  • Why should a high risk score not trigger an automatic shutdown?

    Look for human assessment, approval gates, maintenance windows and rollback planning.

  • What would you verify after a production change?

    Good answers check both security status and process health, with evidence recorded.

Security Engineering

  • How does segmentation reduce lateral movement?

    Good answers describe boundaries that limit access between devices and reduce the blast radius.

  • What makes a detection rule useful rather than noisy?

    Look for contextual tuning, testing with sample data and review with SOC analysts.

  • Why document rollback steps before making a change?

    Good answers explain safe recovery if the change causes unforeseen impact, especially in critical environments.

AI mock interviews are a planned extension. Current banks provide practice questions and answer guidance only.

Translate my Academy skills to resume language

Simulated activityHonest resume wordingType
Analysed provided sample log sets in the Log Analysis lab.Analysed sample security logs in a training lab to identify patterns and document findings.Labs
Investigated a sample EDR alert during the SOC Investigation lab.Completed a simulated SOC investigation using sample EDR alerts and logs; produced triage notes and an evidence-based report.Simulations
Ranked mock vulnerabilities using asset and exposure context in a course project.Built a context-led risk ranking for a training scenario, explaining how asset role and exposure affect priority.Projects
Reviewed a mock directory export for excessive access.Performed a simulated IAM access review of sample role assignments and documented least-privilege recommendations.Labs
Created a prioritisation matrix from sample scan results.Produced a vulnerability prioritisation report in a training project, distinguishing generic scores from business context.Projects
Reviewed a sample cloud architecture diagram and redacted logs.Conducted a cloud security review exercise using a sample architecture and redacted logs; documented questions and recommendations.Projects
Documented a tabletop incident from detection to verified closure.Documented a simulated incident timeline, containment options and verification criteria as part of security training.Training
Traced a finding through detection, incident creation and verification in guided lessons.Studied a risk-to-verification workflow in guided training materials and summarised its ownership and evidence steps.Training
Assessed fictional manufacturing risk with approval-gated containment.Completed a manufacturing security simulation covering IT and OT differences, approval gates and safety-aware recommendations.Simulations
Drafted a short security policy section for a training scenario.Drafted a plain-language security policy section for a training project, including roles and reporting paths.Projects

Hands-on labs

Certification roadmap

The We.Protect Academy Certificate of Completion is evidence that a learner completed the academy's coursework. It is not an accredited external certification, is not issued by any vendor or certifying body, and does not guarantee employment, an interview, or passing any external examination. Always confirm the current requirements of any certification or role with the relevant official organisation.