In an incident an agent can read every alarm and find the cause in seconds. TraceMem lets it, holds any change to a live system for the engineer on call, makes the change itself so the agent never holds a credential, and keeps the record your incident report starts from.
Or call us on +1 650 550 1418
Northern ring · Regional NOC
Reroute proposed via Harbour and Westbury
Span lost between Mill Road and RiversideT+00:00
312 alarms from five exchanges in forty seconds.
Agent reads alarms, topology and open ticketsT+00:12
Every read goes through a published capability, for the engineer on call.
312 alarms, one causeT+00:31
A fibre cut on the Mill Road to Riverside span. Nothing else is wrong.
Reroute proposed via Harbour and WestburyT+00:48
A change to the live network, so it waits for Nadia Kerr, on call, in Microsoft Teams.
Held for Nadia Kerr
Approved by Nadia Kerr. Traffic reroutedT+02:10
TraceMem made the change through the orchestrator. The agent never held its credential.
Early warning drafted from the recordT+02:14
What happened, what changed and who allowed it, for the national authority.
Illustrative incident. The operator, exchanges, counts, names and times are made up.
Each agent holds only the capabilities someone published for it, and no credential of its own. Pick an agent to see what it can read, what it has to ask an engineer for, and what it will never do.
Credentials held by noc-agent: none. TraceMem makes every call through the capability, so there is no key to leak.
Illustrative capabilities. Yours are the ones you publish.
Governed Data AccessSome of these already apply and some are still coming. Most of them ask for an incident report within hours, naming what changed and who allowed it, and only a record kept at the time can answer that fast.
Dates checked against each regulator’s own publication, September 2026. Not legal advice.
None of these involved an AI agent. Each is a regulator's or a national CERT's finding, and each came down to a change nobody reviewed, a credential that opened too much, or automation nobody had planned around.
A misconfigured network element took the mobile network down, with full service restored only after at least 12 hours. More than 25,000 calls to 911 were blocked.
What it came down to
A change to the core network with no peer review, inadequate testing and too few controls on changes.
For an agent, with TraceMem
Every change an agent proposes to a live system waits for an engineer with change authority, and is on the record before it is reported done.
Policy and Exceptions29 Dec 2025 · CERT Polska report, 2026
No MFA at any affected site
Attackers reached wind and solar sites through internet-facing VPNs, damaged controller firmware and ran a wiper. Generation was not interrupted.
What it came down to
Internet-facing VPNs that accepted logins without multi-factor authentication, and devices left on default credentials.
For an agent, with TraceMem
Agents hold no credentials of their own. TraceMem makes every call, for an engineer verified by your own directory.
Governed Data Access9 Aug 2019 · Ofgem report, 2020
£10.5 million paid
After a lightning strike, offshore turbine controllers reacted incorrectly and an automated control system shut down a unit at a gas-fired station. 1.15 million customers lost power.
What it came down to
Automated control behaviour that had been flagged in modelling but never discussed with the system operator.
For an agent, with TraceMem
What every automated action did, under which rule and for whom, is on one record your engineers and your regulator can both read.
Decision TraceAfter the ransomware attack, the regulator found the operator had not planned well enough for shutting down and restarting the pipeline by hand.
What it came down to
No adequate plan for running operations manually when the systems were down.
For an agent, with TraceMem
TraceMem fails closed: if it cannot be reached, agents stop and your people carry on, so the manual plan you already have is the plan.
Policy and ExceptionsPut in your own numbers. What your agents read and changed before a governed path is in place can never be recorded afterwards.
21 working days a month. Your numbers stay in your browser.
In 6 months of waiting
100,800
Agent actions with no record of which engineer they worked for, what they changed or who allowed it.
Pick whichever is quickest for you. However you get in touch, a person replies. With our forward-deployed engineers, TraceMem can be running inside your network in days.
Talk to us now
45days, free
Free for 45 days on our Docker-based trial image, inside your own network. When you are ready, it upgrades to the full enterprise product.
Forward-deployed engineers, ours or our partners', can set it up in days and help you define policies and integrations. This may be charged separately.