Network Insight · Interactive Learning Workspace

Data Centre Security Learning Workspace

Explore how data centre security works in practice. Map trust boundaries, control east–west and north–south traffic, investigate suspicious activity, apply Zero Trust principles, and practise containing and recovering from security incidents through interactive network scenarios.

Security Architecture Traffic & Policy Threat Investigation Zero Trust
05 Learning stages 12 Interactive widgets
Learning mode Interactive educational simulations. Security events, policy decisions and incident outcomes are illustrative and do not represent live monitoring of your infrastructure.

Learning Control Bar

Navigate five stages and track all 15 security activities.

0 of 5 stages 0%
Selected stage: 01 · Security Architecture

Network Insight · Security Learning Progress

Unified Security Learning Dashboard

Track your progress across five security stages and fifteen interactive activities.

0/15 Activities
0/5 Stages
0% Complete
Security learning pathway 0 of 15 activities completed
STAGE 01 0/3
Understand Security Architecture
Explore Stage 01 →
STAGE 02 0/3
Control Traffic and Access
Explore Stage 02 →
STAGE 03 0/3
Detect and Investigate Threats
Explore Stage 03 →
STAGE 04 0/3
Apply Zero Trust
Explore Stage 04 →
STAGE 05 0/3
Respond, Recover and Validate
Explore Stage 05 →
Ready · Begin with security architecture
Start Stage 01 →

Your learning pathway

Explore the Security Workspace

Follow five connected stages, from understanding security boundaries to investigating threats and validating incident recovery. Select a stage to explore its interactive security engineering activities. Your learning progress is saved automatically.

05 Stages
Security Learning Progress 0 of 15 activities · 0%

Stage 1 - Data Centre Security Architecture and Trust Boundaries

01 Learning Stage One Foundation · Architecture · Trust

Understand Security Architecture

Before investigating a threat or writing a security rule, understand what you are protecting, where trust begins and ends, and how systems are separated. A data centre security design is more than a collection of firewalls: it is a set of boundaries, controls and access decisions that work together to limit exposure and contain compromise.

Start by mapping the environment and identifying the purpose of each security zone. Consider how management systems, application workloads, shared services and external connections should interact—and which paths should remain restricted.

  • Security zones: group systems according to their role, sensitivity and exposure.
  • Trust boundaries: identify where access must be evaluated rather than automatically trusted.
  • Control placement: understand where firewalls, segmentation controls and management safeguards can enforce policy.
  • Blast-radius reduction: design boundaries that limit how far a compromised system can reach.
Learning pathway 01 · Architecture 02 · Traffic & Access 03 · Investigation 04 · Zero Trust 05 · Recovery

Practical focus: establish the security context first, then use the interactive exercises below to investigate architecture and trust decisions. Examples in this workspace are educational simulations.

Network Insight · Stage 1 · Interactive Architecture Lab

Security Architecture Explorer

Explore the security architecture of a modern data centre. Select security zones, inspect trust boundaries and evaluate how traffic is controlled between application workloads, shared infrastructure, management systems and protected data.

01 · Select a security zone 02 · Explore security boundaries 03 · Test traffic policies
Interactive architecture views
Data Centre Security Topology Select a zone to investigate
EXTERNAL TRUST BOUNDARY INTERNAL SECURITY BOUNDARIES External Access Internet and partner networks Application Zone Application workloads Service tier Shared Services DNS · Identity Infrastructure dependencies Management Zone Privileged administration Jump hosts Protected Data Databases Sensitive services SECURITY CONTROLS Firewall · ACL Identity · Logging
Security zone Infrastructure Protected data Trust boundary

Network Insight · Interactive Security Architecture Explorer. This is an educational model. Actual traffic decisions depend on firewall rules, workload identity, segmentation policy and deployment context.
Network Insight · Stage 1 · Interactive Widget 2

Trust Zones and Security Boundaries

Explore how security boundaries separate application workloads, shared infrastructure, privileged management systems and protected data. Select a zone or boundary to investigate the required controls.

01 · Select a boundary 02 · Inspect security controls 03 · Evaluate a connection
Interactive Trust Boundary Topology Selected · Boundary B1
LOWER TRUST RESTRICTED ACCESS 01 External Access Users Internet Partners UNTRUSTED 02 Application Tier Web API Services CONTROLLED 03 Shared Services DNS Identity Logging LIMITED ACCESS 04 Management Plane Admin access Jump hosts Device control PRIVILEGED 05 Data Services Databases Sensitive records Storage systems RESTRICTED B1 B2 B3 B4 A trust boundary is a policy enforcement point, not simply a VLAN.
Select a zone or a red boundary. On smaller screens, scroll horizontally to explore the complete topology.
Selected Security Boundary

B1 · External to Application

Security Objective

✓
!

Test a Cross-Zone Connection

Choose a source and destination to evaluate the illustrative security policy.

Network Insight · Educational Security Architecture Model. This interactive simulation demonstrates illustrative security boundaries and policy decisions. It does not inspect live firewall configurations, production traffic or real identities.
Network Insight · Stage 1 · Interactive Widget 3

Security Control Mapping

Translate security objectives into practical enforcement controls. Select an objective, explore the security architecture, review the recommended controls and complete an engineering design checklist.

01 · Choose objective 02 · Explore control mapping 03 · Review controls 04 · Validate design
Security Control Architecture Interactive Mapping
Application Workload East–west traffic
Security Enforcement Firewall · ACL · Identity
Protected Service Approved destination
Illustrative flow: security policy is evaluated before access to the protected service is permitted.

Segment workloads

4 relevant control groups

3 · Engineering Design Review

Validate the controls for the selected objective.

0 of 4 checked
Network Insight · Interactive Security Control Mapping. This educational model illustrates control selection and design review. It does not validate production firewall configurations, identities or live security events. Checklist completion is self-reported and is retained only while this widget remains loaded.
Stage 01 · Security Learning Progress

Understand Security Architecture

Complete three interactive architecture activities to understand security zones, trust boundaries and enforcement controls.

0/3 ACTIVITIES
COMPLETE
Ready · Complete the activities above
Continue to Stage 02 →

Stage 2 - Data Centre Traffic Security and Access Control

Data Centre Security · Stage 2 of 5

Traffic and Access Control

Security zones define where trust changes. Access-control policies determine what can cross those boundaries. In this stage, explore traffic direction, permitted service flows, enforcement points and the difference between network reachability and genuine authorization.

Core principle: connectivity is not authorization

A route between two systems does not mean the connection should be allowed. Each flow needs a valid purpose, a defined policy and suitable enforcement and monitoring.

What you will investigate

Traffic direction

Distinguish north–south traffic entering or leaving the data centre from east–west traffic moving between internal workloads and services.

Policy decisions

Decide which source, destination, protocol, port and identity combinations should be permitted, restricted or denied.

Enforcement points

Understand the roles of firewalls, network ACLs, workload controls and identity-aware policies in enforcing access decisions.

01 Trace a traffic flow 02 Evaluate an access rule 03 Identify over-permissive access 04 Validate enforcement
Stage objective: move from understanding the security architecture to evaluating the traffic policies that protect it.
Network Insight · Stage 2 · Interactive Widget 4

North–South and East–West Traffic Flow Explorer

Trace traffic through a data centre security architecture. Compare external and internal flows, investigate policy enforcement points and follow individual packet paths.

Interactive topology Animated traffic tracing 6 security scenarios Policy inspection

Interactive Security Topology

Choose a scenario or select a device to inspect it.

North–South
EXTERNAL / NORTH Internet users and external services EDGE AND POLICY ENFORCEMENT Firewall, ingress and egress controls APPLICATION WORKLOADS Internal service-to-service traffic DATA AND SHARED SERVICES Sensitive data and identity dependencies External client Internet / external API Edge firewall Policy enforcement Load balancer Application entry Application A Service workload Application B Internal dependency Database Sensitive data Identity service Internal dependency INGRESS · EXTERNAL CLIENT → APPLICATION A
Selected flow Sensitive / review Other connections

Packet Path Walkthrough

Select Play to follow the selected flow.

Explore Security Traffic Scenarios

Switch scenarios to update the topology, packet trace and engineering guidance.

Security principle · Direction does not establish trust

North–south traffic is not automatically safe because it crosses an edge firewall. East–west traffic is not automatically trusted because it remains inside the data centre. Both require appropriate identity, segmentation, policy enforcement and monitoring.

Network Insight · Educational traffic model · Not a live packet capture or production policy validator. Animated paths represent illustrative requests rather than actual network forwarding behaviour.
Network Insight · Stage 2 · Interactive Widget 5

Access Policy Decision Lab

Build a traffic request, evaluate it against a simplified security rule set and investigate why access is allowed, denied or flagged for additional review.

01 · Build request 02 · Evaluate policy 03 · Trace decision 04 · Inspect rules

1 · Build a Traffic Request

Select the source, destination, service and identity context.

Selected Traffic Path READY TO EVALUATE
Source External client
Policy Engine Evaluate
Destination Application A
Select Evaluate Traffic to inspect the policy decision.

Interactive Policy Decision Trace

Follow the three stages of a security policy evaluation.

01 · Request
02 · Rule Match
03 · Decision

Evaluate a request to activate the decision walkthrough.

2 · Policy Evaluation

Inspect the matched rule, enforcement point and decision.

Simulated Policy Decision
READY

Select Evaluate Traffic to inspect this request.

Matched Rule Not evaluated
Traffic Direction North–South
Enforcement Point Not evaluated
Evaluation Count 0

Engineering Explanation

Rules are evaluated in priority order. The first matching rule determines the simulated decision. If no explicit rule matches, default deny applies.

3 · Investigation Scenarios

Load an example request to investigate a legitimate or suspicious traffic flow.

4 · Illustrative Security Rule Table

Rules are evaluated from top to bottom. The first matching rule determines the simulated outcome.

Priority Source Destination Service Identity Action
R01Unknown workloadAny AnyAny DENY
R02External clientApplication A HTTPSAny ALLOW
R03Application ADatabase SQLVerified ALLOW
R04Application AApplication B HTTPSVerified ALLOW
R05Application BIdentity service HTTPSVerified ALLOW
R06Management workstation Management planeSSH Privileged REVIEW
R07AnyDatabase AnyAny DENY
R08AnyManagement plane AnyAny DENY
R09AnyAny AnyAny DEFAULT DENY
Security Principle · An ALLOW decision does not guarantee connectivity

Routing, application authentication and other controls may still reject a permitted connection. REVIEW represents an illustrative approval or investigation requirement, not a standard firewall forwarding action.

Network Insight · Data Centre Security Learning Workspace · Educational policy simulator. Not connected to production security devices.
Network Insight · Stage 2 · Interactive Widget 6 · Visual Upgrade V2

Firewall Rule and Microsegmentation Explorer

Compare perimeter firewalls, network segmentation and workload-level microsegmentation. Investigate how enforcement boundaries change permitted traffic and lateral movement exposure.

3 enforcement models 4 traffic scenarios Interactive topology Packet tracing

Interactive Security Topology

Select a scenario, trace traffic or inspect a workload.

Perimeter Model
EXTERNAL ACCESS Untrusted network PERIMETER ENFORCEMENT North–south security controls APPLICATION NETWORK East–west workload traffic DATA SERVICES Sensitive information External Client Internet access Edge Firewall Ingress policy Application A Service workload Application B Service workload Database Sensitive data EXTERNAL CLIENT → APPLICATION A · HTTPS
Permitted Denied Review required

Packet Path Investigation

Play the trace to follow the selected connection.

Explore Security Scenarios

Choose a traffic flow and change the enforcement model to compare its security decision.

Security Exposure Comparison

Illustrative comparison of the selected model, not measured production security performance.

Internal Policy Granularity Low

Lateral Movement Exposure Higher

Enforcement Scope Perimeter

Engineering Principle · Microsegmentation Is Not Automatic Security

Effective segmentation requires accurate workload identity, correct policy definitions, enforcement coverage and ongoing monitoring. Traditional firewalls can also enforce internal segmentation when deployed at the appropriate boundaries.

Network Insight · Data Centre Security Learning Workspace · Illustrative simulation
Stage 02 · Security Learning Progress

Control Traffic and Access

Complete three interactive security activities to trace network traffic, evaluate access decisions and investigate segmentation.

0/3 ACTIVITIES
COMPLETE
Ready · Complete the activities above
Continue to Stage 03 →

Stage 3 -Threat Detection and Security Incident Investigation

Network Insight · Security Learning Path · Stage 03

Threat Detection and Investigation

Security architecture and access controls establish how traffic should behave. Threat detection reveals when actual activity deviates from that expectation. Learn to interpret telemetry, correlate suspicious events, and investigate potential threats before deciding how to respond.

Modern data centres generate security signals from firewalls, switches, workload agents, identity systems, application logs and network telemetry. An isolated event rarely tells the complete story. Effective investigation requires correlating evidence across these sources, understanding the expected communication patterns, and distinguishing genuine security incidents from routine operational activity.

What you will investigate

01
Security Telemetry and Visibility

Explore flow records, firewall logs, authentication events and workload activity. Understand which observations help reconstruct a suspicious network connection.

02
Threat Indicators and Alerts

Recognise unusual access attempts, unexpected lateral connections, repeated authentication failures and traffic anomalies that warrant further analysis.

03
Investigation and Evidence Correlation

Combine network and security observations into a timeline. Identify the affected workloads, evaluate possible explanations and determine the next investigative step.

From telemetry to investigation

Follow a structured sequence rather than treating every alert as a confirmed compromise.

Observe Collect logs and network events
Detect Identify suspicious patterns
Correlate Connect related evidence
Investigate Validate scope and cause
Escalate Determine response priority
Engineering principle: an alert is evidence, not a conclusion

A blocked connection, unusual traffic spike or authentication failure may be suspicious, but each requires context. Investigation should establish what happened, which assets were involved and whether the available evidence supports an actual security incident.

Network Insight · Stage 3 · Interactive Widget 7 · Visual Upgrade V2

Security Telemetry and Event Correlation Explorer

Investigate suspicious data centre activity using network flows, firewall events, workload telemetry and identity logs. Correlate multiple signals to understand potential threats.

4 investigation scenarios 4 telemetry sources Event correlation Investigation playback

Interactive Investigation Topology

Select a device or play the investigation sequence.

Lateral Movement
EXTERNAL NETWORK Internet and remote systems EDGE SECURITY Firewall and inspection boundary APPLICATION NETWORK Workload activity and internal traffic DATA AND IDENTITY SERVICES Protected dependencies External System Remote endpoint Edge Firewall Security telemetry Application A Workload telemetry Application B Workload telemetry Database Data access logs Identity Service Authentication logs

Investigation Playback

Follow the sequence of synthetic security events.

Telemetry Event Timeline

Filter sources and select events to inspect the evidence.

5 events

Telemetry Sources

Investigation Assessment

Investigation Focus
Visible Evidence
Priority
Evidence Coverage
Recommended Next Step

Security Event Correlation

Correlate evidence from different monitoring systems. Filtering events changes the visible evidence, not the underlying incident.

Visible Telemetry Sources 0 / 4

Distinct sources contributing visible events.

High-Severity Events 0

High-severity signals in the filtered evidence.

Correlation Insight Awaiting evidence

Investigation Principle · Evidence Is Not Proof

A telemetry source provides only a partial view. Missing events in a filtered timeline do not mean activity did not occur. Verify log coverage, timestamp accuracy, enforcement outcomes and operational context before concluding that an incident has taken place.

Network Insight · Data Centre Security Learning Workspace · Synthetic investigation data
Network Insight · Stage 3 · Interactive Widget 8 · Visual Upgrade V2

Threat Indicators and Alert Triage Lab

Work through a simulated security operations alert queue. Inspect evidence, assess priority and confidence, and decide whether to escalate, investigate further or close each alert.

6 security cases Interactive investigation map Evidence-based decisions Triage progress tracking
Total Alerts 6

Simulated investigation cases

Open Alerts 6

Awaiting analyst assessment

Reviewed 0

Completed triage decisions

Escalated 0

Referred for response

Security Operations Triage Progress 0 of 6 reviewed

Security Alert Queue

Select an alert to inspect the available evidence.

Security Alert Investigation

Correlate evidence before choosing a triage action.

Alert Source
Initial Severity
Affected Asset
Security Investigation Map

Highlighted components represent the selected case.

Remote Network Security Firewall Application Database Identity / Admin

Available Investigation Evidence

Review all three evidence observations before recording your assessment.

    Analyst Assessment

    Severity reflects potential impact; confidence reflects how strongly the available evidence supports your interpretation.

    Awaiting Assessment

    Review the evidence and select a triage action.

    Security Operations Decision Summary

    Track your triage decisions across the six synthetic cases. Decisions can be revised by reopening an alert.

    Escalated Cases 0
    Further Investigation 0
    Closed as Expected 0
    Security Principle · Alert Severity Is Not Proof

    An alert can have high potential severity but low evidence confidence. Review the asset, observed behaviour, control outcomes and operational context before escalating or closing. These cases use synthetic data and illustrative triage guidance.

    Network Insight · Data Centre Security Learning Workspace · Synthetic alert data
    Network Insight · Stage 3 · Interactive Widget 9 · Visual Upgrade V2

    Security Incident Investigation Timeline

    Reconstruct a potential security incident from correlated telemetry. Follow events in sequence, inspect affected network components and determine what the evidence reveals.

    3 investigation scenarios 18 synthetic events Animated evidence playback Interactive topology
    Investigation Case
    Events in Sequence
    Current Investigation Phase

    Interactive Incident Evidence Map

    Select a network component to inspect its role.

    Investigation
    EXTERNAL NETWORK Remote systems EDGE SECURITY Firewall and inspection APPLICATION NETWORK Internal workload activity PROTECTED SERVICES Data and identity External System Remote endpoint Edge Firewall Security enforcement Application A Workload Application B Workload Database Data access Identity Service Authentication

    Device Inspection

    Select a component to understand its investigation role.

    Correlated Event Timeline

    Select an event or play the recorded sequence.

    6 events

    Telemetry Source
    Investigation Phase

    Incident Reconstruction Dashboard

    Review the accumulated evidence through the selected point in the investigation.

    Evidence Examined

    Visible events reached in the investigation sequence.

    Distinct Telemetry Sources

    Different sources represented in examined evidence.

    Current Assessment

    Interpretation based on available observations.

    Investigation Finding

    Engineering Principle · Correlation Is Not Causation

    A correlated timeline establishes the order of recorded observations, not necessarily the complete sequence of real-world actions. Clock differences, missing logs, collection delays and limited sensor coverage can affect reconstruction. Investigators should distinguish observed facts from hypotheses.

    Network Insight · Data Centre Security Learning Workspace · Synthetic incident evidence
    Stage 03 · Security Learning Progress

    Detect and Investigate Threats

    Complete three investigation activities to correlate security telemetry, triage suspicious alerts and reconstruct incident timelines.

    0/3 ACTIVITIES
    COMPLETE
    Ready · Complete the activities above
    Continue to Stage 04 →

    Stage 4 - Zero Trust Architecture and Policy Enforcement

    Network Insight · Security Learning Path · Stage 04

    Zero Trust and Policy Enforcement

    Network location alone should not determine whether access is trusted. Explore how Zero Trust principles use verified identities, workload context, least-privilege policies and ongoing evaluation to control communication between users, applications and protected services.

    Traditional network security often relied on trusted internal networks and protected external boundaries. Zero Trust changes the decision model: access requests are evaluated using identity, device or workload posture, resource sensitivity and policy context. Authorisation is explicitly granted for the required operation rather than assumed from network placement. Enforcement can occur through identity-aware gateways, workload controls, application proxies and other policy enforcement points.

    What you will explore

    01
    Identity-Aware Access Decisions

    Examine how verified identities, workload roles, device posture and requested resources influence access decisions. Compare approved, unverified and high-risk requests.

    02
    Continuous Policy Evaluation

    Explore how changing identity, posture, risk or session context can trigger policy re-evaluation. Understand why a previously authorised session may require additional verification or termination.

    03
    Zero Trust Enforcement Scenarios

    Investigate access across application, database and management boundaries. Compare enforcement decisions and examine how narrowly scoped permissions reduce unnecessary exposure.

    How a Zero Trust access decision works

    A simplified policy decision sequence, from access request to ongoing enforcement.

    Request Identify subject and resource
    Verify Check identity and context
    Evaluate Apply access policy
    Enforce Permit or deny the request
    Reassess Monitor changing context
    Engineering principle: never trust implicitly

    Zero Trust does not mean denying every connection. It means granting the minimum necessary access after evaluating relevant evidence, enforcing that decision at an appropriate control point and reconsidering authorisation when conditions change. Successful authentication alone does not guarantee unrestricted access.

    Data Centre Security · Stage 4 · Interactive Widget 10

    Identity-Aware Access Decision Lab

    Evaluate access requests using identity, workload posture, resource sensitivity and access context. Change the conditions, apply the policy and observe how a Zero Trust decision is enforced.

    6 policy scenarios Identity · Role · Posture · Risk Guided evaluation trace ALLOW / DENY / VERIFY

    Configure access request

    Change the attributes used by the policy decision engine.

    Authentication assurance associated with the requesting subject.
    The role must be authorised for the requested resource.
    A simplified assessment of endpoint or workload security state.
    Different resources require different levels of authorisation.
    Illustrative risk signal derived from request context.
    Represents an additional identity verification requirement.

    Policy decision and enforcement path

    Observe the request, policy evaluation and protected resource.

    01 · Request 02 · Policy checks 03 · Enforcement
    Zero Trust access decision flow A requesting identity passes through policy evaluation and an enforcement point before accessing a protected resource. ZERO TRUST ACCESS CONTROL Requesting subject Identity and posture Access request Policy evaluation Role · Resource · Risk Decision and enforcement Protected resource Application API Controlled access POLICY DECISION POINT Access is evaluated before enforcement. ALLOW Illustrative policy model · Not a live enforcement system
    The policy engine makes an authorisation decision; an enforcement point must apply that decision to the actual connection.
    Access decision ALLOW
    ALLOW
    Identity assurance
    Role authorisation
    Security posture
    Risk assessment
    Guided decision trace Step 1 of 3

    Inspect the access request attributes before evaluating the policy.

    Policy evaluation explanation

    Policy model used in this lab

    The simplified engine applies explicit authorisation rules before allowing a request.

    Identity and role

    Unknown roles are denied. Each protected resource accepts only designated identity roles.

    Posture and risk

    Noncompliant workloads and high-risk contexts are denied. Unknown posture and elevated risk require additional checks.

    Least privilege

    Database access is limited to the database service role. Management access requires an administrator role and completed step-up verification.

    Engineering principle: This is a simplified policy decision model, not a live identity provider or enforcement gateway. A VERIFY result means access must not proceed until the required checks are satisfied and the request is evaluated again.
    Network Insight · Stage 4 · Interactive Widget 11 · Visual Upgrade V2

    Continuous Trust Evaluation Simulator

    Establish an authorised application session, introduce changes in identity, workload posture or access risk, and observe how continuous trust evaluation changes the enforcement decision.

    6 security events Dynamic session enforcement Interactive topology Event reconstruction
    Application session · APP-A → Protected API Initial conditions: verified identity, compliant workload, normal risk
    NOT ESTABLISHED
    Session state Not established
    Policy evaluations 0
    Recorded events 0
    Current action Establish session

    Interactive Session Enforcement Topology

    Select a component to inspect its security role.

    APP-A → API
    CONTINUOUS ACCESS ENFORCEMENT Application A Workload identity Session requester Policy Enforcement Continuous evaluation Session control Protected API Application resource Restricted access SESSION NOT ESTABLISHED Illustrative session policy · Not live network enforcement

    Green indicates authorised connectivity. Amber indicates a suspended session requiring validation. Red indicates termination.

    Component Inspector

    Select Application A, Policy Enforcement or Protected API.

    Current Trust Assessment

    Identity Verified
    Workload posture Compliant
    Access risk Normal
    Session decision Not established
    Enforcement Explanation

    Establish the session to begin continuous trust evaluation.

    Introduce a Security Event

    Apply a condition change after establishing the session.

    6 event types

    Guided Session Walkthrough

    Establish an authorised session before introducing a security event.

    01 · Establish 02 · Re-evaluate 03 · Enforce

    Session Event Timeline

    Follow the recorded changes in trust conditions, policy decisions and session enforcement.

    Zero Trust Engineering Principle

    A successful initial access decision does not guarantee continued authorisation. Deployed Zero Trust systems need appropriate monitoring, re-evaluation triggers and enforcement mechanisms. Some changes require renewed verification, while others justify immediate session termination.

    Network Insight · Data Centre Security Learning Workspace · Simulated session policy Stage 4 · Widget 11

    Data Centre Security · Stage 4 · Interactive Widget 12 · V2

    Zero Trust Enforcement Explorer

    Explore how perimeter controls, network segmentation and Zero Trust enforcement affect access to applications, databases and management services. Select an access scenario, trace the request and compare the resulting policy decisions across all three architectures.

    3 enforcement models 6 access scenarios 18 policy outcomes Interactive topology
    Selected architecture Zero Trust
    Access request Application → Database
    Policy outcome ALLOW
    Evaluation stage Decision ready

    Interactive Security Enforcement Topology

    Select a network component to inspect its security role.

    Topology View
    EXTERNAL ACCESS SECURITY ENFORCEMENT APPLICATION SERVICES PROTECTED RESOURCES External identity Remote access Policy enforcement Access control Application A Service workload Application B Service workload Database Protected data Management Administrative plane

    Zero Trust evaluates identity, role, resource and request context before granting access.

    Component Inspector

    Select a component in the topology to inspect its role in the security architecture.

    Select Access Scenario

    Compare identical requests across enforcement models.

    6 Scenarios
    Enforcement Decision ALLOW
    ALLOW
    Enforcement model Zero Trust
    Policy scope Application → Database
    Identity evaluation Verified workload
    Resource protection Identity and resource
    Engineering Interpretation

    Guided Policy Evaluation

    Follow how the selected access request is interpreted, evaluated and enforced.

    Step 01 Identify Request

    Step 02 Evaluate Policy

    Step 03 Enforce Decision

    Compare Security Enforcement Models

    Each architecture applies a different level of access control and resource isolation.

    Model 01 Perimeter-only

    External boundary protection with broad internal reachability.

    Model 02 Network segmentation

    Network-layer policies restrict selected cross-zone connections.

    Model 03 Zero Trust

    Explicit, identity-aware and resource-specific authorisation.

    Access scenario Perimeter-only Segmentation Zero Trust
    Engineering Principle

    Zero Trust is an architectural approach, not a single product. Effective enforcement depends on reliable identity, policy decisions, appropriate enforcement points, workload visibility and continuous reassessment. These examples compare simplified policies rather than guaranteeing that one architecture prevents every attack.

    Network Insight · Data Centre Security Learning Workspace · Illustrative policy comparison Stage 4 · Widget 12
    Stage 04 · Security Learning Progress

    Apply Zero Trust

    Complete three interactive Zero Trust activities to evaluate identity-aware access, investigate changing trust conditions and compare security enforcement architectures.

    0/3 ACTIVITIES
    COMPLETE
    Ready · Complete the activities above
    Continue to Stage 05 →

    Stage 5 - Incident Response, Service Recovery and Resilience

    Network Insight · Security Learning Path · Stage 05

    Incident Response and Recovery

    Security controls reduce risk, but incidents can still occur. Learn how data centre engineering teams investigate confirmed security events, contain affected systems, protect critical services and restore normal operations through a controlled, evidence-driven recovery process.

    Effective incident response requires coordination between security operations, network engineering, infrastructure teams and application owners. Containment actions must reduce the threat without creating unnecessary service disruption. Recovery requires more than restoring connectivity: teams must validate system integrity, confirm that the cause of the incident has been addressed and monitor for signs of recurrence. This stage explores the operational decisions involved in balancing security, availability and recovery confidence.

    What you will explore

    01
    Incident Containment and Isolation

    Investigate how security teams isolate compromised workloads, restrict suspicious traffic and protect critical network segments. Compare containment strategies and evaluate their impact on application availability.

    02
    Service Recovery and Validation

    Explore a controlled recovery sequence involving system integrity checks, configuration restoration, connectivity validation and application health verification before returning services to production.

    03
    Operational Resilience and Lessons Learned

    Examine how incident evidence, recovery metrics and post-incident reviews improve security operations. Identify opportunities to strengthen detection, reduce exposure and improve recovery readiness.

    From security incident to validated recovery

    A simplified operational response lifecycle. In practice, investigation, containment and recovery activities may overlap.

    Identify Confirm incident and scope
    Contain Limit threat propagation
    Eradicate Remove the cause and persistence
    Recover Restore trusted services
    Validate Verify security and service health
    Improve Apply lessons learned
    Security objective

    Stop or limit malicious activity, prevent further compromise and establish confidence that affected systems are safe to return to service.

    Operational objective

    Minimise unnecessary disruption, prioritise critical services and restore business functionality through a documented, controlled process.

    Engineering principle: recovery must be verified

    Restored network connectivity does not prove that an incident has been resolved. Recovery should include evidence-based checks of system integrity, security controls, application functionality and continued monitoring. Containment and remediation decisions should also consider forensic evidence preservation and operational dependencies.

    Data Centre Security · Stage 5 · Interactive Widget 13 · V2

    Incident Containment and Isolation Lab

    Investigate a compromised data centre workload. Apply emergency controls, inspect remaining attack paths and balance threat containment against application availability. Test targeted restrictions before choosing full isolation.

    3 incident scenarios5 containment controlsLive threat pathsAvailability trade-offs

    Interactive Data Centre Security Topology

    Red = exposed threat · Amber = blocked route · Green = protected destination. Select any component to inspect it.

    EXTERNAL CONNECTIVITYAPPLICATION WORKLOADSPROTECTED SERVICES External ClientIngress Application AWorkload Application BWorkload DatabaseProtected data ManagementAdministrative plane

    Select a containment action to evaluate its effect on the incident.

    Component Inspector

    Select a topology component to inspect its security role.

    Containment Controls

    Toggle controls to build a response strategy. Changes update the topology and metrics immediately.

    Threat paths contained0 / 2Scenario-specific exposure paths
    Service availability100%Illustrative service impact score
    Containment statusExposedCurrent response effectiveness
    Controls enabled0 / 5Active emergency restrictions

    Engineering Assessment

    The incident is active. Apply containment controls and assess the remaining exposure.

    Incident Response Timeline

    Review the sequence of response decisions in this simulation.

    Response Engineering Principle

    Containment should consider evidence preservation, application dependencies, emergency change approval and the ability to recover safely. The availability percentages are illustrative scores, not measured production service levels. Blocking modelled paths does not prove eradication of an attacker.

    Network Insight · Stage 5 · Interactive Widget 14 · Visual Upgrade V2

    Service Recovery and Validation Simulator

    Restore an affected data centre service through a controlled recovery process. Preserve evidence, remove the cause, restore trusted state, validate connectivity and service health, and authorise production access only after all six recovery gates have passed.

    3 recovery scenarios 6 validation gates 12 required checks Interactive recovery topology
    Incident scenario Compromised Application
    Recovery stage 1 of 6
    Production access Restricted
    Validation progress 0 / 6

    Interactive Service Recovery Topology

    Select a component to inspect its role in recovery.

    Recovery Network
    SECURITY AND NETWORK CONTROL APPLICATION AND DATA SERVICES Security Enforcement Policy and access control Application Service Production workload Network Fabric Reachability and policy Database Service Protected data

    The affected workload remains isolated until the recovery gates are completed.

    Component Inspector

    Select Security Enforcement, Application Service, Network Fabric or Database Service.

    Recovery Validation Workflow

    Complete the six stages in order. Every stage requires two checks.

    6 Gates

    Stage 1 · Preserve evidence

    Complete the required checks to continue.
    Recovery progress 0 / 6 Validation gates completed
    Security confidence Low Illustrative recovery assessment
    Production readiness Not ready Access remains restricted until approval

    Engineering Recovery Assessment

    Recovery has not started. The affected system must remain isolated until evidence preservation and security validation are completed.

    Recovery Event Timeline

    Follow the validation gates and response decisions.

    Recovery Engineering Principle

    Recovery is not complete merely because an application responds. A controlled return to production also requires eradication verification, trusted restoration, connectivity and policy testing, service integrity checks, authorised approval and enhanced monitoring. Checking a box in this lab represents simulated evidence, not a real infrastructure test.

    Network Insight · Data Centre Security Learning Workspace · Stage 5 · Widget 14 · Illustrative recovery workflow
    Network Insight · Stage 5 · Interactive Widget 15 · V2

    Security Resilience and Post-Incident Review

    Review incident findings, identify control weaknesses and build a prioritised improvement programme. Explore how proposed corrective actions change the modelled resilience of the data centre security environment and address incident-specific gaps.

    3 incident scenarios 6 security controls 6 corrective actions Live resilience assessment
    Incident focus Lateral Movement
    Baseline score 42 / 100
    Actions selected 0 of 6
    Priority gaps covered 0 of 3

    Security Resilience Assessment

    Illustrative maturity score and control-by-control improvement.

    42 Resilience score
    Developing resilience

    The incident exposed weaknesses in network segmentation, security visibility and operational response.

    Before improvements 42
    After proposed improvements 42

    Interactive Security Control Map

    Amber identifies incident-priority gaps. Green identifies selected improvements. Select a control to inspect it.

    SECURITY RESILIENCE Post-Incident Review Segmentation East–West Policy Identity Controls Privilege and Verification Threat Detection Telemetry and Alerts Incident Response Containment Playbooks Recovery Readiness Restore and Validate Security Validation Continuous Assurance
    Control Inspector

    Select a security control to inspect its improvement objective.

    Corrective Improvement Actions

    Select actions to build a post-incident improvement programme. Priorities and effort estimates are illustrative.

    Controls improved 0 / 6 Selected corrective actions
    Modelled improvement +0 Resilience score points
    Improvement status Gaps remain Post-incident review outcome

    Post-Incident Engineering Assessment

    Review the incident findings and select corrective actions to address the identified control weaknesses.

    Prioritised Improvement Roadmap

    Review Status · Awaiting Assessment

    Select corrective actions and generate a post-incident review. The resulting roadmap should be assigned owners, milestones and effectiveness validation before closure.

    Network Insight · Data Centre Security Learning Workspace · Stage 5 · Widget 15 · Illustrative post-incident maturity model. Scores are educational comparisons, not a formal security assessment.
    Stage 05 · Final Security Learning Stage

    Respond, Recover and Validate

    Complete three interactive incident-response activities to contain security threats, restore trusted services and improve operational resilience.

    0/3 ACTIVITIES
    COMPLETE
    ✓ Stage 05 Complete

    You have marked all three incident-response activities as complete. Review your overall progress in the Unified Security Learning Dashboard.

    Ready · Complete the activities above
    Return to Learning Dashboard →

    Network Insight · Security Learning Workspace

    Learning Progress and Workspace Completion

    Track your progress through five security learning stages and 15 interactive activities. Review your completed labs, revisit unfinished investigations and confirm your progress through the Data Centre Security Learning Workspace.

    Activities completed 0 / 15 Interactive security activities
    Stages completed 0 / 5 Five connected learning stages
    Overall completion 0% Saved in this browser
    Overall Learning Progress 0 of 15 complete

    Five-Stage Learning Checklist

    Security Learning Pathway In Progress

    Complete the activities across all five stages to finish your learning pathway. Your progress is synchronised with the stage trackers and dashboard.

    Completion is self-reported and stored locally in this browser. It is a learning progress indicator, not a certification or independent assessment of security competence.
    Return to Dashboard →

    ☕
    Support Network Insight
    Help support the development of interactive networking labs, BGP simulations, and educational content.
    Support the Project
    From theory to interactive practice

    Don't Just Read the Network. Explore It.

    You've explored data centre architecture, routing and resilient design. Now take the next step. Use the interactive simulator to investigate how network components and paths work together. Move beyond diagrams and start exploring network behaviour.

    Network topology Traffic paths Routing decisions Failure scenarios
    LAUNCH THE BGP CORE SIMULATOR Opens in a new browser tab.
    Network in motion Illustrative
    Illustrative leaf-spine topology Two spine switches connect to two leaf switches. Endpoint devices connect to the leaf switches. Animated dashed lines represent example traffic paths. SPINE 1 SPINE 2 LEAF 1 LEAF 2 HOST A HOST B HOST C HOST D
    STEP 01 / OBSERVE Inspect the network Explore the topology, devices and available network state.
    STEP 02 / TRACE Follow the behaviour Investigate routes, forwarding decisions and the paths traffic can take.
    STEP 03 / INVESTIGATE Think like an engineer Use what you observe to reason about changes, redundancy and failures.
    The topology above is illustrative. Open the simulator to explore the functionality it provides.