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.
Learning Control Bar
Navigate five stages and track all 15 security activities.
Unified Security Learning Dashboard
Track your progress across five security stages and fifteen interactive activities.
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.
Stage 1 - Data Centre Security Architecture and Trust Boundaries
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.
What you will explore
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.
- 1 Security zones: group systems according to their role, sensitivity and exposure.
- 2 Trust boundaries: identify where access must be evaluated rather than automatically trusted.
- 3 Control placement: understand where firewalls, segmentation controls and management safeguards can enforce policy.
- 4 Blast-radius reduction: design boundaries that limit how far a compromised system can reach.
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.
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.
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.
B1 · External to Application
Test a Cross-Zone Connection
Choose a source and destination to evaluate the illustrative security policy.
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.
Segment workloads
3 · Engineering Design Review
Validate the controls for the selected objective.
Understand Security Architecture
Complete three interactive architecture activities to understand security zones, trust boundaries and enforcement controls.
COMPLETE
Stage 2 - Data Centre Traffic Security and Access Control
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.
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.
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 Security Topology
Choose a scenario or select a device to inspect it.
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.
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.
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.
1 · Build a Traffic Request
Select the source, destination, service and identity context.
Interactive Policy Decision Trace
Follow the three stages of a security policy evaluation.
Evaluate a request to activate the decision walkthrough.
2 · Policy Evaluation
Inspect the matched rule, enforcement point and decision.
Select Evaluate Traffic to inspect this request.
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 |
|---|---|---|---|---|---|
| R01 | Unknown workload | Any | Any | Any | DENY |
| R02 | External client | Application A | HTTPS | Any | ALLOW |
| R03 | Application A | Database | SQL | Verified | ALLOW |
| R04 | Application A | Application B | HTTPS | Verified | ALLOW |
| R05 | Application B | Identity service | HTTPS | Verified | ALLOW |
| R06 | Management workstation | Management plane | SSH | Privileged | REVIEW |
| R07 | Any | Database | Any | Any | DENY |
| R08 | Any | Management plane | Any | Any | DENY |
| R09 | Any | Any | Any | Any | DEFAULT DENY |
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.
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.
Interactive Security Topology
Select a scenario, trace traffic or inspect a workload.
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.
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.
Control Traffic and Access
Complete three interactive security activities to trace network traffic, evaluate access decisions and investigate segmentation.
COMPLETE
Stage 3 -Threat Detection and Security Incident Investigation
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
Security Telemetry and Visibility
Explore flow records, firewall logs, authentication events and workload activity. Understand which observations help reconstruct a suspicious network connection.
Threat Indicators and Alerts
Recognise unusual access attempts, unexpected lateral connections, repeated authentication failures and traffic anomalies that warrant further analysis.
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.
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.
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.
Interactive Investigation Topology
Select a device or play the investigation sequence.
Investigation Playback
Follow the sequence of synthetic security events.
Telemetry Event Timeline
Filter sources and select events to inspect the evidence.
Telemetry Sources
Investigation Assessment
Security Event Correlation
Correlate evidence from different monitoring systems. Filtering events changes the visible evidence, not the underlying incident.
Distinct sources contributing visible events.
High-severity signals in the filtered evidence.
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.
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.
Simulated investigation cases
Awaiting analyst assessment
Completed triage decisions
Referred for response
Security Alert Queue
Select an alert to inspect the available evidence.
Security Alert Investigation
Correlate evidence before choosing a triage action.
Highlighted components represent the selected case.
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.
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.
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.
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.
Interactive Incident Evidence Map
Select a network component to inspect its role.
Select a component to understand its investigation role.
Correlated Event Timeline
Select an event or play the recorded sequence.
Incident Reconstruction Dashboard
Review the accumulated evidence through the selected point in the investigation.
Visible events reached in the investigation sequence.
Different sources represented in examined evidence.
Interpretation based on available observations.
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.
Detect and Investigate Threats
Complete three investigation activities to correlate security telemetry, triage suspicious alerts and reconstruct incident timelines.
COMPLETE
Stage 4 - Zero Trust Architecture and Policy Enforcement
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
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.
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.
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.
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.
Configure access request
Change the attributes used by the policy decision engine.
Policy decision and enforcement path
Observe the request, policy evaluation and protected resource.
Inspect the access request attributes before evaluating the policy.
Policy model used in this lab
The simplified engine applies explicit authorisation rules before allowing a request.
Unknown roles are denied. Each protected resource accepts only designated identity roles.
Noncompliant workloads and high-risk contexts are denied. Unknown posture and elevated risk require additional checks.
Database access is limited to the database service role. Management access requires an administrator role and completed step-up verification.
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.
Interactive Session Enforcement Topology
Select a component to inspect its security role.
Green indicates authorised connectivity. Amber indicates a suspended session requiring validation. Red indicates termination.
Select Application A, Policy Enforcement or Protected API.
Current Trust Assessment
Establish the session to begin continuous trust evaluation.
Introduce a Security Event
Apply a condition change after establishing the session.
Guided Session Walkthrough
Establish an authorised session before introducing a security event.
Session Event Timeline
Follow the recorded changes in trust conditions, policy decisions and session enforcement.
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.
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.
Interactive Security Enforcement Topology
Select a network component to inspect its security role.
Zero Trust evaluates identity, role, resource and request context before granting access.
Select a component in the topology to inspect its role in the security architecture.
Select Access Scenario
Compare identical requests across enforcement models.
Guided Policy Evaluation
Follow how the selected access request is interpreted, evaluated and enforced.
Compare Security Enforcement Models
Each architecture applies a different level of access control and resource isolation.
External boundary protection with broad internal reachability.
Network-layer policies restrict selected cross-zone connections.
Explicit, identity-aware and resource-specific authorisation.
| Access scenario | Perimeter-only | Segmentation | Zero Trust |
|---|
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.
Apply Zero Trust
Complete three interactive Zero Trust activities to evaluate identity-aware access, investigate changing trust conditions and compare security enforcement architectures.
COMPLETE
Stage 5 - Incident Response, Service Recovery and Resilience
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
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.
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.
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.
Stop or limit malicious activity, prevent further compromise and establish confidence that affected systems are safe to return to service.
Minimise unnecessary disruption, prioritise critical services and restore business functionality through a documented, controlled process.
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.
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.
Interactive Data Centre Security Topology
Red = exposed threat · Amber = blocked route · Green = protected destination. Select any component to inspect it.
Select a containment action to evaluate its effect on the incident.
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.
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.
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.
Interactive Service Recovery Topology
Select a component to inspect its role in recovery.
The affected workload remains isolated until the recovery gates are completed.
Select Security Enforcement, Application Service, Network Fabric or Database Service.
Recovery Validation Workflow
Complete the six stages in order. Every stage requires two checks.
Stage 1 · Preserve evidence
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 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.
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.
Security Resilience Assessment
Illustrative maturity score and control-by-control improvement.
The incident exposed weaknesses in network segmentation, security visibility and operational response.
Interactive Security Control Map
Amber identifies incident-priority gaps. Green identifies selected improvements. Select a control to inspect it.
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.
Post-Incident Engineering Assessment
Review the incident findings and select corrective actions to address the identified control weaknesses.
Prioritised Improvement Roadmap
Select corrective actions and generate a post-incident review. The resulting roadmap should be assigned owners, milestones and effectiveness validation before closure.
Respond, Recover and Validate
Complete three interactive incident-response activities to contain security threats, restore trusted services and improve operational resilience.
COMPLETE
You have marked all three incident-response activities as complete. Review your overall progress in the Unified Security 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.
Five-Stage Learning Checklist
Complete the activities across all five stages to finish your learning pathway. Your progress is synchronised with the stage trackers and dashboard.
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.
Recommended Reading
Continue beyond the interactive security labs with four engineering guides covering data centre protection, firewall inspection, network security implementation and integrated security architecture.
Data Center Security
Explore modern data centre security architecture, Cisco ACI segmentation, workload isolation, microsegmentation and identity-driven access control. Understand how security policies reduce lateral movement and protect critical applications.
Cisco Firewall with Cisco IPS
Follow traffic through stateful firewall inspection, access policy, connection tracking and intrusion prevention. Explore Cisco Secure Firewall, Snort 3, threat detection and evidence-based security decisions.
Implementing Network Security
Examine practical network security implementation, risk assessment, access controls, firewall deployment, monitoring and vulnerability management. Connect architectural security principles with operational engineering practices.
Network Security Components
Understand how identity, access control, firewalls, segmentation, IDS/IPS, endpoint protection and security telemetry work together. Explore the relationship between enforcement, visibility and coordinated incident response.