The Achilles Working Group is a collaborative body of security researchers, software vendors, and industry experts that develops and maintains a shared, machine-readable vulnerability database for industrial control systems (ICS) and operational technology (OT). It was founded in 2013 to address the lack of standardized vulnerability information for critical infrastructure, and its primary output is the Achilles Communication Protocol (ACP) and the Achilles Vulnerability Database (AVD), which are used by asset owners and vendors to identify and remediate cyber risks in industrial environments.
Background and Origins
The group emerged from a real-world problem: traditional IT vulnerability databases like the National Vulnerability Database (NVD) were not well suited to ICS/OT. Industrial protocols (Modbus, DNP3, OPC, etc.) and embedded devices behave differently from enterprise IT systems, and a vulnerability that is critical in IT might be merely annoying in OT, or vice versa. The Achilles Working Group was formed by a consortium of companies—including major automation vendors and security firms—to create a dedicated, vendor-neutral repository. The name “Achilles” references the Greek hero’s one weak spot, symbolizing the goal of finding and hardening the single point of failure in industrial networks.
How the Database Works
The Achilles Vulnerability Database is not a public, freely searchable list like the NVD. It operates on a membership model. Vendors submit vulnerability reports to the group, which then validates, scores, and publishes them to members. The scoring uses a custom system that considers the specific protocol, the device’s role, and the potential impact on physical processes—not just the standard CVSS base score. For example, a buffer overflow in a protocol parser that is remotely exploitable without authentication would be rated higher than a local privilege escalation that requires physical access. Members access the database through a secure portal and receive alerts when new vulnerabilities affect their deployed devices.
Membership and Access
There are two main tiers of membership:
- Vendor members—automation and control system manufacturers who submit their own vulnerabilities and get early access to others’ data. They are expected to provide patches or mitigations.
- Asset owner members—industrial companies (energy, water, manufacturing) that use the database to prioritize their patching and risk management efforts. They do not submit vulnerabilities but can search the database and set up alerts.
Membership is paid, and pricing is not publicly listed—interested organizations must contact the group directly. The group also publishes occasional public summaries and white papers, but the full database is reserved for members.
Relationship to Other Standards
The Achilles Working Group does not operate in isolation. It aligns its vulnerability scoring with the ISA/IEC 62443 series of standards (which cover industrial automation and control systems security) and coordinates with ICS-CERT (now CISA’s ICS division) in the United States. When a vulnerability is published in the AVD, the group typically shares a sanitized version with CISA so it can be added to the public ICS advisories. This dual-track approach means that even non-members eventually hear about the most critical issues, but members get the technical details and affected product lists weeks or months earlier.
Common Misconceptions
A frequent misunderstanding is that the Achilles Working Group is the same as the “Achilles Test” or “Achilles Certification” offered by GE Digital (formerly Wurldtech). Those are separate commercial products—a hardware-in-the-loop testing platform that assesses the robustness of a device against network attacks. The Working Group is a non-profit industry consortium, not a testing lab. Another misconception is that the database is free or open to the public; it is not. Finally, some assume it only covers Achilles-branded protocols, but the name is historical—the database covers all common ICS protocols and many proprietary ones.
How to Choose Whether to Join
For an asset owner, the decision hinges on your risk posture and budget. If you operate critical infrastructure with legacy devices that are rarely patched, the early warning and detailed technical data can be invaluable. Consider these factors:
- How many distinct ICS/OT vendors do you have? More vendors means more vulnerability data to track.
- Do you have a dedicated OT security team that can act on the alerts? If not, the data may sit unused.
- Is your industry regulated (e.g., NERC CIP for power, TSA directives for pipelines)? Those regulations often require awareness of known vulnerabilities.
- What is your current vulnerability management process? If you rely solely on CISA advisories, membership gives you a head start.
For vendors, membership is almost mandatory if you want to be seen as security-conscious in the industrial market, because asset owners often check the AVD before purchasing.
Limitations and Criticisms
The Achilles Working Group is not without its detractors. Some security researchers have criticized the closed nature of the database, arguing that vulnerability information should be public to pressure vendors to fix issues. Others note that the membership fee can be prohibitive for smaller asset owners, creating a two-tier system where only large companies get the best data. There is also the inherent limitation that the database only contains what vendors and researchers submit—if a researcher discovers a bug and does not report it to the group, it will not appear. Finally, the scoring system, while tailored to OT, is still subjective and has been accused of underrating certain attack chains that combine multiple low-severity issues.
Frequently Asked Questions
Is the Achilles Vulnerability Database free? No, it requires a paid membership. There is no public search interface, and even the list of affected products is only available to members.
Does joining the Achilles Working Group guarantee my devices are secure? No. It provides information about known vulnerabilities, but you still need to apply patches, configure firewalls, and monitor your network. The group does not test or certify devices.
Can I submit a vulnerability I found in an ICS device? Yes, if you are a member (vendor or asset owner). The group accepts submissions from any member, though they prefer coordinated disclosure with the vendor.
How often is the database updated? Updates are continuous, but there is no fixed schedule. The group publishes new vulnerabilities as they are validated, which can be several per week during active research periods.
Is the Achilles Working Group affiliated with the Greek hero Achilles? Only in name. It is a modern cybersecurity consortium, and the name is a metaphor for finding the weak point in industrial systems, not a reference to ancient mythology.
Alternatives and Complementary Tools
If you cannot afford membership or want broader coverage, consider these alternatives:
- CISA’s ICS advisories (free, public, but less detailed and delayed).
- The MITRE CVE list with the ICS-CERT filter (free, but not OT-specific scoring).
- Vendor-specific security advisories from Siemens, Schneider Electric, Rockwell, etc.
- Commercial threat intelligence feeds from firms like Dragos or Mandiant that include OT-specific data.
In practice, many large asset owners use the Achilles database alongside these public sources, treating it as a premium early-warning system rather than a replacement.
Related
- Hestia Myth Interpretation: Goddess of the Hearth
- Hestia New York NY: Greek Goddess in the Big Apple
- Dionysus Park Door Code: Full Guide
How pages are sourced and corrected: Sources and editorial policy.