One server in Toronto, ON, left open to the internet
Every arc is an attack attempt, timed from published averages for an exposed server. Turn on security layers one at a time and watch what each one stops.
- Inbound /hr
- 0
- Exposure
- 100%
- Risk
- Critical
- reached target
- blocked at edge
- compromise / lateral
- contained
Mitigation controls
Turn on a layer and watch what it stops. Rates are modelled on published averages for an exposed server.
Simulation, not live data. 1× is real time; 10× and 60× compress an hour into 6 and 1 minutes.
- Blocked
- 0
- Reached
- 0
- Breaches
- 0
Cost of downtime
- Revenue / hr
- $9,845
- Lost so far
- $0
Average Ontario company this size. An uncontained breach has a 40% chance of a 36-hour outage.
Event log
- Waiting for traffic…
0 of 5 layers on. Baseline is about 1,274 attempts an hour.
Where the numbers come from
Arrivals follow a Poisson process using the hourly averages below. Where no good public figure exists we say so and use a stated assumption.
- SSH / RDP brute force757
5.4M login attempts across 10 cloud honeypots in 30 days, about 757 per server per hour.
Sophos, Exposed: Cyberattacks on Cloud Honeypots (2019) - Web exploit attempts440
About 960,000 blocked attacks per site in Q2 2024, roughly 440 per hour.
Indusface, State of Application Security Q2 2024 - Credential stuffing76
Median 19% of authentication attempts are credential stuffing. We assume the portal sees 400 logins an hour. assumption
Verizon, 2025 DBIR credential stuffing research - DDoS burst0.5
Cloudflare mitigated 47.1M DDoS attacks in 2025. Per-server frequency varies widely; we model one burst every two hours. assumption
Cloudflare, 2025 Q4 DDoS threat report - Lateral movement—
Spawned after a successful compromise: the attacker scans and pivots to neighbouring hosts.
- Chance an attempt succeeds0.14%
Weak-credential SSH honeypots were compromised about 26 times a day, against ~18,000 daily attempts.
Palo Alto Networks Unit 42, honeypot compromise study (2021)
- Geo-IP blocking100% of non-CA/US
Drops any connection from outside Canada and the US at the edge firewall, before it reaches a service.
- DDoS mitigation & rate limitingDDOS 100%BRUTE 90%CRED 60%
Upstream scrubbing absorbs volumetric floods; per-source rate limits and lockouts stop most repeated login attempts. assumption
- Web application firewallWEB 95%
Inspects HTTP/S requests and blocks known exploit patterns (SQL injection, path traversal, scanner signatures). assumption
- Multi-factor authenticationBRUTE 99.2%CRED 99.2%
A correct password is no longer enough. Microsoft measured a 99.22% drop in account-compromise risk with MFA.
Microsoft, MFA account-compromise study (99.22% risk reduction) - Network microsegmentationLATERAL 100%
A compromised host can only reach the services its segment allows, so the attacker cannot pivot.
- Revenue per employee, Ontario$409,542
Ontario non-financial enterprises reported $2.15 trillion in total revenue in 2024 across 5.25 million paid jobs. Finance and insurance are left out because their revenue per job is not typical of a mid-sized office.
Statistics Canada, Table 33-10-0551-01: Financial and employment statistics for enterprises, by province (2024) - Business hours a year2,080
A 40-hour week, 52 weeks a year. Lost revenue is counted at this rate for every simulated hour of outage, so treat the total as an upper bound. assumption
- Revenue per hour, 25 to 100 staff$4,922–$19,690
Headcount × revenue per employee ÷ business hours. A 50-person company comes to about $9,845 an hour.
- Outage after a breach40% · 36 h
Of businesses hit by a cyber incident in 2021, about 40% had downtime, averaging 36 hours. A breach that segmentation does not contain takes systems down with that chance and for that long.
Statistics Canada, Impact of cybercrime on Canadian businesses, 2021
Source countries are an illustrative mix weighted toward large hosting regions, which is where most scanning traffic comes from. Real exposure depends on what you run, where it is hosted and how it is configured, which is what an audit measures.
Find out which of these layers you actually have.
Our infrastructure audit checks each control on your real network and ranks what to fix first.