Notifications
Clear all
Topic starter
18/08/2026 2:34 pm
TL;DR: A single ChatGPT prompt retrieved more than 400 internal files in 42 milliseconds because OAuth access and server-to-server API calls bypassed human-centred security controls, according to Seclore. The real failure is not AI access itself but the lack of persistent data context, classification, and rights management around what that access can reach.
NHIMG editorial — based on content published by Seclore: ChatGPT Read 400 Internal Company Files in 42 Milliseconds
Questions worth separating out
Q: What breaks when AI systems inherit broad repository access?
A: Broad inherited access lets AI systems reach data that was never intended for machine-scale retrieval, including stale, duplicated, or sensitive content.
Q: Why do AI agents complicate traditional IAM controls?
A: AI agents complicate traditional IAM controls because they do not behave like human users with short, predictable sessions.
Q: How do security teams know if an AI integration has become overtrusted?
A: Look for connectors, MCP servers, and vendor accounts that can reach production data, change configurations, or run actions without a separate approval step.
Practitioner guidance
- Inventory AI-connected OAuth integrations Map every AI connector that can read enterprise storage, including delegated scopes, token lifetimes, and the data domains it can enumerate.
- Classify data before AI access is approved Apply sensitivity labels and purpose-based policy to documents before granting AI backends any retrieval path.
- Monitor service-to-service retrieval patterns Build detections for unusual API volume, parallel file enumeration, and cloud IP access that bypasses browser telemetry.
What's in the full article
Seclore's full post covers the operational detail this post intentionally leaves for the source:
- How the Semantic Triad classifies content using content, context, and intent at the document level
- How AI DLP and EDRM apply persistent controls after a file leaves its source repository
- How the audit trail captures which integration touched which files, from which IP, and when
- How sensitive values can be masked before they reach an AI processing layer
👉 Read Seclore's analysis of ChatGPT retrieving 400 internal files in 42 milliseconds →
AI drive enumeration: is your data context keeping up?
Explore further
18/08/2026 3:20 pm
Data context has become the missing control plane for AI integrations. Authentication alone no longer tells practitioners whether an AI backend should see a file, a folder, or an entire workspace. Content classification, regulatory context, and intent-based policy must work together, because machine-speed retrieval collapses the review window that traditional approval models assume. The practitioner conclusion is simple: if context does not travel with the data, access control is incomplete.
A question worth separating out:
Q: Who is accountable when an AI agent accesses regulated data improperly?
A: Accountability sits with the teams that govern the agent's identity, the data classification, and the policy that allowed the access path. If those controls are disconnected, no single owner can explain why the access existed or why it was not removed sooner. Shared context is what makes accountability traceable.
👉 Read our full editorial: AI drive enumeration exposes the gap in data context controls
