← All posts

Industry Verticals

73 posts on industry verticals.

EU AI Act for Healthcare: What Articles 6, 12, and Annex III Require of Hospital AI Deployments

EU AI Act high-risk classification applies to several healthcare AI use cases including AI as a safety component of medical devices under Article 6(1) and the Annex III categories covering access to essential services, biometric categorization, and emergency triage. From August 2, 2026, hospitals deploying these AI systems take on deployer obligations under Article 26 and have to support providers in meeting Articles 8 through 17. The Medical Device Regulation and the EU AI Act layer for software-as-a-medical-device. The architecture that satisfies the high-risk regime is per-decision audit records that capture identity, data class, policy state, and decision outcome on the hospital side.

healthcareeu-ai-actmedical-devicesmdrai-compliancehospital-ai
Read post →

B2B SaaS with AI Features: How Enterprise Security Reviews Now Block the Deal

B2B SaaS vendors that added AI features in the last twelve months are now meeting an enterprise security review process that did not exist when the product was scoped. Buyers ask about identity context at the model API call, per-decision audit records, prompt-level data classification, and the deployment regime under the EU AI Act. Sales cycles stall on questions the engineering team did not anticipate. This piece walks through what enterprise security reviews now ask of SaaS-with-AI vendors, where most product architectures are exposed, and the inspection layer that closes the gap before procurement does.

b2b-saasai-compliancesecurity-revieweu-ai-actenterpriseaudit
Read post →

EU AI Act for Fintech: How Credit Scoring and Fraud Detection Become High-Risk in August 2026

On August 2, 2026 the EU AI Act high-risk system requirements begin to apply to fintech credit scoring, creditworthiness assessment, and several adjacent financial decisions. The classification falls under Annex III point 5(b). Deployers inherit Article 26 obligations including per-decision logging, human oversight, instructions for use, and incident notification. The provisions overlap with DORA on third-party risk and incident reporting. This piece walks through which fintech AI use cases become high-risk, what the deployer obligation actually requires, and where most lender deployments are exposed.

eu-ai-actfintechcredit-scoringai-compliancefinancial-servicesaudit
Read post →

AI Credit Scoring Under Annex III Point 5(b): What High-Risk Classification Requires of Banks

Annex III point 5(b) of the EU AI Act classifies AI used to evaluate the creditworthiness of natural persons or establish a credit score as high-risk. From August 2, 2026 the deployer obligations under Article 26 and the provider obligations under Articles 8 through 17 apply. The text exempts AI used only for the detection of financial fraud. Most bank credit deployments today combine scoring, fraud detection, and bureau enrichment in a single pipeline that triggers high-risk classification end-to-end. This piece walks through what the classification means, where bank pipelines blur the fraud-vs-scoring line, and the architecture that produces audit records the supervisor will accept.

eu-ai-actcredit-scoringbankingai-complianceauditannex-iii
Read post →

Fannie Mae LL-2026-04: What the Lender AI Governance Mandate Requires from Mortgage Originators

On April 8, 2026, Fannie Mae issued Lender Letter LL-2026-04, a governance framework for AI and ML in mortgage origination and servicing. It takes effect August 6, 2026, 120 days after publication. Freddie Mac Section 1302.8 has been enforced since March 3, 2026. The combined GSE regime requires inventory, governance, audit trails, and disclosure on demand for AI used in any step of the loan lifecycle, including vendor AI tools the lender does not control. This piece walks through what the mandate requires, where lender deployments are exposed, and the inspection architecture that satisfies the disclosure obligation.

fannie-maemortgageai-governanceai-complianceauditlender-letter
Read post →

Finance AI and Pre-Announcement Earnings Exposure: How AI Tools Create MNPI Leakage

Pre-announcement earnings exposure inside finance teams now flows through AI tools that finance teams use for drafting, modeling, and summarization. The exposure is functionally a material non-public information leak when an employee pastes a draft press release, a working forecast, or a board-pack excerpt into an unauthorized AI tool. SEC Regulation FD, insider trading regimes, and individual market-abuse regulations in the EU and the UK reach the conduct regardless of whether the leak was intentional. This piece walks through where the AI exposure sits inside the financial close and earnings preparation cycle, what controls regulators expect, and the inspection architecture that prevents MNPI from leaving the perimeter.

mnpireg-fdfinanceai-securityshadow-aimarket-abuse
Read post →

FERPA and AI: What School Records Confidentiality Requires from AI Tools in K-12 and Higher Ed

FERPA protects the confidentiality of education records. Schools and the edtech vendors operating on their behalf are now putting student data through AI tools for tutoring, grading assistance, behavioral analytics, and parent communication. The "school official" exception in FERPA covers vendors only when specific written agreement, legitimate educational interest, and direct control conditions are satisfied. Most AI vendor relationships were not constructed with those conditions in mind. This piece walks through what FERPA actually requires when AI processes education records, where the school official exception breaks for AI vendors, and the architecture that satisfies the disclosure controls.

ferpaedtechstudent-dataai-complianceauditk12
Read post →

AI in OT Environments: What IEC 62443 and NIS2 Require When LLMs Touch Industrial Control Systems

Manufacturing OT environments now host AI tools for predictive maintenance, anomaly detection, work-instruction generation, quality inspection, and operator copilots. The AI calls cross zones that IEC 62443 was designed to segment and bring NIS2 incident reporting and supply chain obligations into the operational technology footprint. Most OT deployments use AI through cloud APIs that violate the segmentation assumptions of the IEC 62443 reference model. This piece walks through where AI sits in modern OT, what IEC 62443 and NIS2 require for the AI traffic, and the inspection architecture that produces records the regulator and the customer auditor will accept.

ot-securitymanufacturingiec-62443nis2ai-securityindustrial-control
Read post →

AI Security for Legal Discovery: The Identity, Privilege, and Audit Controls a Production Deployment Has To Run

Legal discovery copilots read into the document repository, the case management system, and the email archive. The data the copilot reads at request time crosses attorney-client privilege, work-product doctrine, and the protective-order terms specific to each matter. This piece walks through the identity-aware policy decisions a legal discovery deployment has to commit at the request boundary, the audit record format that survives Rule 26 disclosure and a privilege challenge, and the architectural pattern that closes the gap.

legal-discoveryattorney-client-privilegework-productai-securityidentity-awareaudit-logs
Read post →

AI Security for HR Recruiting: The Identity, Bias, and Audit Controls a Production Deployment Has To Run

HR recruiting copilots reach across the ATS, the resume corpus, the assessment vendor data, and the interview transcripts. The decisions the copilot supports fall inside the EU AI Act Annex III high-risk classification for employment, the EEOC enforcement perimeter, and state employment-screening statutes like NYC LL 144 and Illinois AIVIA. This piece walks through the identity-aware policy decisions an HR recruiting deployment has to commit at the request boundary, the audit record format that survives an EEOC complaint and an EU AI Act review, and the architectural pattern that closes the gap.

hr-recruitingeu-ai-act-annex-iiieeocnyc-ll-144ai-securityaudit-logs
Read post →

AI Security for Finance Back Office: The Identity, Data, and Audit Controls a Production Deployment Has To Run

Finance back-office copilots reach across the GL, the close calendar, the vendor master, and the pre-announcement earnings detail. The data the copilot reads at request time crosses MNPI thresholds, vendor confidentiality contracts, and SOX 302 attestation territory. This piece walks through the identity-aware policy decisions a finance back-office deployment has to commit at the request boundary, the audit record format that survives SOX and SEC review, and the architectural pattern that closes the gap.

finance-back-officemnpisoxai-securityidentity-awareaudit-logs
Read post →

AI Gateway for Banks: The Inspection Layer for Regulated AI Traffic Under OCC, FFIEC, and the EU AI Act

Banks handle AI traffic that touches credit decisions, fraud screening, customer service transcripts, internal research copilots, and increasingly model-assisted regulatory reporting. Each route carries a different supervisory expectation. This piece walks through the regulatory regimes a US or EU bank operates under, the inspection target the gateway covers per route, the audit record format that satisfies OCC SR 11-7, FFIEC AIO guidance, EU AI Act Article 12, and the deployment topology that fits a bank-grade environment.

bankingfinanceoccffieceu-ai-actmodel-risk-management
Read post →