← All posts

Problem-Aware

249 posts on problem-aware.

Shadow AI Monitoring Tools: What to Measure and Where to Operate

Shadow AI monitoring tools observe employee AI usage that runs outside the IT-sanctioned stack. The category covers browser extensions that intercept ChatGPT and Claude sessions, CASB integrations that surface AI SaaS use, network telemetry that flags AI endpoints, and identity-aware proxies that route AI traffic through a policy point. Most tooling today produces visibility without enforcement. The architectural distinction that matters for compliance is whether the tool can block, redact, or modify AI traffic at the moment of the request, not just record it after the fact.

shadow-aimonitoringai-securitygovernanceenterprise-aienforcement
Read post →

Shadow AI Governance Framework: From Discovery to Enforcement

A shadow AI governance framework defines how an enterprise discovers, classifies, controls, audits, and reports on AI usage that runs outside the IT-sanctioned stack. The five layers map onto the EU AI Act Article 26 deployer obligations, the NIST AI RMF Govern function, and the ISO 42001 AI management system. Most organizations have policy and discovery covered. The control and audit layers are where the framework usually stops short of operational coverage. The piece walks through what each layer has to produce.

shadow-aigovernancecomplianceeu-ai-actnist-ai-rmfenterprise-ai
Read post →

Prevent Data Leaks to ChatGPT: The Inspection Point Your Endpoint Stack Lacks

Cloud Radix found 77% of employees using unauthorized AI tools paste sensitive business data into ChatGPT and similar models. The endpoint, network, and email stacks most enterprises run today were tuned for files and email and miss the JSON request body where the prompt actually lives. I walk through the inspection point that closes the gap, the four operations it performs on every prompt, and the audit record it produces for the compliance regimes the deployment is operating under in 2026.

shadow-aichatgptdata-protectionai-dlpai-securityenforcement
Read post →

Prompt Injection Defense in Depth: The Three Inspection Layers That Compose

Prompt injection defense in depth combines three inspection layers: request-path classification that flags suspicious instructions in the prompt, model-side safety training that resists injection during inference, and response-path inspection that catches successful injections in the model output. No single layer catches every attack. The combination produces stronger coverage than any layer in isolation. I walk through what each layer sees, where each one is blind, and how the audit record reconciles the decisions across layers.

prompt-injectionai-securitydefense-in-depthenforcementllm-securityowasp
Read post →

Agentic AI Enterprise Deployment: The Identity and Audit Surface That Has to Be in Place First

Agentic AI in enterprise environments adds an autonomy layer to the LLM stack that the rest of the controls were not designed for. Agents authenticate at the start of a session, but the actions they take across the session can run for hours, target many endpoints, and execute many tool calls. The identity, authorization, and audit surface that has to be in place before an agentic deployment goes to production is broader than the surface a non-agentic LLM deployment needs. I walk through the surface, where most deployments are exposed, and what the 2026 regulatory set expects from agentic AI in regulated environments.

agentic-aiai-securityenterpriseidentityauditenforcement
Read post →

The True Cost of a Shadow AI Breach: $670K On Top, 247 Days to Detect, 65% PII Exposure

The IBM Cost of Data Breach Report studied 600 breached organizations and found that one in five experienced breaches linked to shadow AI. Those incidents cost $670,000 more than standard breaches, exposed customer PII in 65% of cases, and took 247 days to detect. The numeric premium is the visible surface. The architectural reason behind it is identity correlation failure, classification blindness, and the absence of policy enforcement at the AI request layer.

shadow-aiai-securitydata-loss-preventionai-governancecybersecurity
Read post →

Shadow AI Detection Software: What the Category Should Actually Detect

Shadow AI detection software is converging into a category, with vendors marketing variants of network monitoring, browser-extension telemetry, and CASB pivots. The detection problem decomposes into four signals: traffic identification, identity correlation, prompt-level classification, and policy state. Software that produces the first signal without the other three solves discovery and leaves the enforcement gap open. I walk through what the four signals look like, why most current detection tools generate the first one only, and what the shift from detection to enforcement requires of the architecture.

shadow-aiai-securitydata-loss-preventionpolicy-enforcementai-governance
Read post →

Agentic AI in the Enterprise: Where the Action Surface Sits and How It Gets Controlled

Agentic AI in the enterprise introduces a new action surface: the LLM-driven agent that calls tools, queries databases, sends emails, files tickets, runs code, and triggers workflows on behalf of an authenticated user. The control problem is not whether the model behaves. The control problem is who authorized this specific action, against what data, under which policy, and with what audit record. I walk through what the enterprise action surface looks like in 2026, where the control points sit, and how the NIST three-pillar framework maps to the enterprise deployment.

agentic-aiai-securityidentity-and-authorizationinline-enforcementarchitecture
Read post →

AI System Prompt Leakage: What Leaks, How It Leaks, and Where to Stop It

System prompts carry the AI applications instructions, role assignments, tool definitions, retrieved context, and sometimes credentials or routing keys. A leaked system prompt exposes the application logic to an attacker, including the role boundaries, the tool catalog, and any sensitive context the prompt happened to include. The leakage modes are well-understood. The mitigations live at the AI request boundary, not inside the model. This piece walks through the leak surfaces, the demonstrated attack techniques, and the architectural pattern that prevents leakage.

system-promptprompt-injectionai-securitydata-leakageai-governanceowasp-llm
Read post →

Prompts Become Shells: What Microsoft''s May Disclosure Means for Any Enterprise Running LangChain, AutoGen, or Semantic Kernel

On May 7, 2026, Microsoft Security Research published a disclosure that walks through prompt-to-shell escalation paths in mainstream AI agent frameworks, including LangChain, AutoGen, and Semantic Kernel. The disclosure reframes agentic AI from a data-leak concern into a remote code execution attack surface. The reframing matters because the SOC playbook for an RCE class of vulnerability is different from the privacy playbook most security teams currently apply to AI traffic. This article walks through the disclosed escalation paths, identifies which framework patterns are exposed, and outlines the enforcement architecture that contains the blast radius before the prompt reaches the agent.

agentic-aircelangchainautogensemantic-kernelprompt-injection
Read post →

When the LLM Is the Attacker''s Hands: CVE-2026-39987 and the Case for Per-Decision Audit Logging

On May 10, 2026, The Hacker News documented an incident where attackers exploited CVE-2026-39987 in Marimo (≤0.20.4) to gain pre-auth RCE inside a victim AWS environment, harvested credentials, and then drove an LLM agent to operate AWS Secrets Manager on their behalf. The LLM was the post-exploitation tool. This article walks the attack path and explains why the per-decision audit log of LLM traffic just acquired forensic and regulatory weight that legacy CloudTrail data lacks.

ai-securityllm-securityagentic-aiforensic-auditauditcybersecurity
Read post →

Shadow AI in 2026: Detection Patterns, Real Incidents, and What Your SOC Should Already Be Doing

The shadow IT framing for shadow AI is now outdated. Shadow AI is browser-extension-deep: ChatGPT in DevTools, Copilot in IDE, Claude in Slack. Blocking fails for the same architectural reason it failed for shadow SaaS in 2018. This article walks through current detection patterns at the DNS, proxy, OAuth consent, and browser inventory layers, three documented shadow AI incidents from 2025-2026, and why a policy gateway succeeds where blocking does not. The piece refreshes the existing shadow AI canon for the patterns SOCs are actually seeing in production this year.

shadow-aiai-securitycybersecuritydata-loss-preventiondlppolicy-enforcement
Read post →