1.10 · Lack of data access logs

Explore 1 source-supported AI security cases for 1.10 · Lack of data access logs in Databricks DASF 3.0, with evidence, scope, and defensive analysis.

Risk category

Data access is not logged or audited sufficiently to show who used which data and how. The organization may consequently overlook unauthorized access or misuse and lack the evidence needed for investigations and compliance. Effective auditing requires both usable access records and an accountable process for reviewing them.

Official framework source ↗ · Open interactive explorer ↗

Incident · · Practical overlap

Zeabur October Breach: AI Credentials Exposed Across Cloud and Cluster Boundaries

Zeabur, a platform for hosting applications and databases, reported an October 14-15 intrusion affecting hosted AI-service credentials. Attackers used leaked internal credentials across cluster and cloud boundaries; a replacement credential was captured in a later backup and subsequently used without authorization. Customers own upstream-key revocation and recovery of deployments they administer; the operator owns internal isolation and backup access.

Why it relates: Regional gaps in service-secret read evidence limit reconstruction of unauthorized access affecting AI credentials. The incomplete records concern hosting and credential access, not an established ML dataset-access log.

October operational incident only. Shared mechanisms and AI-hosting layers can justify bounded practical overlap; no inference that an agent, MCP server or particular LLM was deployed. Same-author second pass, not independent validation.

AIA · Read the full case ↗ · SecureFlow · Read the full case ↗