← All posts

Industry Verticals

266 posts on industry verticals.

FFIEC AI Controls Mapping: Owners, Tests, Evidence, and Gaps

FFIEC AI controls mapping should connect each technology-neutral examination anchor to a scoped AI control, accountable owner, enforcement point, repeatable test, retained evidence, current result, and open gap. This guide builds that map across governance, inventory, lifecycle, access, logging, providers, resilience, and assurance.

ai-complianceai-governancefinancial-servicesregulationauditpolicy-enforcement
Read post →

EU MDR AI Compliance Checklist for Medical Device Software

This EU MDR AI compliance checklist turns intended purpose, software classification, technical documentation, quality management, post-market surveillance, change control, and routed LLM evidence into owner-assigned tests. Each check has a pass condition and retained artifact, with the request gateway boundary stated plainly.

ai-complianceai-governanceauditregulationpolicy-enforcementcompliance
Read post →

FERPA AI Controls Mapping for the Authenticated LLM Path

This FERPA AI controls mapping connects disclosure authority, legitimate educational interest, identity, purpose, destination policy, audit records, retention, and vendor evidence to named owners and repeatable tests. It keeps the authenticated HTTP enforcement boundary separate from consent, contract, student-rights, endpoint, and legal obligations.

ai-complianceai-governancecomplianceauditidentity-and-authorizationpolicy-enforcement
Read post →

EU MDR AI Audit Evidence for a Notified Body Review

EU MDR AI audit evidence should let a notified body move from a selected device to its intended purpose, approved software configuration, risk and validation records, field signals, changes, and corrective actions. This guide builds that assessor package while keeping routed LLM evidence inside its actual HTTP boundary.

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

FDA AI/ML Guidance AI Compliance Checklist for Device Software

This FDA AI/ML guidance AI compliance checklist gives medical-device teams seven gradable checks for scope, lifecycle documentation, data and validation, PCCP changes, quality-system records, postmarket response, and routed LLM traffic. Each check names an owner, pass condition, retained evidence, and remediation state without presenting nonbinding guidance as a regulation.

ai-complianceai-governancecomplianceregulationauditpolicy-enforcement
Read post →

FERPA AI Audit Evidence for Student Record Disclosures

FERPA AI audit evidence should reconstruct each governed disclosure of personally identifiable information from education records, including the recipient, legitimate interest, authority, identity, purpose, policy decision, and retained record. This guide separates request-layer evidence from consent, contract, student-access, and vendor-governance records owned elsewhere.

ai-complianceai-governancecomplianceauditidentity-and-authorizationpolicy-enforcement
Read post →

COPPA AI controls mapping across legal duties and HTTP enforcement

A COPPA AI controls mapping should connect each Part 312 duty to an accountable owner, control point, test, and evidence artifact. This mapping covers scope, notice, consent, parental rights, minimization, security, vendors, retention, and the limited enforcement available on routed HTTP LLM calls.

ai-complianceregulationai-governancepolicy-enforcementaudit
Read post →

FDA AI/ML Guidance Audit Evidence for Device Software Reviews

FDA AI/ML guidance audit evidence should let a reviewer trace an AI-enabled device software function through its intended use, development data, validation, approved change route, deployed configuration, and postmarket signals. This guide builds a reviewer-selected evidence package while separating nonbinding FDA guidance from the binding Quality Management System Regulation.

ai-complianceai-governanceauditcomplianceregulationforensic-audit
Read post →

FDA AI/ML Guidance AI Controls Mapping for Device Software

This FDA AI/ML guidance AI controls mapping connects lifecycle documentation, model data, validation, PCCP changes, QMS records, postmarket response, and routed LLM traffic to a control objective, accountable owner, enforcement point, repeatable test, retained artifact, and explicit boundary. It preserves the difference between draft guidance, final guidance, and regulation.

ai-complianceai-governancecomplianceregulationauditpolicy-enforcement
Read post →

EU MDR AI Controls Mapping for Medical Device Software

This EU MDR AI controls mapping links each medical-device software objective to an accountable owner, control point, repeatable test, retained evidence, and explicit boundary. It covers intended purpose, technical documentation, changes, post-market surveillance, CAPA, and routed LLM requests without assigning full conformity to one technical component.

ai-complianceai-governanceauditregulationpolicy-enforcementarchitecture
Read post →

IRS Publication 1075 AI Audit Evidence for Model Requests and Decisions

IRS Publication 1075 AI audit evidence starts with a complete population of authenticated model requests, then binds reviewer-selected samples to identity, destination, policy, decision, response handling, integrity, and retention. This guide separates evidence an HTTP policy gateway can produce from programme, legal, endpoint, and operational records that stay outside that boundary.

ai-complianceai-governanceirs-1075public-sectorauditdata-protection
Read post →

FISMA AI Audit Evidence for Model Requests and Decisions

FISMA AI audit evidence starts with a complete population of authenticated model requests, then binds reviewer-selected samples to identity, destination, policy, decision, response handling, integrity, and retention. This guide separates evidence an HTTP policy gateway can produce from programme, legal, endpoint, and operational records that stay outside that boundary.

ai-complianceai-governancefismapublic-sectorauditpolicy-enforcement
Read post →