Hardening IT and OT Detection Audit trail

Better protected. Every step logged.

Cybersecurity for everything that runs code in your organisation. We find what runs, carry out the updates, watch for attacks and log every step: a record you can show auditors, insurers and NIS2 supervisors.

We only read, change nothing, and you keep the results.

Not ready to talk yet? Get our checklist and the monthly letter.

Why now

The flaws are public. Attackers read the list too.

Scanners record which software and versions answer where, all the time, so the first attempts can come within minutes of a flaw being published, often before its patch. Updates are one part of the work. We also watch for the attack itself, and answer it.

4,926

new vulnerabilities published in the past seven days, 23 of them rated critical so far

38

added in the past 30 days to the list of flaws already used in attacks

−7 days

estimated average in 2025 from a patch’s release to the first attack: a week before the fix existed

<30 min

from publication to the first attack attempts we saw on CVE-2026-98432, a Linux kernel flaw, in October 2026

What attackers used, once a month

One email: the flaws added to that list in the month, by kind of product, and one thing worth checking on your own systems. Read November’s letter.

The monthly letter and occasional news from H2 Labs: what attackers used each month, one thing worth checking, and now and then a new checklist, tool or service of ours. The checklist comes first. We email a link to confirm the address, and every email has a one-click unsubscribe.

H2 Labs keeps this address; Resend, in the United States, delivers our email. What we keep and for how long: privacy notice.

Counted on 13 November 2026. Sources: nvd.nist.gov (critical means CVSS v3 critical, and many new entries are not scored yet) · CISA Known Exploited Vulnerabilities, catalogue 2026.11.10, 1,779 flaws in all · Mandiant, M-Trends 2026 (the estimated mean time to exploit in 2025, counted from the patch’s release) · H2’s own logs for CVE-2026-98432.

What we do

Find, fix, watch, show

Four parts of one service, for everything that runs code in your organisation. Start with the first, and add the others as you need them.

Fig. 1 Find, fix, watch, show: one loop around your systems

Find

Know what runs

Every system that runs code, from servers and cloud accounts to network gear and plant controls, checked against the flaws being exploited and against end of support.

Fix

Updates, done

We carry out the updates, the intricate ones included: platform and operating system upgrades and firmware, planned around your business, with a way back at every step.

Watch and respond

Attacks, answered

EDR on your systems and a SIEM over your logs look for scans, attacks and signs of a breach. Each gets an automatic first response and a person alerted.

Show

Everything on the record

Every action, change and check is logged: who, what, when and why. A short summary each month, and full audit logs on request.

What we cover

Everything that runs code, and every way it connects. A system nobody lists is a system nobody watches.

  • Servers and cloud Linux and Windows Server, hypervisors, containers, cloud accounts
  • Network Routers, firewalls, switches, VPNs and Wi-Fi
  • Industrial and OT Controllers, sensors and plant networks
  • Devices and links Building and meeting-room systems, cameras, printers, Bluetooth
  • Access Single sign-on, passkeys, Linux login and sudo rules, with Identity Core
  • Workstations Hardened Linux for the people with the most access, with UHT

How each part runs, the discipline behind it, and the balance we set with you →

We also build tooling and connect the platforms you already run →

Getting started

Three steps, the first one free

You keep the responsibility and get the evidence. We run all four parts, share them with your team, or install the tools on your side and train your people to run them.

Before step 1, if you like: what the internet sees of you. Send us your domain and we send back what anyone can see of you from outside, from public sources only. Free, with no access and no call.

How far to go is a balance of security, ease of use, cost and speed of change. We set it together for each kind of system, and write it down. See three examples.

Already under attack? Emergency response within hours, subject to availability and authorised access. Request incident assistance → Or read how a response runs.

Not ready to talk yet

What is actually running: a checklist

Attackers look for the system nobody listed. The checklist helps you find yours first, in about an afternoon, without our tools and without a call.

  1. Devices that run code and were never listed, such as building and production controls
  2. Systems past the end of their support
  3. Services listening on the network that nobody chose to open
  4. Accounts nobody uses, and accounts with more access than the job needs
  5. Connections that leave your network, and where they go
  6. Changes nobody can explain

Read November’s letter before you sign up →

First we email a link to confirm the address. The checklist arrives once you press Confirm on the page it opens; the letter and news start only if you tick the box.

H2 Labs keeps this address; Resend, in the United States, delivers our email. What we keep and for how long: privacy notice.

Why H2

People who have done this on production fleets, IT and OT

Done at scale

The team has run inventory, vulnerability triage, planned platform upgrades and detection for production fleets of thousands of hosts and assets in managed security operations.

IT and OT

The team has worked on industrial sensor fleets and locked-down enclaves as well as data centres, and runs IT with a plant’s discipline: every device known, every change planned and reversible, and scheduled around your operations.

The details, done

Each of your administrators gets two hardware keys. One touch signs in to your single sign-on and confirms each sudo, and the same keys still open the servers when the sign-on is down. We check that twice a year. What comes with every plan.

Stays on your side

We work on your systems with your permission and leave the results with you. Our tools run on your servers or the cloud you choose.

Under European law

A European team, working under European law and the contract we sign with you.

Work in the open

We publish field notes and essays from the work itself.

Also from H2 Labs

What else we build and run

H2 Labs is a European technology and social lab. These are tools we built for our own work, and run ourselves. All of them, with drawings, on one page →

Security tools

  • UHTHardened, immutable Linux for workstations and hosts.
  • Identity CoreSelf-hosted single sign-on, passkeys, Linux login and sudo rules.
  • Runtime AssuranceKnow what runs, control what changes, act with evidence.
  • askdNo inbound port: machines dial out, silent to scans.
  • Isolation stackLandlock, egress allowlists and sandboxes that fail closed.

Operations

  • H2 PagerOn-call paging for when Atlassian switches Opsgenie off on 5 April 2027.
  • Windows to LinuxKeep good hardware working on a maintained system.

Platform and agents

  • ServoThe self-hosted app platform this site runs on.
  • ZoyaA sovereign personal agent with a memory that never resets.