PWX Discover
Agentless. Finds every power component across the fleet, maps firmware to known CVEs and shows attack paths from an exposed BMC to GPU damage.
Open the live consolePOWER-LAYER SECURITY
Your tools protect software.
PWX protects the physics.
A compromised administrator or firmware component can issue commands beneath SIEM and EDR visibility. PWX maps this hidden layer, establishes a physical baseline and raises a verdict from the rail before hardware is damaged.
THE PRODUCT LINE
PWX Monitor
Continuous monitoring, alerts and SIEM export, into the tools you already run.
See the integrationsPWX Protect
Six modules, from millisecond detection by the PWX-01 agent on the BMC to inline blocking with PWX-06. PWX-01 is proven on our bench; PWX-06 is on the roadmap.
See the six modulesTHE PWX PLATFORM
One power graph, from the management interface to the silicon.
PWX Discover, agentless, to see the fleet through Redfish. The PWX-01 agentwhere you need milliseconds, on PMBus. Every power event is tied to who issued it, what hit the rail and what it did to the CPU and GPU, then correlated at the edge into one verdict.
REDFISH CONNECTS ON REAL SERVERS DURING THE PILOT · PMBUS AGENT AT 100 HZ · VERDICTS INTO THE SIEM YOU ALREADY RUN
THE PWX CONSOLE
One console. Three people, three answers.
What Dana, Alex and Finkel open every morning: the fleet without an agent, the paths to the power, the rail live at 100 Hz, the findings that reach the SOC, and how an attack is stopped and proven.
Power surface: every way in to the power →Power postureApplied across every vendor, re-checked every 4 hours
Last scan · 12m agoBMC accounts hardened412 BMCs · drift +3
Host Interface off128 still on
Firmware current11 with known CVEs
Rails write-protectedconfirmed by agent
DANA · SOC LEADPILOTWhich path reaches my GPUs, and what closes it.
Every setting that lets a host reach a rail, scored across every vendor and re-checked every four hours. Dana fixes the one that protects the most hardware first.
ALEX · SOC ANALYSTTODAYThe rail, live. The verdict in 20 ms.
A hundred samples a second from the regulator. When a command drives the rail outside its safe range, the verdict strikes with the physical evidence attached, then the rail settles. Alex gets the finding, not the firehose.
FINKEL · CFOPILOTEvery power component, found without installing anything.
Read-only through the management interfaces the fleet already has. Model, firmware and source for every BMC, regulator, GPU board and PDU. Nothing new in the rack, nothing to approve.
ALL EIGHT WINDOWS
Power inventory2,184 components · 9 vendors · discovered without an agent
Last scan · 6m ago| Layer | Asset | Model | Firmware | Source |
|---|---|---|---|---|
| BMC | gpu-node-17 | Dell iDRAC9 | 7.10.50 | Redfish |
| Regulator | CPU0 VCORE | Infineon XDPE | rev 2A | Redfish * |
| GPU board | HGX · 8× H100 | NVIDIA HGX | 24.03 | HMC |
| PSU | PSU 1 | Delta 3,200 W | 00.0E.02 | Redfish |
| Rack power | R12 · PDU A | Raritan PX4 | 4.2.0 | SNMP |
Every power component, found on day one.
Read-only through Redfish, IPMI, DCGM and SNMP. Model, firmware and source for every BMC, regulator, GPU and PDU. Nothing installed, no new hardware.
Power postureApplied across every vendor, re-checked every 4 hours
Last scan · 12m agoBMC accounts hardened412 BMCs · drift +3
Host Interface off128 still on
Firmware current11 with known CVEs
Rails write-protectedconfirmed by agent
Power posture, checked every four hours.
The settings an attacker needs to reach the power: BMC accounts, the host-to-BMC channel, firmware age, rail write-protection. Drift shows up before an attacker uses it.
Attack paths to the railRanked by physical impact
CRITICALHOSTgpu-node-07
BMCdefault account
RAILVRM_01
ASSET8× H100
1Tenant VLAN → Redfish → VOUT_COMMAND3,600 GPUsCRIT
2Host Interface on → BMC128 serversCRIT
3Shared root credential → 47 BMCs47 serversHIGH
Every path ends at a rail. Fix that one first.
PWX follows each path from a host through the BMC to the regulator and the GPUs behind it, and ranks it by the hardware it can physically break.
VRM_01 · output voltagegpu-node-07 · PMBus · 100 Hz
LIVEFRAMES / S100
VOUT NOW5.212 V
VERDICTNORMAL
The rail, live at 100 Hz.
The agent reads every regulator rail a hundred times a second. When a command drives a rail outside its safe range, the verdict lands in 20 ms with the physical evidence attached.
Today in your SIEMSplunk · Datadog
Last 24 h0power events
0anomalies
3findings
CRITSetpoint rewrite on VRM_01 · gpu-node-07T0836
HIGHUnexplained sustained load · rack R12T1496
MEDLogin to BMC from the host channelT1078
Findings, not firehose.
Forty thousand power events become three findings, each with the asset, the evidence and the ATT&CK mapping, in the Splunk or Datadog your team already runs.
Rail health · fleetHealth score 0 to 100, per rail
8,640 rails050100
FLEET SCORE0
TRENDING TO FAIL3 rails
WINDOW72 h ahead
Rail health the operations team pays for.
The same 100 Hz stream scores the health of every rail: ripple, drift and thermal margin. Failing regulators show up days ahead, so the fleet runs closer to its real limits.
Response tiersFrom the first malicious write to the paperwork
speedPWX-06 blocks the command in the BMCnever reaches the railROADMAP
Detect at the rail, physical evidence20 msTODAY
Fleet rule pushed to every BMCunder 1 sROADMAP
Your SOAR isolates the BMC portsecondsPILOT
SIEM alert and ticketminutesTODAY
Stopped in milliseconds, not in a ticket.
When an attack is live there is no time for a ticket. PWX-06 filters power commands inside the BMC and drops a malicious write before it reaches the rail. Detection at the rail runs today.
Incident PWX-2291 · confirmed attackgpu-node-07 · rack R12 · signed audit chain
ATTACKT+0 sLogin to the BMC from the host
T+40.000 sVOUT_COMMAND to VRM_01
T+40.020 sVerdict ISOLATE, SOA breach
T+44 sSOAR isolated the BMC port
T+6 minTicket closed with evidence
NIS2 Art. 21IEC 62443 SR 2.8PMBus 1.5 profileSHA-256 audit chain
One chain of evidence the auditor accepts.
Who issued the command, what it did to the rail, what PWX decided and what your controls did, in one signed record. The same record feeds the NIS2 and IEC 62443 evidence packs.
ILLUSTRATIVE CONSOLE · NUMBERS ARE EXAMPLES · LIVE: PWX DISCOVER AND PWX MONITOR, AGENTLESS INVENTORY, FIRMWARE CVES, ATTACK PATHS, SIEM EXPORT · ON OUR BENCH: PWX-01 AGENT AT 100 HZ, 20 MS DETECTION · PILOT: REDFISH ON YOUR SERVERS, RAIL HEALTH, SOAR HOOKS · ROADMAP: PWX-06 INLINE BLOCKING, FLEET RULES
PWX PROTECT
Six modules, one deployment.
PWX-01 · PROVEN ON OUR BENCH
Silicon Sentinel
The agent on the BMC: rails sampled at 100 Hz, attack to verdict in milliseconds
PWX-02 · NEXTCompliance Reporter
Agent-grade evidence for NIS2 and IEC 62443, with evidence packs on demand
PWX-03 · NEXTPower Management & Predictive
Degrading power hardware surfaced before it takes a server down
PWX-04 · ROADMAPPowerCert
Certification for the vendors who build the power components, against the standard your fleet is measured by
PWX-05 · ROADMAPPWX-Connect
Agent verdicts carried into your OT and security tools, beyond the SIEM export in PWX Monitor
PWX-06 · ROADMAPEnforce · Power Firewall
Every power command checked against policy inside the BMC; a malicious write dropped before it reaches the rail
WHAT IT IS WORTH
Two problems, one layer.
FOR SECURITY
An attacker who reaches the power layer can damage silicon permanently, and nothing above it will record how. PWX holds a physical baseline of your hardware and acts on physical evidence, not on a statistical guess.
- Attack detection grounded in measured behaviour
- Response only on physical or protocol evidence
- Evidence trail that survives the incident
FOR OPERATIONS
The same measurements show hardware degrading before it fails. Power components drift for hours or days before they take a server down.
- Early warning on degrading power hardware
- Replace on a schedule instead of during an outage
- One deployment serving both teams
Early-warning capability is being validated with design partners on production hardware.
THREE PEOPLE IT IS BUILT FOR
Same deployment. Three jobs done.
Attacks beneath EDR don't write logs. I need evidence, not a guess.Physical evidence in 20 ms.
Ten thousand alerts a day. I need the three that matter.Findings, not firehose.
Not one dollar of new hardware.Nothing installed to start. No new silicon.
WHO IS IN CONTROL
The power layer answers to you. Not to a vendor.
You cannot audit a component by asking it how it is doing.
Every server in your estate contains a management controller running firmware you did not write and cannot inspect. It has authority over the physical power of the machine. PWX gives you an independent view of what that layer is actually doing, and a switch that belongs to you.
Firmware you did not write, from a supply chain you did not choose
Every controller ships with code authored under someone else's jurisdiction
Independent of vendor firmware
We observe the power layer rather than trusting what it reports about itself
Your data stays where you put it
Runs fully inside your environment, including disconnected networks
Machine telemetry only
No workload content, no customer data, ever
Your switch, your authority
Enforcement acts under policy you set and can revoke
Designed for defence, government and national infrastructure environments.
On sovereignty and enforcement leverage · Stefan Fritz →
ECOSYSTEM INTEGRATIONS
SplunkMicrosoft SentinelDatadogServiceNow
Findings delivered into the tools you already run, see the live Datadog stream on Proof.
AUDIT & COMPLIANCE
Evidence for the frameworks you answer to.
The power layer is inside the scope of the major OT and infrastructure frameworks, and today it is the part of the estate with the least evidence behind it. PWX is designed to produce that evidence, on demand.
| FRAMEWORK | OBLIGATION AREA | WHAT PWX PRODUCES |
|---|---|---|
| NIS2EU 2022/2555 · ART. 21 | Risk-management measures: asset visibility, incident detection and handling, evidence for reporting | Continuous inventory of the power layer; detection with a physical evidence trail; an incident record that survives the incident |
| IEC 62443INDUSTRIAL AUTOMATION & CONTROL | Continuous monitoring and asset inventory of control systems | Per-controller monitoring against a baseline learned from your own hardware; evidence packs on demand |
| NERC CIPBULK ELECTRIC SYSTEM | System security management and internal network security monitoring for cyber systems | Behavioural monitoring of the management plane; alerting into your existing tools; retained records under your control |
PWX PRODUCES EVIDENCE. COMPLIANCE ITSELF REMAINS AN ASSESSMENT OF YOUR WHOLE ENVIRONMENT · NO SINGLE PRODUCT MAKES YOU COMPLIANT, AND WE DO NOT CLAIM OTHERWISE.