Tools & Platforms
Inventory, assess and secure industrial control systems.
Software built for industrial environments
Our platforms are designed for the constraints of the field: production networks that cannot be interrupted, legacy equipment, proprietary protocols and segmented architectures. They cover asset inventory, risk assessment and IEC 62443 certification support.
What our platforms cover
Three capabilities, used in this order on every engagement. Each one feeds the next: an inventory is what makes a risk assessment credible, and a risk assessment is what makes a certification file defensible.
Asset inventory
Know what is actually connected before trying to protect it.
An industrial site rarely has an up-to-date inventory. Our tooling builds one passively, by listening to the traffic already present on the network rather than probing equipment that cannot tolerate it. It identifies PLCs, RTUs, HMIs, engineering workstations and network equipment, along with their firmware versions, their protocols and the flows between them.
- Passive discovery, no active scanning on production segments
- Recognition of the usual industrial protocols
- Firmware and version tracking, mapped against known vulnerabilities
- Communication matrix between zones and conduits
Risk assessment
Turn an inventory into a ranked, defensible list of risks.
Once the installed base is known, the question becomes which weaknesses actually matter for this plant, this process and this level of exposure. Our assessment tooling ties each asset to the threats that concern it, weighs them against the operational consequence of a failure, and produces the justification trail an auditor will ask for.
- Threat scenarios tied to real equipment, not generic checklists
- Consequence weighting based on the industrial process at stake
- Ranked remediation plan, costed and sequenced
- Traceability from finding to requirement to evidence
IEC 62443 certification support
Follow the standard without rebuilding the paperwork every time.
IEC 62443 is demanding less because of its technical requirements than because of the evidence it expects. Our platform carries the requirements of the relevant parts of the standard, records the state of each one, and keeps the link between a requirement, the asset it applies to and the proof that it is met — through successive audits.
- Requirement tracking with security levels SL 1 to SL 4
- Zone and conduit modelling
- Gap analysis against the target security level
- Evidence retained between audit cycles
Designed for OT, not adapted from IT
Most security tooling assumes an office network: agents can be installed, machines can be rebooted, scans can run at any hour. None of that holds on a production floor. These four constraints shape everything we build.
Networks that cannot be interrupted
A production line does not stop for a security scan. Everything we deploy on an operational network is designed to be passive by default, and any active step is scheduled with the plant.
Legacy equipment
Industrial installations run for twenty or thirty years. Our tooling is built to work with controllers that predate any notion of network security, and that will not be replaced in the short term.
Proprietary protocols
Beyond Modbus and OPC UA, every vendor brings its own. We keep the protocol coverage of our tooling aligned with what we actually meet on our clients' sites.
Segmented architectures
A correctly built site is split into zones and conduits. Our tooling reflects that structure rather than flattening it, and works across segments without asking you to open them.
Not sure which platform fits your site?
Tell us about your installation — its size, its protocols and the standard you are working towards — and we will tell you what is relevant, including when the answer is that you do not need a tool yet.
Talk to us