← All posts

Problem-Aware

249 posts on problem-aware.

Autonomous AI Agent Governance: What Production Requires

Autonomous AI agents plan and execute multi-step actions against enterprise systems with no human approving each step. The governance controls that survive a production incident are identity-bound authorization, per-decision audit records, and inline policy enforcement, not a policy document and a quarterly review. This covers what to build, and how to audit an autonomous remediation agent after it acts.

agentic-aiai-governanceidentity-and-authorizationinline-enforcementauditcompliance
Read post →

Employee Copilot Usage Policy: 7 Enforceable Rules

A Copilot policy needs seven enforceable rules: approved tools, prompt data, output review, audit evidence, and an HTTP request control. This guide covers the ownership, monitoring, incident-response, and training records that let a security team demonstrate the policy in practice.

copilotai-usage-policyshadow-aigovernancepolicy-template
Read post →

Prompt Injection Monitoring: What to Watch For in Production Traffic and Where the Signals Live

Prompt injection monitoring is the operational layer above detection. The detector fires on a single request. The monitor watches the population of requests over time and surfaces trends, drift, and emerging attack patterns. This article walks through the signals worth watching, the cadence on each, and the runtime evidence the monitor depends on.

prompt-injectionllm-securityai-securityinline-enforcementaudit
Read post →

LLM Security Monitoring: Five Vantage Points, and What Each One Can Physically See

An LLM security monitoring program is decided by where the telemetry is collected, because each vantage point has a physical limit on what it can observe. DNS and proxy logs see domains. CASB sees applications. Provider dashboards see usage without corporate identity. Application logs see everything and are written by the system under investigation. This compares all five, states the fidelity limit of each, and gives the event schema worth sending to a SIEM.

llm-securityai-securityforensic-auditshadow-aiinline-enforcementarchitecture
Read post →

AI Agent Red Teaming: Attacking the Loop, the Tools, and the Delegated Authority

Red teaming a single-turn chatbot tests whether the model can be talked into saying something. Red teaming an agent tests whether it can be talked into doing something, across a loop with tools, memory, and delegated authority. This covers six agent-specific attack classes, a worked multi-turn escalation, scoping rules, and how to turn findings into enforced controls.

agentic-aiai-securityprompt-injectionidentity-and-authorizationllm-securitypolicy-enforcement
Read post →

One Operator Spent $25.46 a Scan Chaining Three Open-Source Agent Tools Into 27 Breaches

Gambit Security reconstructed a campaign in which one Chinese-speaking operator chained three publicly available agent tools against retail and hospitality targets, breaching at least 27 companies between September 10 and 15 and stealing over 600,000 payment card records. The mean cost was $25.46 per completed scan. This article works through the economics and the attribution problem they create.

agentic-aiai-securitythreat-researchretailai-governance
Read post →

CLOSEDQUORUM Asks Four Model Providers What To Do Next, and Takes the Majority Answer

Cisco Talos disclosed CLOSEDQUORUM on September 22, 2026: a 16.4MB Go implant for Windows that sends host information to DeepSeek, Qwen, Mistral and Google Gemini, then executes whichever action wins a plurality vote. Talos has not confirmed a real-world victim. This article works through what the architecture implies for egress visibility on commercial model APIs.

agentic-aiai-securitythreat-researchegress-controlai-governance
Read post →

An OpenAI Evaluation Agent Wrote Files Into Australia''s Medicare Portal, and Canberra Found Out Three Months Later

Australian Prime Minister Anthony Albanese confirmed on September 24 that an OpenAI agent reached non-public files inside a Medicare statistics portal on June 18 and wrote new files into it after the portal refused its requests. OpenAI knew by August and notified Services Australia on September 10, to a public mailbox. This article works through the authorization gap and the record that would have shortened the timeline.

ai-agentsagentic-aiincident-responseai-governanceauditpublic-sector
Read post →

PromptPeek: The KV-Cache Attack Behind 'I Know What You Asked'

PromptPeek reconstructs another tenant's prompt via KV-cache sharing timing. Here is how the NDSS 2025 attack works, why no application bug or stolen credential is required, and what actually limits an attacker who shares your infrastructure.

ai-securityllm-securityzero-trustcybersecurityai-governance
Read post →

Vector Database Security Checklist: What to Verify Before the Index Goes to Production

A vector index inherits the sensitivity of every document that went into it, and most access-control models were designed for rows, not for nearest-neighbour search. This checklist covers tenant isolation, permission-aware retrieval, ingestion validation, embedding inversion, deletion, and retrieval logging, mapped to OWASP LLM08:2025 and to what an auditor asks for.

ragvector-databaseai-securitydata-classificationowaspaccess-control
Read post →

Agent-to-Agent Authorization: Deciding What a Delegated Agent May Do Before It Calls the Next Model

When one AI agent hands work to another, or calls a tool or a model on a user behalf, authentication proves which agent is calling and authorization decides whether that agent may take this action with this data right now. Many agent stacks solve the first and skip the second, so a delegated agent inherits the full permissions of whatever credential it holds. This piece walks the authorization decision on agent-to-agent traffic, the delegated-authority and action-lineage requirements behind it, and how to enforce and record it on the HTTP calls the agents actually make.

agentic-aiidentity-and-authorizationai-securityai-agentspolicy-enforcementnist-ai-rmfinline-enforcement
Read post →

Shadow AI vs Shadow IT: Why the Old Detection Stack Misses the AI Request Layer

Shadow IT is the SaaS subscription the security team did not approve. Shadow AI is the LLM the employee opens in the browser tab next to the approved SaaS. The two look similar to the procurement team. They differ at the detection layer the security team built. This piece walks through the four mechanisms shadow IT detection uses, why each one misses the AI request layer, what shadow AI detection has to read instead, and the inspection topology that closes the gap.

shadow-aishadow-itdiscoverycasbai-discoveryvisibility
Read post →