Security monitoring, around the clock.
24/7 security monitoring across IT and OT, run alongside our NOC so availability and security alerts are triaged by one team. On the corporate side we watch identity and endpoint telemetry: unusual sign-ins, new mailbox forwarding rules, service accounts logging on interactively, privileged group changes. On a control network we alert on change: a new device, a new conversation, a controller switched into program mode. Detections are tuned to your environment and your maintenance calendar.

Why it matters
A SOC is only useful if its alerts mean something. We tune detections to your environment and your maintenance calendar, so planned work doesn't page anyone and genuinely unusual behaviour on IT or OT networks does.
What it covers
- Identity, endpoint and network telemetry
- Endpoint, firewall, identity and cloud-tenant logs into a SIEM, with detections for credential abuse, privilege changes and lateral movement, correlated with the OT side rather than kept in a separate silo. Coverage mapped against MITRE ATT&CK.
- OT-aware detection
- New asset, new conversation, PLC mode change to program, firmware or logic download, unexpected function codes, for example a Modbus write from a host that is not the engineering workstation. Coverage mapped against MITRE ATT&CK for ICS.
- Escalation and runbooks
- Runbooks agreed with your site, an escalation path, and a person who picks up the phone, not only a dashboard.
How it runs
Map the coverage
A detection coverage map against ATT&CK for ICS, so you can see what is watched and what is not, rather than assuming everything is covered.
Learn the site
Your maintenance calendar and your normal, so planned maintenance doesn't trigger alerts and unexpected behaviour does.
Triage and escalate
Alerts triaged against that baseline and escalated on the runbook you agreed, with the reasoning attached.
Report
A monthly report and incident notes you can hand to an auditor or an insurer.
What you receive
- Detection coverage map against MITRE ATT&CK for ICS.
- Escalation runbook agreed with the site.
- Monthly report.
- Incident notes.
Worked to
- MITRE ATT&CK for ICS
- NIST CSF 2.0 (Detect, Respond)
Common questions
How do you keep false alerts down?
The detections are tuned to the estate we watch and to your maintenance calendar, so a booked change does not page anyone and a genuinely new behaviour does. Alerting on change means the quiet plant stays quiet.
Do you understand OT alerts, or just forward IT ones?
OT-aware detection is the point: mode changes, logic downloads, unexpected function codes and new conversations, mapped to ATT&CK for ICS, not a Windows signature set pointed at a PLC.
Related services
Tell us what you need.
Email, call or use the form below. The first call is free, and if the work isn't a fit for us, we'll tell you and recommend someone who is.
A free first call to talk through what you need.
A fixed-scope first engagement: one site, an assessment you can act on.