Your browser could not start the 3D view. The device list and the steps below tell the same story.
One flat network
POS
Cameras & IoT
Back office
Drag to rotate · click any device
78
paths any device could open to another
Alert
00:00
Managed IT, networks and security · Toronto
Networks for stores, clinics and offices, watched around the clock.
Kestrel designs, secures and monitors small-business networks across Ontario. This is one store from a 12-location retail chain we rebuilt. Scroll through it, or click any device.
Card terminals, cameras and the back-office PC shared one switch fabric, and remote access ran on shared VPN passwords. We assessed 3 reference stores, then rolled the new design out to all 12 on staggered nights.
01 · The store
Twelve devices, one switch
Two checkout lanes, four cameras and a recorder, a cooler sensor, a door sensor, a smart lock on the back door, the staff Wi‑Fi and one back-office PC. Every cable ends at the same switch in the back-office rack. Each red line is a path one device could open to another: 78 in total.
02 · Where it broke
One segment, one password, no owner
Flat network. A camera could talk to a card terminal as easily as to its recorder.
Shared VPN password. The same login opened every store for anyone who had it.
Cameras next to the tills. Anything that took over a camera could see the card terminals.
2–4 hours after hours. The previous MSP blamed the firewall vendor; nobody owned the call.
03 · What we changed
Three zones with firewall rules between them
78 open paths became 11 allowed ones. POS, cameras and IoT, and the back office each got their own VLAN. The firewall allows only the paths a store needs and denies the rest by default. Remote access moved to per-user MFA, and every VPN or POS alert now goes to a named person at the Kestrel NOC.
Firewall rule audit and deny-by-default between segments
MFA on all remote access, one login per person
Alerting with named escalation, 24/7
A one-page “what to do when the VPN is red” sheet for store managers
04 · Same attack, two networks
Say a camera gets compromised. What can it reach?
On the old network the traffic walks from the camera through the switch to the card terminals and the office PC. On the new one the firewall drops it at the edge of the camera zone, and the alert is acknowledged by a person.
05 · Result
Incidents now have an owner and a clock
Overnight “who do we call” incidents stopped. The IT lead gets one thread with the root cause instead of vendors pointing at each other.
What changed across the chain
<15min
Mean time to acknowledge VPN and POS alerts in the first 90 days, down from 2–4 hours after hours
12
Stores moved to segmented VLANs, rolled out on staggered nights
3
Zones per store: POS, cameras and IoT, back office, with deny-by-default rules between them
1
Owner for the rack, the VPN and the escalation path
“Our old MSP blamed the firewall vendor. Kestrel owned the rack, the VPN and the escalation path end to end.”
IT lead, 12-store retail chain
What we do
One team for the network, the security around it and the people who answer when it breaks.
01
Network design
Switching, Wi‑Fi and VLANs planned per site, so tills, cameras and staff devices never share a segment. Rollouts after closing time.
02
Security and access
One login per person, a second factor on every remote session, tested backups and a firewall rule audit you can read.
03
24/7 monitoring
VPN, POS links and firewalls watched by our NOC. Every alert goes to a named engineer, not a queue.
04
Cameras and IoT
Cameras, recorders, door sensors and smart locks installed on their own zone, with no route to the tills.
Kestrel NOCLive · demo data
142sites
141healthy
1open alert
6 minmedian ack, 30 days
Site
VPN
POS link
Latency
Store 04 · Mississauga
Up
Up
18 ms
Store 07 · Oakville
Up
Degraded
96 ms
Clinic · Yorkville
Up
n/a
22 ms
Store 11 · Barrie
Up
Up
31 ms
Office · Liberty Village
Up
n/a
9 ms
Store 07 POS link degraded, ISP packet loss 4%
Acknowledged by Dana Okafor, ticket opened with the ISP
Failover to LTE backup, POS link back to normal
Who we work with
RetailChains of 3 to 40 stores, POS and payment networks, after-hours support
ClinicsDental and medical offices, patient data kept apart from guest Wi‑Fi
Offices10 to 150 people, Microsoft 365, remote staff and one help desk
RestaurantsOrdering tablets, kitchen printers and cameras that stay online on a Friday night
How a project runs
Week 1AssessmentWe walk two or three sites and map every device and login.
Week 2DesignZones, firewall rules and access, written up on one page you can approve.
Weeks 3–6RolloutSite by site after closing, with a manager sign-off each morning.
OngoingMonitoringThe NOC takes over, and you get one report a month.
Plans
Monthly, per site. Setup is quoted after the assessment.
Monitor
$190/ site / month
24/7 alerting on VPN, POS and firewall
Named escalation
Monthly report
Managed
$390/ site / month
What most store chains choose
Everything in Monitor
Firewall, switch and Wi‑Fi management
MFA and access reviews
Unlimited remote support
Managed + cameras
$520/ site / month
Everything in Managed
Camera and IoT zone management
Recorder health checks
Does your store look like the before?
Tick what is true today. It takes thirty seconds and nothing leaves this page.
Founded in Toronto in 2014. Eighteen engineers, one NOC, and a rule that every client knows who to call.
DODana OkaforNetwork lead
MTMarc TremblayIdentity and security
PRPriya RamanNOC manager
Book a network review
Tell us how many sites you run. Dana or Marc will call you within one business day to set up the assessment. This is a demo: the form does not send anything.