An established security process, but AI policy and AI office in name only
Overall rating “solid”. No deduction for controversies. The superscript numbers link directly to the source.
1 · Responsibility
Arm documents a general risk and control structure, but for AI there are only principles, with no published policy, no AI responsibility at board level and no figures.
What is documented
- According to its charter, the Audit Committee is responsible for data protection, technology and information security and whistleblowing procedures1
- A management Risk Review Committee reports quarterly; the board discusses the use of AI within Arm2
- The Raise a Concern Helpline is available around the clock, also to people outside Arm; retaliation is prohibited3 6
- Employees receive annual ethics training and an AI e-learning course, without figures6
The case against
AI rules in name only
- The code of conduct refers to an unpublished AI Policy and an “AI Office” without a mandate or staffing3
- The policy on internal use of AI is named without content; the 2019 Trust Manifesto contains no implementation mechanisms6 7
- Neither the board nor its committees have a designated responsibility for AI4 5
Sources for Responsibility (9)
- Arm Holdings plc: Audit Committee Charter · 1 August 2023 · primary source
- Arm Holdings plc / SEC EDGAR (Form 6-K): Annual Report and Consolidated Financial Statements for the year ended 31 March 2026 · 31 March 2026 · primary source
- Arm Limited: Arm Code of Conduct FYE25 · 1 February 2025 · secondary source
- Arm Holdings plc: Governance – Overview & Documentation · 3 November 2026 · secondary source
- Arm Holdings plc / SEC EDGAR (Form 6-K): Notice to ADS Holders 2026 Annual General Meeting · 6 August 2026 · secondary source
- Arm: A Future Built on Arm: FYE25 Sustainable Business Report · 31 March 2025 · secondary source
- Arm: Arm AI Trust Manifesto · 6 November 2019 · secondary source
- Arm Newsroom (Mark Hambleton): Arm Metis: agentic AI security framework · 28 May 2026 · secondary source
- Arm Holdings plc / SEC EDGAR (Form 6-K): Results of 2026 Annual General Meeting · 9 September 2026 · primary source
2 · Safety
Arm documents a NIST-aligned security programme, a PSIRT with bug bounty and formal verification, but Mali driver flaws were exploited, and AI-specific testing is missing.
What is documented
- The 20-F describes a NIST-aligned programme with a CISO, annually tested contingency plans, external maturity assessments and Audit Committee oversight6
- The PSIRT acknowledges reports within two working days, is a CNA and publishes bulletins7
- A bug bounty programme with safe harbour covers Mali drivers and firmware8
- The Realm Management Monitor was formally verified; verification is built into the development pipeline, and a bug found was fixed1
- Arm commits to export, customs and sanctions law and has a trade compliance function14
The case against
Vulnerabilities in own systems
- Arm confirmed exploitation of CVE-2024-4610 in the Mali drivers; distribution of the fix depends on device makers9 10
- Further flaws affect the Mali drivers (CVE-2025-0072) and the circumvention of the Memory Tagging Extension (TikTag)11 12
- The group D1R claims a data theft from arm.com; there is no statement from Arm13
Sources for Safety (16)
- arXiv (Wu, Xiong, Manino, Stockwell, Cordeiro; Arm Centre of Excellence, University of Manchester): Verifying components of Arm Confidential Computing Architecture with ESBMC · 6 June 2024 · primary source
- Arm: Arm's Systematic Approach to Product Security · 3 November 2026 · secondary source
- Arm: Embedded Assurance and Certifications · 3 November 2026 · secondary source
- Arm: Zena Compute Subsystem – Accelerating Time to Market for Safe, AI-Ready Automotive SoC · 3 November 2026 · secondary source
- Arm Newsroom (Mark Hambleton): Arm Metis: agentic AI security framework · 28 May 2026 · secondary source
- Arm Holdings plc / SEC EDGAR: Form 20-F FY2026, XBRL report R33: Cybersecurity Risk Management and Strategy Disclosure (Item 16K) · 31 March 2026 · primary source
- Arm: Product Security Incident Response · 3 November 2026 · primary source
- Intigriti: Arm Bug Bounty Program – Detail · 1 June 2025 · primary source
- The Hacker News: Arm Warns of Actively Exploited Zero-Day Vulnerability in Mali GPU Drivers · 11 June 2024 · secondary source
- Cyber Security News: Arm Mali GPU Kernel Driver 0-Day Vulnerability Actively Exploited in the Wild · 3 February 2025 · secondary source
- cvelogic: CVE-2025-0072 – Mali GPU Kernel Driver allows improper GPU memory processing operations · 2 May 2025 · secondary source
- The Register: Arm Memory Tag Extensions leak (TikTag) · 18 June 2024 · secondary source
- DeXpose: D1R Ransomware Attack on ARM: Compromise of UK Tech Giant · 13 July 2026 · secondary source
- Arm Limited: Arm Code of Conduct FYE25 · 1 February 2025 · secondary source
- Arm Holdings plc / SEC EDGAR: Form 20-F for the fiscal year ended March 31, 2026 · 31 March 2026 · secondary source
- Tom's Hardware: Arm to sell its new AGI CPU in China · 1 April 2026 · secondary source
3 · Transparency
Arm discloses security flaws with CVE identifiers and documents the models in its AI Portal, but the AI Policy and the AI Office's mandate are not published, and there is no AI report.
What is documented
- Arm discloses security flaws through bulletins with CVE identifiers and publicly flagged the exploited Mali flaw1 3
- The 20-F describes cyber strategy and governance in concrete terms2
- For optimised third-party models in the AI Portal, origin, licence, evaluation, accuracy versus the base model and liability notices are documented5
- For TikTag, Arm named the affected processor cores6
The case against
AI governance not disclosed
Gaps on limitations and overview
- Limitations and failure modes of AI features in vehicle IP are not documented
- There is no overview of all models provided and their documentation status
Sources for Transparency (7)
- Arm: Product Security Incident Response · 3 November 2026 · primary source
- Arm Holdings plc / SEC EDGAR: Form 20-F FY2026, XBRL report R33: Cybersecurity Risk Management and Strategy Disclosure (Item 16K) · 31 March 2026 · primary source
- Cyber Security News: Arm Mali GPU Kernel Driver 0-Day Vulnerability Actively Exploited in the Wild · 3 February 2025 · secondary source
- Arm Limited: Arm Code of Conduct FYE25 · 1 February 2025 · secondary source
- Arm Developer (Arm AI Portal): YOLOv5s INT8 (XNNPACK, ExecuTorch) – Purpose of this Release · 3 November 2026 · primary source
- The Register: Arm Memory Tag Extensions leak (TikTag) · 18 June 2024 · secondary source
- Arm: A Future Built on Arm: FYE25 Sustainable Business Report · 31 March 2025 · secondary source
4 · Why the harm rule does not apply
The harm rule does not apply: there is no judgment, authority decision or fine concerning harm from AI; the exploited Mali flaw is a driver bug with no link to AI.
5 · Controversies (3)
- mediumArm confirmed exploitation in the wild of vulnerability CVE-2024-4610 in its own Mali GPU kernel drivers; the fix depends on device makers. · 11 June 2024 · unklar
- minorThe group D1R claimed to have stolen data from arm.com; there is no confirmation or statement from Arm. · 13 July 2026 · unklar
- minorWith TikTag, researchers showed that the Memory Tagging Extension of several Cortex cores can be circumvented; Arm confirmed the affected cores. · 18 June 2024 · unklar
6 · What remains open
- Responsibility for AI on the board or in executive management
- Content and implementation of the AI Policy and the AI Office's mandate
- End-use checks for the AGI CPU and AI IP
- Remediation status and distribution of the Mali driver fixes among device makers
- Confirmation or refutation of the group D1R's data theft claim
7 · How it was assessed
Cut-off date: 3 November 2026 · 42 searches, 36 fetches.
Primary documents read (9)
- Form 20-F FY2026 (S01, two retrievals up to Item 3.D) as well as XBRL reports R33 Cybersecurity (S02) and R27 Contingencies (S03), FilingSummary
- Form 20-F FY2025 (S05, Part 1)
- UK Annual Report and Consolidated Financial Statements FY2026 (S06, two retrievals)
- AGM 2026: Notice (S32) and Voting Results (S31)
- Sustainable Business Report FYE25 (S07)
- Code of Conduct FYE25 (S08) and website (S37)
- Audit Committee Charter (S09), governance page (S10)
- PSIRT page (S11), product security page (S12), bug bounty programme (S13), certifications page (S14), Zena CSS (S15)
- Model page Arm AI Portal (S18), Trust Manifesto 2019 (S19)
Research of 3 November 2026 under Globalance AI Footprint rulebook version 0