Boston Scientific was pursuing partial shipping restoration on August 30, while electronically submitted orders waited for fulfillment and an investigation with outside cybersecurity experts continued.
Boston Scientific said in its August 30 evening update that it was working toward restoring shipments of some products that week after a cyber incident disrupted certain on-premises operating systems and business applications. Electronic orders were still being accepted and queued for later fulfillment. Company update.
The company reported no indication of related unauthorized activity since August 25 and said cloud systems were unaffected. CrowdStrike and other specialists were assisting the investigation. Full ordering and shipping capacity depended on demonstrated restoration. The update did not establish complete recovery or identify an actor or entry method. August 30 statement.
Accepting an order does not establish that it can reach fulfillment. For organizations reviewing their own readiness, Layer8’s Resonance Monitoring can connect agreed service checks and vendor telemetry with dependencies, alert routing and responsible owners.
A proposed engagement would map the agreed order-to-fulfillment functions, assign an owner to each dependency and define which interruptions need escalation. Teams would distinguish a healthy application from a usable business service, with checks covering the agreed functions that customers and staff actually need and their documented success criteria. That could reduce delays caused by unclear ownership while keeping recovery decisions tied to observable service results.
Acceptance would require an agreed exercise showing a service problem reaching the right owner, escalation working when that person is unavailable, and the selected fulfillment function completing after restoration. Staffed hours and remediation authority would be explicit in the service schedule.