Blog

Analysis on enterprise AI governance, inline policy enforcement, agentic AI security, and regulatory compliance.

What Is Agentic AI: The Architectural Definition, the Control-Plane Implications, and the Audit Record It Requires

Agentic AI is a software pattern where an LLM-driven agent decomposes a goal, calls tools, observes results, and iterates until the goal completes. The pattern differs from generative AI by the loop, the tool calls, and the autonomy. The control-plane implications are distinct: identity at the agent level, scoped permissions for each tool call, audit records for each step in the loop, and the question of who carries liability for the agent decisions. The NIST AI agent identity and authorization framework took comments through April 2, 2026 and set the operational baseline.

Problem-Awareagentic-aiai-agentsai-governanceauditinline-enforcementcompliance
Read post →

Enterprise AI Usage Policy Template: The Eight Sections That Survive Both Workforce Adoption and Regulatory Review

An AI usage policy that an enterprise can actually enforce contains eight sections: scope and definitions, sanctioned tools list, data classification rules, role-based permissions, the disclosure obligation, the inspection and monitoring statement, the incident reporting path, and the policy version history. A policy without inspection architecture behind it leaves the enterprise with a written commitment the workforce can ignore. The eight sections align with the EU AI Act Article 26 deployer obligations and the Article 12 record-keeping mandate.

Problem-Awareai-governanceai-policycomplianceshadow-aiauditai-security
Read post →

Shadow AI Detection Methods: The Five Detection Surfaces and Why Three of Them Miss Most Real Usage

Shadow AI detection happens on five surfaces: endpoint agents, network DNS, SSL inspection, identity provider logs, and inline AI request proxies. Endpoint, DNS, and identity logs detect attempts to reach known AI vendor domains but miss prompt content and never see browser-based usage to unsanctioned tools. SSL inspection captures content but only where TLS-break infrastructure is deployed to the AI provider domains. Inline proxies on the AI request path see identity, classification, and policy state at decision time. The five surfaces differ in what they detect and when.

Problem-Awareshadow-aiai-securityai-governanceinline-enforcementcomplianceaudit
Read post →

Shadow AI for CISOs: The Four Questions the Board Asks and the Records the CISO Has to Produce

Cloud Radix reports 90% of CISOs identify shadow AI as their top security concern for the year. Boards are now asking four questions that translate directly into operational records: which AI tools are in use, what data has flowed to them, what policy applied at decision time, and what was the exposure window. The CISO who can answer the four with contemporaneous records has discharged the operational duty. The CISO who reconstructs from logs after the fact has not.

Problem-Awareshadow-aicisoai-securityai-governanceauditcompliance
Read post →

Employee ChatGPT Monitoring: The Inspection Points That Actually See Prompt Content (and the Ones That Miss It)

Employee ChatGPT usage produces five separable telemetry surfaces, and only two of them see the prompt content. Endpoint and DNS surfaces see the connection. SSL inspection and inline AI proxies see the content. SSO sees the sign-in but nothing after it. The combination of where the inspection happens and what the record contains decides whether the monitoring satisfies the operational requirement an auditor or a board would accept. Cloud Radix reports 77% of employees using unauthorized AI admit to pasting sensitive business data into prompts.

Problem-Awareshadow-aichatgptmonitoringinline-enforcementai-governancedlp
Read post →

EU AI Act Foundation Models: How the Regulation Treats Pre-Training, Fine-Tuning, and Substantial Modification

The EU AI Act does not use the term "foundation model" in its operative text. The regulation treats the underlying systems as general-purpose AI models under Article 51 and triggers systemic-risk obligations at 10^25 training FLOPs under Article 52. Fine-tuning and integration into downstream systems are handled separately by Article 25. The result is a layered obligation set that depends on whether the model is pre-trained, fine-tuned, or repurposed into a high-risk system.

Compliance & Regulationeu-ai-actfoundation-modelsgpaicomplianceai-governanceregulation
Read post →

EU AI Act GPAI: What General-Purpose AI Model Providers Owe Under Article 51 and the Article 53 Code of Practice

Article 51 sets a separate obligation track for general-purpose AI models. Article 52 lists what counts as systemic-risk GPAI. Article 53 requires the provider to draw up technical documentation and to make information available to downstream providers. The GPAI obligations took effect August 2, 2025, ahead of the high-risk obligations. The Code of Practice published by the AI Office sets the practical compliance roadmap for the most-deployed foundation models in 2026.

Compliance & Regulationeu-ai-actgpaifoundation-modelscomplianceai-governanceregulation
Read post →

EU AI Act for Fintech: Why Credit Scoring, Fraud Detection, and Insurance Pricing Land in the High-Risk Bucket

Annex III point 5(b) of the EU AI Act puts AI used in evaluating the creditworthiness of natural persons in the high-risk bucket. Annex III point 5(c) puts AI used in life and health insurance pricing in the same bucket. Fraud-detection AI used in retail banking sits in scope where it affects access to essential services. DORA, the Digital Operational Resilience Act, runs in parallel with overlapping log retention and incident reporting obligations. The August 2, 2026 high-risk deadline and the January 17, 2025 DORA effective date are both already binding.

Compliance & Regulationeu-ai-actfintechdoracomplianceai-governanceaudit
Read post →

EU AI Act for Healthcare: Why AI in Diagnostics, Triage, and Clinical Decision Support Lands in the High-Risk Category

Healthcare AI sits in the high-risk category by two paths. Annex III lists AI used in employment and essential services. The Medical Device Regulation pulls in any AI that meets the definition of a medical device, including most diagnostic and triage tools. The combination means most clinical AI deployments owe both the EU AI Act high-risk obligations and the MDR conformity assessment. The August 2, 2026 deadline applies, and the record-keeping infrastructure most hospitals run today fails the Article 12 test.

Compliance & Regulationeu-ai-acthealthcarecomplianceai-governancemedical-deviceaudit
Read post →

EU AI Act Conformity Assessment: The Two Routes, Who Performs Each One, and What the Audit File Has to Contain

A high-risk AI system cannot be placed on the Union market without a conformity assessment. Article 43 allows two routes: an internal control procedure based on Annex VI, and a third-party procedure involving a notified body and Annex VII. The route depends on the system category. The audit file must contain the technical documentation listed in Annex IV, including the system architecture, the risk management process, the data governance approach, and the record-keeping system. Most enterprise deployers have not yet built the record-keeping side.

Compliance & Regulationeu-ai-actcomplianceai-governanceauditregulationhigh-risk-ai
Read post →

EU AI Act Fines: How Article 99 Sets €35M / €15M / €7.5M Tiers and Who Pays Each One

Article 99 of the EU AI Act sets three penalty tiers. €35 million or 7% of global turnover for prohibited practices. €15 million or 3% for high-risk non-compliance. €7.5 million or 1% for supplying misleading information. The high-risk tier is the one that lands on most enterprise deployers, and the math is set up so that the higher of the absolute number and the percentage applies.

Compliance & Regulationeu-ai-actcomplianceai-governanceregulationauditai-security
Read post →

RAG Prompt Injection: How the Retrieval Step Becomes the Attack Surface

RAG prompt injection turns the retrieval step into the attack surface. Adversarial content inside a retrieved document reaches the model context with the same trust level as the application instructions. The model has no architectural way to distinguish trusted spans from untrusted spans. This piece walks through the four retrieval paths that open the surface, the failure modes the model alone cannot close, and the inspection-layer controls that produce a deterministic decision and an audit record EU AI Act Article 12 reviewers will accept.

Problem-Awareprompt-injectionragllm-securityai-securityindirect-prompt-injectionaudit
Read post →