Strategic PartnersIssue 033 records
NetApp
NetApp's AI Data Engine reached general availability: release 1.3, dated October 26 and documented on October 30, is NetApp's first GA AIDE release. It ships metadata cataloging, cleanup of stale and duplicate data, retention actions, and MCP access for named AI clients scoped by Entra ID. Analysts in March had expected GA months earlier. AIDE's requirements show it needs an internet connection to AWS-hosted endpoints, NetApp Console sign-in, usage metrics sent to NetApp, and a link to the Console agent. NetApp's October 30 Brotli advisory lists Console Agent containers as affected or under investigation, with no fix. CISA has listed this flaw as actively exploited. For SLED, network egress approval and Console agent patching come before any AI benefit. No new SLED deployment evidence was found.
- Evidence records
- 3
- Cross-source patterns
- 1
- Evidence classes
- 3 vendor claim
- Outcomes
- 2 cautionary1 emerging
- Source freshness
- 3 new this fortnight
- Research completed
- 2026-11-02
Choose a role to see its takeaway beside every record in the ledger.
Patterns across the evidence
Synthesis · Lighthouse Advisory interpretation
AIDE reaching GA puts the Console agent and cloud egress, not AI features, on the critical path for SLED pilots
NetApp declared AI Data Engine 1.3 generally available on 26 October, months after the GA timing analysts reported in March. Its requirements page shows an online installation that depends on AWS-hosted registries, NetApp Console SaaS identity, usage-metrics endpoints and a bidirectional link to the Console agent. NetApp's Brotli advisory, updated 10/30, lists Console Agent containers as affected or under investigation for a flaw CISA has added to KEV, with no fix listed, while AIDE itself is listed as not affected. For SLED evaluators the gating work is egress approval and Console agent patch posture before any AIDE scan begins.
Operating questionCan the security office approve AIDE's outbound endpoints and telemetry, and is every Console agent inventoried with compensating controls until NetApp lists a fixed build?
Supporting evidenceNetApp declares AI Data Engine 1.3 its first generally available release, with metadata cataloging, lifecycle actions and governed MCP accessNetApp AI Data Engine requirements: online installation depends on AWS-hosted registries, NetApp Console SaaS authentication and usage-metrics endpointsNetApp (Product Security)
Evidence ledger
Full record · every source keeps its link and limitations
NetApp declares AI Data Engine 1.3 its first generally available release, with metadata cataloging, lifecycle actions and governed MCP access
NetApp's AI Data Engine (AIDE) documentation states that version 1.3, dated 26 October 2026, is the first generally available release. AIDE is described as a metadata intelligence service managed through NetApp Console. It scans connected file shares, database servers and StorageGRID systems into a metadata catalog. It flags cold, stale and duplicate data, open-permission directories and oversized or unused database tables. It can copy or archive files to NFS or SMB targets, tag them or permanently delete them, and save filters as monitored policies. It offers governed MCP access for Claude Code, Claude Desktop, Cursor and OpenCode, with Microsoft Entra ID scopes per collection. The 1.3 notes do not mention vectorization, semantic enrichment, Data Curator or Data Guardrails, which StorageMath, HyperFRAME and Futurum described as part of the earlier AIDE positioning.
Why it matters, evidence and limitations
- Why it matters
- SLED institutions with large unstructured file estates, such as county file servers, university research shares and district home directories, can now evaluate AIDE as a supported product rather than an early-access program. The functions that ship are data hygiene and governance: finding stale and duplicate data, open permissions and retention-driven deletion. These map to records-retention and storage-cost work more directly than to generative AI. There is no SLED deployment evidence yet.
- Evidence and measured results
- Vendor release notes only. Timeline context from independent analysts: Futurum (March 2026) reported management expected GA in Q4 FY2026, and HyperFRAME (19 March 2026) reported broader rollout expected in early summer. GA landed on 26 October, months later than both. The companion deployment overview (10/23/2026) gives sizing baselines of up to about 3 billion files single-node and 6 billion multi-node, which NetApp calls recommended baselines rather than hard limits. No benchmarks, customer counts or accuracy measures are given.
- Limitations and uncertainty
- Vendor-authored. GA status does not establish production scale, accuracy or cost outcomes. The 1.3 feature list is narrower than the 2025 announcement, and this run did not confirm whether the missing features are deferred or dropped. Known limitations were covered in our 2026-10-29 edition. This GA notice is a first-time source; it was updated 10/30 and is not in the archive.
NetApp AI Data Engine requirements: online installation depends on AWS-hosted registries, NetApp Console SaaS authentication and usage-metrics endpoints
NetApp's AIDE requirements page (updated 10/29/2026) says an online installation must reach a list of outbound endpoints. They include NetApp's container registry and S3 and STS endpoints in AWS us-west-2, NetApp Console registration and authentication (api.bluexp.netapp.com, netapp-cloud-account.auth0.com), a logs and metrics streaming endpoint, and AWS Cognito in us-east-1 for sending product usage metrics to NetApp. Runtime downloads come from GitHub, get.k3s.io and Docker endpoints, and installer scripts from a CloudFront host. login.microsoftonline.com is needed only for governed MCP access. The endpoints are the same through a proxy. The network table requires bidirectional Console agent to AIDE traffic on ports 80, 443, 8080 and 9000, and inbound 443 for AI clients to the MCP server. Active Directory DNS used by AIDE nodes must also resolve external names.
Why it matters, evidence and limitations
- Why it matters
- This is the practical gate for SLED adoption of AIDE. Agencies with CJIS, HIPAA, FERPA or state data-residency rules, and campuses with segmented research networks, will need security review of outbound connections to SaaS and AWS endpoints and of usage-metrics transmission. Air-gapped public-safety or utility environments may not fit an online installation. This run found no AIDE offline procedure.
- Evidence and measured results
- Vendor requirements documentation listing endpoints, purposes, initiating components and ports. No independent validation. The page describes an online installation and this run did not find an offline or dark-site AIDE procedure in the pages opened. NetApp Console separately documents private-mode releases (latest 4.10.0, 17 September 2026), but this run did not establish whether AIDE supports private mode.
- Limitations and uncertainty
- Vendor documentation that may change. Absence of an offline procedure in the pages opened is not proof that none exists. Telemetry content and retention are not described here. First-time source, not in the archive; included now because GA (26 October) makes these requirements the evaluation gate.
NetApp advisory NTAP-20261023-0001 (v8.0): actively exploited Brotli flaw affects Console Agent containers and ONTAP Select Deploy; no fixes listed; AIDE and ONTAP 9 not affected
NetApp's advisory for CVE-2026-111497, a Google Brotli decoder flaw that NetApp says is also known as Node2Shell or HTTP2Shell and scores CRITICAL 9.2, was at version 8.0 on 10/30/2026 with status Interim. Listed as affected: NetApp Console Agent Container (audit), Console Agent Container (e-series) and the ONTAP Select Deploy administration utility. Under investigation: the Console Agent OVA, eleven other Console Agent containers, Data Classification, SolidFire/HCI, XCP and others. Version 8.0 moved six Console Agent containers into that status. ONTAP 9, AI Data Engine, the AIDE MCP Server and the AIDE LangChain Retriever are listed as not affected. The remediation tab lists no patches and no workarounds. Independently, CISA added CVE-2026-111497 to its Known Exploited Vulnerabilities catalog on October 27 based on evidence of active exploitation.
Why it matters, evidence and limitations
- Why it matters
- SLED teams running NetApp Console agents, which Console documentation ties to Cloud Volumes ONTAP deployments and the AIDE requirements tie to AIDE, now have a KEV-listed flaw in components with no NetApp fix listed. State and local agencies that follow CISA KEV prioritization, and universities with similar policies, will need compensating controls and tracking for these components even though ONTAP 9 itself is not affected.
- Evidence and measured results
- Vendor advisory with product status lists and revision history (1.0 on 10/23 through 8.0 on 10/30). Independent corroboration of exploitation comes from CISA's 10/27 KEV alert and the Canadian Centre for Cyber Security alert AL26-027 (10/28), neither of which mentions NetApp. NetApp's Console what's-new page lists no Console agent release after 4.11.0 (16 September). Its 15 October entry did not render.
- Limitations and uncertainty
- Vendor-authored and Interim; the advisory went through eight versions in a week. NetApp gives no NetApp-specific exploitation evidence. CISA and CCCS describe Brotli generally. The page is JavaScript-rendered. First-time source, not in the archive. The 10-30 edition covered the separate PHP2SHELL and MySQL advisories.
How to read this edition
Source findings, measured results and limitations come from the cited publications. Patterns, operating questions, role takeaways and implementation considerations are Lighthouse Advisory interpretation, stated as questions to validate locally rather than guaranteed outcomes. Vendor and operator claims are labeled as claims. Full research method.
- Vendor claim
- A supplier-provided assertion that has not been upgraded to independent evidence.