Who Verifies That the Recovery Can Be Trusted?
In an ordinary incident, no independent party fulfills this role. Standard incident response teams focus on threat containment and technical server restoration, leaving a critical gap in verifying whether restored financial and operational data is safe to run the business. Rushing to reconnect without independent validation risks secondary data corruption, audit failure, and unexpected operational halts.
Ownerstone provides the Board, CFO, and General Counsel with immediate, independent verification: whether the recovery plan is credible, whether the SAP landscape is transactionally sound, and whether reconnection can proceed safely. The same unfiltered view extends to the security posture itself: how exposed the business is in dollar terms, whether the integrators and hosting providers it depends on are managed as risks, and whether its insurance will respond.
Cyber work is led by Dr. Alexander Miranda, Cyber Risk Advisor, with a direct line to the principals from the first call.
The Method Is the Same. Here Is What Changes.
The five phases of Board-led recovery apply whether the cause of distress is a failing program or an attack. Each phase below notes what Ownerstone does when it is the latter. The full method is on the home page.
The incident-response firm contains; we make sure no restart is committed before the Board has seen the restoration plan.
Restoration-integrity assessment of the recovered landscape and of the transactions processed by hand during the outage.
A recovery and close timeline the CFO can defend to auditors, counsel, and lenders.
The incumbent rebuilds; we validate each restoration gate independently.
Post-incident resilience review, and the security gate any in-flight program must now pass.
Three Ways to Engage
From the first call: the Owner’s response stood up, evidence preserved, the responder selected and overseen, every restoration gate verified before reconnection, and Board decision rights preserved throughout.
Exposure quantified in dollars, regulatory and framework assessment, third-party risk across integrators and hosting providers, response readiness, fractional CISO and Board reporting, and insurance readiness and claims support.
For live landscapes: confirms that a clean, isolated restore of SAP exists and has been rehearsed before a security event occurs. The security gate any in-flight program must now pass.
Cyber Events That Stopped the Business · 2019–2025
Twelve incidents where a cyber event halted ERP-dependent operations. The failure modes are the ones Ownerstone already diagnoses: talent diverted from a rollout, a transformation paused, a quarterly report postponed, receivables that could not be invoiced.
Five-week global production shutdown. Quarterly loss before tax of £485M against a £398M profit a year earlier; revenue down 24%. No cyber insurance in force. UK government £1.5bn loan guarantee.
Online sales offline for roughly six weeks. £101.6M exceptional costs; £100M insurance receipts expected over about eighteen months.
Swing from £45M profit to £126M loss; 6.5M member records compromised.
$65M–$75M pre-tax impact. July spent catching up on purchase orders, invoicing, and payments processed by hand during the outage.
Results publication suspended; paper and fax ordering continued into early 2026. Net profit forecast cut by ¥47.5bn.
Net sales fell 20% in the quarter after five weeks of manual order-taking. The $580M ERP transformation paused for more than a year. $380M suit filed against Cognizant, July 2025.
Inability to invoice and collect receivables. The SAP S/4 rollout was delayed three to six months at $20M–$30M additional cost because IT was diverted to recovery and manual transactions had to be re-keyed.
“The entirety of the Debtors’ accounting and financial systems were hacked and encrypted.” The resulting failure to meet lender reporting requirements was cited as necessitating the filing.
MKS delayed its earnings release; Applied Materials disclosed a $250M knock-on from the supplier outage. Consumer class action followed.
About three weeks of supply-chain disruption; $20.5M insurance reimbursement later disclosed.
170 plants on pen and paper; complete Q1 report postponed about five weeks. NOK 220M insurance recognized by year-end. Ransom not paid.
Q4 earnings release delayed. $23M remediation against $4M revenue impact: the rare case where IT cost exceeded lost sales.
A note on attribution. Most companies never name their ERP vendor in a cyber disclosure. Each card above states plainly whether SAP was named by the company, identified only by third parties, or not identified at all. We list them because the failure mode, not the logo on the encrypted server, is what a Board needs to see. Figures are as disclosed in the sources cited; no per-day “cost of an SAP outage” statistic exists from a credible source, and we do not publish one.