The engagement

Prove your exposure —
before you buy enforcement tools.

The Critical-Conduit Assessment covers one conduit and takes a few weeks, at a fixed price set after scope confirmation. It is off-path throughout — we never transmit on your network, and the tap/SPAN change is made by your team under your change control. No device inserted, no writes, no change to any validated system. You walk away with one clear deliverable your engineering team owns — countersigned by your engineer and cryptographically signed by us. A second conduit is scoped and priced separately.

Passive
SPAN / tap only — nothing inline
2–4 wks
Tap to final report, one conduit
1 conduit
The unit of sale — a second conduit is scoped and priced separately
Fixed price
Set after scope confirmation, before any work starts
Scope

One conduit. The one that keeps you up at night.

A conduit is the link between an operator screen and the controller that runs a physical thing. One conduit is the unit of sale: we take a single, high-consequence one and work it end to end. If you want a second conduit covered, it is scoped and priced separately — never bundled in as an assumption.

HMI ↔ PLC

The screen-to-controller path for a life-safety process.

BMS ↔ controller

Building management — HVAC, chillers, medical gas, power.

Engineering workstation ↔ controller

The maintenance path where dangerous writes originate.
The engagement

From tap to final report.

Six steps on the one conduit in scope. Facilities and clinical/plant engineering are in the room from day one — they own the equipment, and their sign-off is what turns findings into decisions.

01

Scope

Pick the conduit, name the owners, arrange a read-only tap.
02

Observe, passively

Capture off to the side. Nothing inline, nothing written.
03

Engineering / biomed validation

Sit with the people who know what each point physically does.
04

Consequence mapping

Every dangerous write mapped to its real-world worst case.
05

Existing-control analysis

What your current stack actually covers — and where it doesn't.
06

Findings workshop & final report

Walk the results together; your engineer countersigns the findings and you receive the cryptographically signed, prioritized remediation plan.
What you walk away with

Artifacts, not slideware.

Four documents covering the one conduit in scope.

Register-consequence map

Every dangerous write, its physical meaning, and the worst case if abused — countersigned by your engineer.

Write-path coverage matrix

Which function codes can reach each critical point, and which are covered today.

Compensating-control assessment

What your existing firewalls / segmentation actually prevent — and the gaps.

Per-register fail-mode sheet

A "fail-safe vs fail-open" decision for each critical device, countersigned by your engineer.
What you provide

Low lift. No credentials to any control system.

A read-only tap or capture

SPAN port, tap, or an existing PCAP from the conduit.
🗺

Network & asset context

The segment, the controllers, and any register documentation you have.
🤝

An engineering owner + your existing controls

The person who knows the equipment, and details of the firewall/NAC you already run.
Who does the work, and what "signed" means

Yechiel performs every assessment.

Wardhelm is a small, senior practice, not a bench of rotating consultants. Yechiel is the engineer who scopes the conduit, runs the passive capture, does the analysis, and sits in the findings workshop — the same person from the first call to the final report. You always know who is on your site.

Countersigned by your engineer

Every consequence claim is walked line by line with your facilities or biomed engineer, who signs it off. That signature says the physical meaning is correct — and it comes from your side, not ours.
🔐

Cryptographically signed report

The delivered report carries a digital signature and hash, so you or an auditor can verify later that the copy you hold is exactly the one we handed over, unaltered.

Two different things

When this site says "signed", it means one of those two — a human engineering sign-off on the findings, or a cryptographic signature on the file. Neither is a certification, and neither is an enforcement action.

Scope your first conduit. One conduit, fixed price after scope confirmation.