How is an automation incident different from a cyberattack?
An automation incident is a control system failure whose root cause is engineering (sensors, actuators, control logic, calibration, or setpoints), not an attacker on the network. A cyberattack is unauthorized activity through networks, credentials, or malware. Most control system harm comes from the former, and is routinely misread as equipment failure.
Why do organizations miss these incidents?
Automation incidents rarely look like incidents. They show up as equipment failures, unexplained downtime, recurring process problems, or root-cause findings that never quite close. Operators see that something is wrong but aren't trained to classify it, and security teams know networks, not normal process behavior.
Should we start with the Workshop or the Annual Service?
Start with the Incident Identification Workshop if you want a lower-commitment way to test the ACS approach. The same Workshop is the onboarding component of the Annual Service, which then keeps you current all year. If you're not sure, a 20-minute Incident Review will tell you which fits, or whether neither does.
How much does the Annual Service cost?
Pricing is based on the size of your organization. Request an Incident Review for a quote. The Annual Service begins with the Incident Identification Workshop, then adds the ACS annual incident report, comparison with your sector and geography, significant-event notifications, periodic reviews, and year-round availability by phone, email, and video.
Does ACS replace our cybersecurity team?
No. ACS makes your engineering and security teams better at recognizing the automation incidents that network monitoring misses. It complements your cybersecurity program; it doesn't replace it.
Is incident data shared confidentially and non-punitively?
Yes. ACS turns what it learns into trusted, non-punitive information sharing that helps the whole sector improve, without exposing the organizations involved.