Secure Autonomous
FeedbackGet alertsCheck a deployment
Controls › C-A3

Provenance of the actor's software and hardware

The origin of the code and components that sense, decide, and connect is documented, and no party able to compel access or control sits in that chain.

Actor layerMissing or failed in 1 case (0 ended in harm)Worked in 0Machines: 1

Where it was missing or failed

The third column is what this control would have looked like in that case: the concrete form, not the abstract name.

CaseWorldWhat it would have looked like hereStatusOutcome
Triton 2017MachinesIntegrity of the safety controller's code: the malware modified the controller's in-memory firmware to add programming; the US Federal Bureau of Investigation (FBI) says Schneider Electric addressed the vulnerability, in Tricon model 3008 versions 10.0 to 10.4, with version 11.3 of the controller, released in June 2018absentStopped by the operator's control

Rules and standards that map to it

Strength says whether the rule's text requires this control, implies it, or only recommends it. Draft mappings are the Register's reading, not yet checked by a person, and none is legal advice.

RuleStrengthWhere, and whyJurisdiction
Connected vehicles rule: vehicle connectivity systems and automated driving systems with a China or Russia nexus (15 CFR part 791, subpart D) (draft mapping)Required by the text§§ 791.302–791.304: prohibited hardware, covered software (vehicle connectivity and automated driving system software), and manufacturer transactions with a China or Russia nexusUnited States
FCC Covered List: foreign-produced uncrewed aircraft systems and critical components, and DJI and Autel equipment (Secure and Trusted Communications Networks Act; FY2025 NDAA § 1709) (draft mapping)Required by the textthe national security determination of December 21, 2025: equipment authorization is denied by country of production and by named producer, including critical components such as flight controllers and data linksUnited States
NERC Critical Infrastructure Protection standards (CIP-005, CIP-007, CIP-013, CIP-015), approved by FERC (draft mapping)Required by the textCIP-013: supply chain risk management plans covering vendor products, including verification of software integrity and authenticityUnited States (bulk electric system)
NIST AI 600-1: Generative AI Profile of the AI Risk Management Framework (draft mapping)Recommendedvalue chain and component integration: provenance of third-party models, data, and componentsUnited States (voluntary)
Careful Adoption of Agentic Artificial Intelligence (AI) Services (ASD's ACSC, CISA, NSA, Canadian Centre for Cyber Security, NCSC-NZ and NCSC-UK joint guidance, 1 May 2026) (draft mapping)RecommendedDeveloping secure agents, Manage third-party components (p. 18): 'Restrict tool use to an approved allow list of tools and versions that are regularly verified as secure'.United States (voluntary), jointly with Australia, Canada, New Zealand and the United Kingdom

Recent signals touching this control

DateSignalKind
2026-10-16CVE-2026-88755: Z.ai ZCode connects to repository-declared MCP servers
The National Vulnerability Database (NVD) records that Z.ai ZCode v3.11.2.6792 automatically connects to Model Context Protocol (MCP) servers declared in a repository's workspace configuration, which the record says may let an attacker execute arbitrary code when a crafted repository is opened. Source ↗
vulnerability
2026-02-19GHSA-9ppg-jx86-fqw7: unauthorized npm release of cline@2.3.0
The maintainers' advisory says someone without authorization used a compromised npm publish token to release cline@2.3.0 on 17 February 2026 with an added install step that globally installed another package, openclaw; version 2.4.0 replaced it about eight hours later and the token was revoked. Source ↗
disclosure

All signals for this control.

Deploying something? Check a deployment ranks every control against the cases that match your profile. Patterns shows where this control fails across worlds.

Help shape the Register

A person reads every answer; changes it leads to are logged in the methodology. To dispute a claim or reply for a named company, use Respond, dispute, or submit.

Did this page help with what you came to do?