SOC SCREEN SIMULATION
00:00:00 / 10:00:00
← EXIT

SOC Screen — Security Operations Center Dashboard Simulator

This page is the main wall screen of a security operations centre, the room where a company's security analysts watch for attacks and respond to them. It defends one invented company, XSCRIPT SYSTEMS, with eight sites around the world. A dot-matrix world map shows attacks arcing in from across the globe and breaking on a shield ring around each site. About every five minutes something gets through: a ransomware outbreak, a flood of traffic, a stolen-password attack. The camera flies to the site, opens a diagram of its network, and the incident is worked from detection to resolution. Over the full ten hours, one threat actor, GLASS VIPER, moves through every stage of an intrusion and is found, contained, and removed. Click ⛶ FULLSCREEN and it fills the screen.

Is any of it real?

No. It is an animation, and both the screen and the bar under it say SIMULATION. The company, its sites and endpoint counts, the threat actor, the analysts and shift leads, the IP addresses, domains, host names, and every line in the alert stream are invented and drawn in your browser. The page makes no connections while it runs, monitors nothing, and cannot reach your computer or anyone else's. The clock on the screen is a simulated UTC time, not your real time.

The shape of it is real, though. The panels, the metrics, the incident phases, and the campaign stages are the ones real security teams use, and the section on what a SOC does below explains each of them.

What's on the screen

What happens

Two things run at once: routine incidents, about one every five minutes, and one long campaign that takes the whole ten hours.

Incidents

The ten hours are split into 120 five-minute slots, each holding one incident somewhere inside it. Most incidents last between about 70 seconds and two minutes (the first, a quick one, takes 46 seconds), and each goes through the same four steps.

  1. Detected. The status turns red, the alarm glow comes up at the screen edges, an alert lands in the stream, and the on-call team is paged. The camera flies to the site over about three seconds.
  2. Triage. For roughly the first third of the incident, the analysts pull telemetry and scope the damage. In most incident types, red arcs from the attacker get through the shield to the site.
  3. Containing. The colour turns amber. The response named on the screen runs to 100%: scrubbing traffic upstream, forcing multi-factor sign-in, isolating a host, patching an appliance, cutting outbound traffic. Hostile packets stop at the cut link.
  4. Resolved. For the last 14 seconds the site shows RECOVERED and the callout turns green. The camera pulls back to the world over six seconds.

The routine incident types are ransomware detonation, DDoS flood, C2 beaconing, credential stuffing, insider data movement, zero-day exploit, and malicious package. The most serious ones (level 4 or 5) push the threat level to SEVERE or CRITICAL.

The GLASS VIPER campaign

The campaign starts unnoticed: during reconnaissance its three servers show only as faint dashed markers. As the investigation goes on they are identified one by one, labelled GV-C2-1 to GV-C2-3, and their amber traffic is tracked across the map. Four of the 120 incidents are the campaign's milestones, marked with a GLASS VIPER tag. In the eradication stage the servers are sinkholed and crossed out.

TimeSecondsCampaign stage or milestone
00:00:000Reconnaissance: port sweeps and probing of login pages
00:48:002880Spear-phishing; the first C2 server is identified
00:50:303030Spear-phishing wave at NYC-HQ: 214 lures sent to finance staff
01:54:006840Initial access; the second C2 server is identified
01:55:306930VPN appliance exploit at FRA-DC2 (level 5, CRITICAL)
03:00:0010800Persistence: implants and beacons
04:12:0015120Lateral movement; the third C2 server is identified
04:15:3015330Lateral movement incident at LON-OF
05:24:0019440Exfiltration
05:25:3019530Exfiltration attempt at SIN-DC3: 2.4 GB staged for upload
06:36:0023760Containment: the actor's infrastructure blocked everywhere
07:42:0027720Eradication: implants removed, C2 servers sinkholed
08:48:0031680Recovery and hunt, to the end of the cycle

Moments worth seeing in the first hour (seek with the bar or use ?t=):

TimeSecondsWhat happens
00:00:000Boot-up: the panels wipe on, the map scans in, and the sites light up
00:00:1212Ransomware detonation at DAL-DC1 in Dallas; containment from 0:28, resolved at 0:44
00:07:17437Ransomware detonation at FRA-DC2 in Frankfurt
00:12:14734Ransomware detonation at NYC-HQ in New York
00:15:43943Zero-day exploit against the application tier at FRA-DC2
00:23:031383DDoS flood at FRA-DC2
00:28:021682Credential stuffing at NYC-HQ
00:40:002400Shift handover from APAC (Singapore) to EMEA (Frankfurt)
00:50:303030GLASS VIPER spear-phishing wave at NYC-HQ
00:55:303330C2 beaconing at FRA-DC2

Over the full ten-hour cycle there are 120 incidents: 24 ransomware detonations, 21 DDoS floods, 17 cases of C2 beaconing, 14 of credential stuffing, 14 of insider data movement, 13 zero-day exploits, 13 malicious packages, and the 4 campaign milestones. NYC-HQ is hit most often (27 times) and the São Paulo office least (5). The simulated clock runs from 05:20 to 15:20 UTC, so the map's day/night line moves 150 degrees west across the map, and the watch passes from APAC to EMEA at 00:40:00 and from EMEA to AMER at 08:40:00.

How to use it

The page draws at the full resolution of your screen, up to 4K. On a slow computer it lowers the resolution by itself to keep the motion smooth.

Keyboard shortcuts

Good uses

Background screens for films, series, and adverts set in a security team, a newsroom covering a cyber attack, or a corporate war room; a wall display for a security awareness week, a careers fair stand, or an office lobby; a backdrop for talks, webinars, and podcasts about security; tabletop exercises, where the incident names give the team a scenario to talk through; escape rooms and live-action games that need a "we are under attack" screen; and gaming or coding streams. It is calmer than most hacking screens: the motion is steady, and the drama comes in short incidents. For OBS setup as a browser source, see the streaming toolkit.

What a SOC does

A security operations centre is the part of an organisation that watches for attacks and handles them. Some are a room with a wall of screens like this one; many are a team spread over several countries; smaller organisations often pay an outside provider to run one for them. The work is mostly reading, sorting, and deciding. Security tools produce far more alerts than people can look at, so most of a SOC's effort goes into finding the few that matter among the many that do not.

Tiers of analysts

Many SOCs split the work into tiers, though the names and boundaries vary.

Organisations with offices around the world often run the SOC as "follow the sun": teams in different time zones each take an eight-hour shift so nobody works nights. The SOC shift panel shows exactly that, with handovers between Singapore, Frankfurt, and Dallas. A good handover note, listing open cases and anything to keep an eye on, matters as much as any tool.

The tools behind the panels

SIEM
Security information and event management. It collects logs and events from across the organisation into one place, searches them, and raises alerts when rules match. The alert stream on the right is a SIEM view, and the events-per-second tile is the rate it ingests.
EDR
Endpoint detection and response: software on each laptop and server that records what runs on it and can isolate a machine from the network with one command. Isolating a host is the containment step for ransomware and C2 beaconing on this screen.
Firewall, IDS, and WAF
A firewall allows or blocks connections. An intrusion detection system (IDS) watches traffic for known attack patterns. A web application firewall (WAF) sits in front of a website and blocks malicious requests such as SQL injection. The site callout draws all three.
SOAR
Security orchestration, automation, and response: playbooks that carry out routine steps automatically, such as enriching an alert with context or blocking a known bad address everywhere at once.
UEBA
User and entity behaviour analytics. It learns what is normal for each account and machine and flags unusual behaviour, such as a finance account suddenly downloading a whole share.
Threat intelligence
Information about attackers and their infrastructure, shared between organisations and sold by vendors. The INTEL lines in the stream and the attribution figure in the campaign panel come from this side of the work.
Indicators of compromise
Concrete traces of an attack, such as a file hash, a domain name, or an IP address, that can be searched for elsewhere. The campaign panel's indicator count grows as the investigation finds more.
Sinkholing
Taking control of a domain that malware calls home to, usually with the registrar's help, so that infected machines talk to a harmless server instead. It is the last step for GLASS VIPER's servers here.

Triage, priorities, and the numbers on the wall

Cases are usually ranked by priority. P1 is an active, serious incident that needs people on it now; P2 and P3 are lower. The open-alerts tile and the P1/P2/P3 queue show the size of the pile. Two numbers are watched closely. Mean time to detect (MTTD) is how long it takes, on average, to notice something; mean time to respond (MTTR, sometimes mean time to resolve) is how long it then takes to deal with it. Both are tracked over weeks and months rather than minute by minute; the tiles on this screen move faster than real ones would, so there is something to watch.

The biggest everyday problem in a real SOC is alert fatigue: so many low-value alerts that the important one is missed. A lot of the work that never appears on a wall screen goes into tuning rules, automating the dull checks, and deciding what not to alert on.

The cyber kill chain

In 2011 researchers at Lockheed Martin published a paper describing intrusions as a chain of steps, borrowing the military term "kill chain". If defenders can break any link, the attack fails, so it pays to detect intruders as early in the chain as possible. Their seven stages are:

  1. Reconnaissance: researching the target, its people, and its exposed systems.
  2. Weaponisation: preparing the tool for the attack, such as a document carrying malicious code.
  3. Delivery: getting it to the target, most often by email.
  4. Exploitation: making it run, through a software flaw or by tricking a person.
  5. Installation: putting something in place that survives a restart.
  6. Command and control: a channel back to the attacker, often hidden in ordinary-looking web traffic.
  7. Actions on objectives: what the attacker came for, such as stealing data or encrypting it for ransom.

The campaign panel uses a simplified version that a SOC might put on a wall: reconnaissance, spear-phishing (delivery), initial access, persistence, lateral movement, and exfiltration for the attacker, followed by containment, eradication, and recovery for the defenders. Critics point out that the original model fits malware-led intrusions best and says little about what happens once an attacker is inside, which is why lateral movement is usually added as a stage of its own.

MITRE ATT&CK

Where the kill chain is a rough outline, MITRE ATT&CK is a detailed shared vocabulary. MITRE, a US not-for-profit, maintains a public knowledge base of the tactics attackers use (the goal at each step, such as initial access, persistence, lateral movement, or exfiltration) and, under each tactic, the specific techniques seen in real intrusions. The enterprise matrix has fourteen tactics and hundreds of techniques and sub-techniques. SOC teams use it to label alerts consistently, to check which techniques their detections cover and which they miss, and to compare notes with other organisations. Several of the campaign stage names on this screen are ATT&CK tactic names.

Incident response phases

Once an alert is confirmed as an incident, most teams follow a written process. The long-standing version of the US National Institute of Standards and Technology's incident handling guide, SP 800-61, describes four phases:

PhaseWhat happensOn this screen
PreparationPlans, contacts, tools, and practice before anything goes wrongThe shifts, the playbooks in the alert stream
Detection and analysisSpotting the problem, confirming it is real, and working out its scopeDETECTED and TRIAGE
Containment, eradication, and recoveryStopping the spread, removing the attacker, and restoring normal serviceCONTAINING and RESOLVED; the last three campaign stages
Post-incident activityReviewing what happened and what to change"Incident closed · report filed" in the stream

In practice the phases overlap and loop: containing one machine often turns up another. The first thing a team protects is evidence, which is why "snapshot taken" lines appear before a host is wiped.

The incident types on the screen

Ransomware
Malware that encrypts files and demands payment for the key. The usual response is to isolate affected machines quickly and restore from backups that the attacker could not reach.
DDoS flood
A distributed denial-of-service attack sends more traffic than a service can handle, from many machines at once. Large floods are absorbed by scrubbing services upstream. The guide to what a DDoS attack is explains it in plain English.
Credential stuffing
Trying usernames and passwords leaked from other websites, in bulk, against a login page. Rate limits and multi-factor authentication are the main defences.
C2 beaconing
An infected machine checking in with its command-and-control server at regular intervals. The regular rhythm and the rare domain are often what gives it away.
Insider data movement
A large or unusual copy of data by someone inside the organisation. Most such alerts turn out to be innocent, which is why they are handled with care.
Zero-day exploit
An attack on a software flaw for which no fix exists yet. A "virtual patch", a WAF rule that blocks the attack pattern, can buy time until the vendor ships one.
Malicious package
A poisoned software library, often with a name one letter off a popular one, pulled into a build. It is one form of supply-chain attack.

How the simulation works

The whole ten-hour cycle is worked out in advance from a fixed random seed: when each incident starts and which site it hits, and about 154,000 attack arcs, each with its source city, target, type, and flight time. Each arc on the map stands for many blocked attempts, so the per-minute counts in the panels are much larger than the number of arcs. The world map is a grid of one-degree dots from a stored land mask, shaded by a simple model of the sun for mid-November driven by the simulated clock. The camera is a flat map view that zooms smoothly in and out, so a dive onto a site reads as one move. Because every frame is a function of the time alone, the page can jump anywhere in the cycle at once, and the same moment always looks the same. To protect screens left on for hours, the whole layout drifts a few pixels on a slow path.

Frequently asked questions

Is this a real security operations centre?

No. It is an animation. The company, its eight sites, the threat actor GLASS VIPER, the analysts, the IP addresses, the host names, and every alert in the stream are invented and drawn in your browser. The page connects to nothing, monitors nothing, and cannot affect your computer or anyone else's.

What is a SOC?

A security operations centre (SOC) is the team, and often the room, that watches an organisation's computers and networks for attacks and responds when something goes wrong. Analysts work through alerts from security tools, investigate the ones that matter, and lead the response to confirmed incidents. Large SOCs run around the clock in shifts.

What is the cyber kill chain?

It is a model of the steps an intruder goes through, from researching a target to achieving their goal. Lockheed Martin published the best-known version in 2011 with seven stages: reconnaissance, weaponisation, delivery, exploitation, installation, command and control, and actions on objectives. The idea is that defenders who break any link stop the attack. The campaign panel on this screen uses a simplified chain that ends with the defenders' response.

How long does it run before it repeats?

Ten hours. In that time the SOC handles 120 incidents, one in each five-minute slot, and the GLASS VIPER campaign moves through all nine stages, from reconnaissance at the start to recovery and threat hunting in the last 72 minutes. Then the cycle starts again. The screen is calculated frame by frame rather than played from a recording, so it needs no download and never buffers.

Can I jump to the interesting parts?

Yes. Drag the seek bar, or press the left and right arrow keys to move ten seconds at a time. To open the page at a given moment, add ?t= to the address with the number of seconds, for example ?t=3030 for the GLASS VIPER spear-phishing wave.

Can I use it in a video or on a stream?

Yes. It is free to use for videos, films, streams, presentations, training sessions, and events. Click FULLSCREEN, or add the page as an OBS browser source at 1920 × 1080 or 3840 × 2160; the scene is drawn at the full resolution of the source.

Does it flash?

No. There are no white flashes, full-screen fades, or strobing. While a serious incident is open, the edges of the screen glow red and the glow swells and eases about once every three seconds, then fades as the incident is contained. Blocked attacks make small, brief flashes on the rings around each site. The first few seconds of the cycle are a boot-up in which the panels wipe on. If your system is set to reduce motion, the page opens paused. See accessibility and visual effects for more.

Does it work offline?

Once the page and its fonts have loaded, the simulation makes no further network requests, so it keeps running if the connection drops. The optional VIDEO view streams from YouTube and needs a connection.

Related tools

For a wider view of attack traffic between countries, open the cyber attack map; the guide to what a DDoS attack is explains one of the incidents here in more depth. The data centre simulator shows the infrastructure a SOC protects, and the tech dashboard is a general-purpose monitoring wall. For the other side of the story, the system breached screen shows what an attack looks like when the defenders lose.