← All posts

Industry Verticals

266 posts on industry verticals.

AI Vendor Risk for Airlines Lives at the Operational Interface

EU Part-IS requires aviation organizations to identify interfaces with other organizations that can create mutual information-security exposure and to manage risks in contracted activities. NIS2 adds direct supplier and service-provider relationships to required supply-chain security measures. This article applies both duties to authenticated airline model traffic.

ai-securityai-governanceai-complianceregulationauditpolicy-enforcement
Read post →

AI Vendor Risk for Accounting Firms Starts With the Client Record

FTC safeguards requirements make accounting firms responsible for selecting service providers that can protect customer information, putting safeguards in contracts, and overseeing how providers handle the data. This article applies that duty to AI requests carrying tax records, payroll files, client correspondence, and engagement notes.

ai-securityai-governanceai-complianceauditcompliancepolicy-enforcement
Read post →

HIPAA-Compliant AI Agent Platforms: BAAs, Access Control, and Audit Evidence

HIPAA compliance for an AI agent platform starts with a signed Business Associate Agreement, but the Security Rule also demands access control under 45 CFR 164.312(a) and audit controls under 164.312(b). This guide names the model platforms and healthcare tools that sign BAAs in 2026, then explains why a vendor BAA alone does not produce the identity-bound access-control and audit evidence a covered entity needs across its own clinicians and agents.

hipaahealthcareai-complianceai-securityidentity-and-authorizationauditpolicy-enforcement
Read post →

Shadow AI in Mortgage Lending: Borrower Files and Unapproved Model Routes

Shadow AI in mortgage lending can move borrower tax returns, bank statements, credit findings, appraisal notes, and servicing records into model services outside the lender''s approved controls. This article isolates the unauthorized HTTP request path, connects it to Regulation B and the FTC Safeguards Rule, and sets out the identity, content, destination, and evidence controls needed before borrower data reaches an LLM.

shadow-aiai-securityai-governancecompliancedata-loss-preventionaudit
Read post →

CSBS AI Supervisory Framework: Prepare the Examiner Evidence File

The CSBS Artificial Intelligence Supervisory Framework gives state examiners a Core Examiner Guide, document request list, work program, nonbank supplements, and an optional risk-tiering worksheet. Financial institutions can prepare by connecting each AI use case to its owner, purpose, vendor, risk tier, data controls, change record, and operating evidence. The framework remains discretionary, and each state agency decides how to incorporate it.

ai-complianceai-governancecomplianceregulationauditpolicy-enforcement
Read post →

AI Governance for Security Architects: Put Policy on the Model-Call Path

A security architect turns AI governance requirements into trust boundaries, identity flows, policy decision points, and evidence paths. This article maps the role to the HTTP model-call boundary, where authenticated users and agents can be evaluated against data classification, model authorization, and policy before a request leaves the enterprise.

ai-governanceai-securityarchitecturezero-trustidentity-and-authorizationpolicy-enforcement
Read post →

AI Governance for ML Engineers: Put the Control Contract Into the Deployment Path

ML engineers make AI governance executable by binding model releases to owners, approved purposes, data classes, evaluation evidence, routes, and rollback conditions. Runtime model calls then need identity-aware policy and a decision record so production use can be traced to the control contract approved for that release.

ai-governancedevsecopsarchitecturepolicy-enforcementauditnist-ai-rmf
Read post →

AI Governance for SOC Analysts: Turn Policy Decisions Into Investigable Events

A SOC analyst needs AI governance to produce events that can be triaged, correlated, and escalated. This article defines the event fields, detection logic, evidence chain, and response handoffs for governed HTTP model traffic, while keeping endpoint activity, local MCP processes, and destination-system actions inside their proper control boundaries.

ai-governanceai-securitycybersecurityforensic-auditauditpolicy-enforcement
Read post →

SR 11-7 AI Audit Evidence After SR 26-2

SR 11-7 AI audit evidence needs a current-source correction before fieldwork begins. SR 26-2 superseded the 2011 letter on April 17, 2026 and excludes generative and agentic AI from direct scope. Banks that apply its model-risk disciplines to LLMs through internal policy should freeze complete populations, let reviewers select samples, trace each request to approval and change records, and preserve gaps through retest.

ai-complianceai-governanceauditforensic-auditregulationpolicy-enforcement
Read post →

SR 11-7 AI Controls Mapping After SR 26-2

This SR 11-7 AI controls mapping uses the current SR 26-2 source and assigns bank-defined LLM controls to real owners. It maps governance, inventory, review, monitoring, change, third-party, and routed HTTP objectives to implementation points, repeatable tests, evidence, coverage verdicts, and open gaps while preserving the direct-scope exclusion for generative and agentic AI.

ai-complianceai-governanceauditregulationpolicy-enforcementforensic-audit
Read post →

AI Governance for Risk Managers: Turn Risk Appetite Into Runtime Decisions

A risk manager can approve an AI risk appetite and maintain the risk register. The role can assign control owners yet still lack evidence that production requests stayed inside those limits. This article gives the role an operating model for translating risk statements into request-level rules and monitoring exceptions, with escalation decisions supported by a traceable record.

ai-governanceai-compliancenist-ai-rmfauditpolicy-enforcementcompliance
Read post →

AI Governance for Behavioral Health Starts With the Treatment Context

AI governance for behavioral health has to distinguish treatment support, documentation, outreach, crisis workflows, and administrative work. The control model should bind every approved LLM call to a person, purpose, data class, and provider route while preserving the stricter handling that applies to substance use disorder records.

ai-governanceai-compliancehipaaauditpolicy-enforcementidentity-and-authorization
Read post →