← All posts

Industry Verticals

266 posts on industry verticals.

EBA ICT Guidelines AI Audit Evidence After the DORA Scope Change

The EBA narrowed its ICT and security risk management Guidelines after DORA began to apply. For AI used in payment-service customer interactions, the remaining evidence question concerns security guidance, customer choices, alerts, updates, and support. This guide builds an audit package around that current scope while separating runtime AI records from adjacent payment controls.

ai-governanceai-compliancecomplianceregulationdoraaudit
Read post →

COPPA AI audit evidence for sampling, retrieval, and integrity

COPPA AI audit evidence should let an assessor reconstruct which child-facing data flows existed, how consent and parental requests were handled, and which safeguards operated. This guide separates population sampling, record retrieval, integrity checks, and the bounded evidence available at a routed LLM request.

ai-complianceregulationauditforensic-auditpolicy-enforcement
Read post →

CJIS AI Controls Mapping: Requirements at the Authenticated LLM Boundary

This CJIS AI controls mapping connects selected access, information-flow, identity, and audit requirements to an implementation point, owner, test, evidence artifact, and explicit boundary. It shows where an HTTP AI gateway contributes direct or partial coverage and where IAM, records, operations, endpoints, and incident teams remain responsible.

ai-complianceai-governancearchitecturecjispolicy-enforcementpublic-sector
Read post →

CJIS AI Compliance Checklist: Owners, Evidence, and Pass Conditions

This CJIS AI compliance checklist converts policy requirements into actions with named owners, evidence artifacts, and pass conditions. It covers scope, authentication, information flow, event content, review, reporting, integrity, search, retention, and boundary ownership for AI requests that may handle criminal justice information.

ai-complianceai-governancechecklistcjispublic-sectorzero-trust
Read post →

CJIS AI Audit Evidence: Build a Review Package Investigators Can Replay

CJIS AI audit evidence should let a reviewer reproduce the population, sample selection, request decision, protected record, and retrieval result. This guide turns CJIS audit requirements into an evidence package for authenticated HTTP AI traffic while keeping IAM, endpoint, records, and incident duties with their proper owners.

ai-complianceai-governanceauditcjispublic-sectorzero-trust
Read post →

AI Governance for Real Estate Starts With the Property Decision

AI governance for real estate should separate tenant screening, leasing communications, brokerage work, property operations, valuation, and lending. Each use needs an owner, permitted data, exact model route, review requirement, and evidence tied to the property or applicant record. Request-layer controls can govern authenticated HTTP model traffic while housing decisions, consumer-report duties, fair-housing review, and vendor-managed AI remain with their assigned owners.

ai-governanceai-compliancepolicy-enforcementidentity-and-authorizationaudit
Read post →

AI Governance for Municipal Government Starts With the Service Record

AI governance for municipal government should connect every approved use to a department, public service, record system, data class, model route, and accountable official. Citywide policy supplies common rules, while service owners decide how generated work enters permitting, benefits, public safety, procurement, and resident communications. Request-layer evidence can support that program for authenticated HTTP model traffic without replacing records management or official decisions.

ai-governanceai-compliancenist-ai-rmfpolicy-enforcementaudit
Read post →

AI Governance for Mortgage Lending Starts With the Loan File

AI governance for mortgage lending should connect every approved use case to a loan-stage owner, permitted borrower data, the exact model route, and review evidence. ECOA and Regulation B require specific adverse-action reasons that reflect the factors actually considered. Federal automated valuation model rules add quality controls for covered mortgage valuations. A lender also needs separate controls for vendor-managed AI and decisions that never cross an LLM gateway.

ai-governancemortgagefair-lendingai-compliancepolicy-enforcementaudit
Read post →

AI Governance for Medical Devices Connects Change Control to Field Evidence

AI governance for medical devices should connect each AI function to its intended use, regulatory status, quality-system owner, change-control path, field monitoring, and retained evidence. FDA guidance on AI-enabled device software and predetermined change control plans makes lifecycle risk management concrete. EU MDR adds quality management and post-market surveillance duties. Routed LLM calls need a control record without confusing request evidence with device validation.

ai-governanceai-compliancemedical-devicesfdaeu-mdraudit
Read post →

AI Governance for Media and Publishing Needs an Editorial Evidence Chain

AI governance for media and publishing needs an editorial evidence chain that connects source material and model use to human review, publication authority, provenance, and correction records. Request-layer policy can govern authenticated HTTP model calls routed through it. Editorial judgment and rights clearance, plus archive integrity and publishing approval, remain with the newsroom or publisher.

ai-governanceai-complianceeu-ai-actauditpolicy-enforcement
Read post →

AI Governance for Law Firms Needs Matter-Level Decision Rights

AI governance for law firms needs matter-level approval instead of one firm-wide permission for a named model. The operating record should connect each legal use to the responsible lawyer, client terms, permitted information, model route, review duty, and retained evidence. Request controls support that program for authenticated HTTP calls routed through an enforcement point.

ai-governanceai-compliancepolicy-enforcementauditidentity-and-authorization
Read post →

AI Governance for Higher Education Needs Campus-Level Decision Rights

AI governance for higher education needs a campus operating model that separates admissions, learning assessment, research, student services, and administrative assistance. Each approved LLM route should carry an originating identity, purpose, education-record classification, and policy decision. Request-layer evidence supports the program without replacing academic judgment or institutional review.

ai-governanceai-compliancenist-ai-rmfauditidentity-and-authorization
Read post →