ARCS/Crosswalks/Financial Services Sector Profile

This instrument is informative and is not part of the normative ARCS control text. Financial services regulation is fragmented across jurisdictions, regulators, and use cases. This profile identifies recurrent regulatory themes where ARCS control families are relevant and maps them to ARCS families. It does not map any single regulatory instrument and does not claim compliance with any financial services obligation.
SectionsOverviewInterpretive statusSector characteristicsARCS relevanceRegulatory themesRepresentative sourcesOutside scopeReferences

Overview

Financial services institutions operate under extensive recordkeeping, supervision, audit, vendor governance, and preservation obligations. As AI systems are deployed in these environments, their interaction records become subject to those same disciplines.

This profile identifies the most common regulatory themes in financial services where ARCS control families are relevant, without mapping any single regulatory instrument.

Interpretive status

This profile is an informative sector-level instrument. It is not a crosswalk against any single regulatory framework. It does not establish compliance with any financial services obligation and does not alter the normative ARCS control text.

Sector characteristics

Financial services regulation combines long retention obligations, mandatory supervision and surveillance requirements, robust audit expectations, strict vendor governance rules, and multi-jurisdictional compliance complexity. AI systems create new record classes (interaction logs, agent traces, automated decision records) that existing recordkeeping frameworks did not anticipate.

ARCS relevance

Within financial services, the most relevant ARCS domains are retention tier classification, audit trail governance, vendor custody chain mapping, preservation and litigation hold, non-creation verification, and publish-boundary controls for records crossing organizational or jurisdictional boundaries.

Regulatory themes

The following themes recur across financial services regulatory regimes. For each theme, the profile identifies the most relevant ARCS control families.

Books and records obligations

ARCS-LIF, ARCS-TAX, ARCS-VER

Financial institutions face extensive recordkeeping requirements governing the creation, retention, and production of business records. AI systems that generate interaction records in regulated contexts create new record classes that may fall within these obligations. ARCS-LIF, ARCS-TAX, and ARCS-VER are most relevant: lifecycle classification, retention tier assignment, and verification of recordkeeping claims.

Supervision and surveillance

ARCS-AGT, ARCS-CUS, ARCS-LIF

Supervisory obligations require firms to monitor communications and activities for compliance. AI interaction records, agent tool traces, and automated decision artifacts may become subject to supervisory review. ARCS-AGT, ARCS-CUS, and ARCS-LIF support supervision by making runtime-generated records classifiable, locatable, and lifecycle-governed.

Vendor and third-party risk management

ARCS-CUS, ARCS-OPB, ARCS-VER

Financial regulators require governance of third-party service providers. AI vendor relationships create custody chains for interaction records across operator, vendor, and subprocessor surfaces. ARCS-CUS, ARCS-OPB, and ARCS-VER govern custody mapping, operator-boundary documentation, and vendor governance declaration verification.

Retention and disposal

ARCS-LIF, ARCS-NCR, ARCS-VER

Financial services regulation imposes specific retention periods and disposal requirements. AI interaction records require the same lifecycle discipline applied to traditional business records. ARCS-LIF governs retention tiers, deletion posture, and deletion verifiability. ARCS-NCR governs auditable non-creation for record classes that should not exist.

Audit trail and examination readiness

ARCS-VER, ARCS-LIF, ARCS-TAX

Regulated financial institutions must maintain auditable records and be prepared for regulatory examination. ARCS-VER, ARCS-LIF, and ARCS-TAX support examination readiness by making lifecycle state, custody chain, and classification treatment verifiable and testable against documented governance claims.

Preservation and litigation hold

ARCS-PV, ARCS-CUS, ARCS-LIF

Financial litigation, enforcement actions, and regulatory investigations require preservation of relevant records. ARCS-PV governs hold triggers, suspension of deletion, multi-vendor preservation communication, and coordinated hold management across distributed AI record surfaces.

Model governance and validation records

ARCS-TAX, ARCS-AGT, ARCS-LIF

Financial regulators increasingly require governance of AI and algorithmic decision models. The records generated during model validation, testing, and monitoring create governed record classes. ARCS-TAX, ARCS-AGT, and ARCS-LIF support classification and lifecycle treatment of model governance artifacts.

Data residency and cross-border custody

ARCS-CUS, ARCS-OPB, ARCS-PUB

Financial regulation often restricts where data may be stored and processed. AI interaction records that cross jurisdictional boundaries create custody chain and operator-boundary questions. ARCS-CUS, ARCS-OPB, and ARCS-PUB govern custody mapping, boundary documentation, and publish-boundary controls across jurisdictions.

Representative sources

The regulatory themes above draw from obligations across multiple jurisdictions and regulators. This list is representative, not exhaustive. Separate framework-specific crosswalks may be published for individual regulatory instruments.

Regulator / sourceRelevant themes
SECBooks-and-records requirements (Rules 17a-3, 17a-4), recordkeeping for investment advisers, supervision obligations
FINRASupervision requirements (Rules 3110, 3120), communications review, recordkeeping, vendor oversight
NYDFSCybersecurity regulation (23 NYCRR 500), risk assessment, audit trail, third-party service provider security
OCC/Fed/FDICBank examination procedures, model risk management (SR 11-7/OCC 2011-12), third-party risk management
EU DORADigital Operational Resilience Act: ICT risk management, incident reporting, digital operational resilience testing, third-party risk
FCAUK Financial Conduct Authority operational resilience, AI governance, consumer duty, systems and controls
SEC
Books-and-records requirements (Rules 17a-3, 17a-4), recordkeeping for investment advisers, supervision obligations
FINRA
Supervision requirements (Rules 3110, 3120), communications review, recordkeeping, vendor oversight
NYDFS
Cybersecurity regulation (23 NYCRR 500), risk assessment, audit trail, third-party service provider security
OCC/Fed/FDIC
Bank examination procedures, model risk management (SR 11-7/OCC 2011-12), third-party risk management
EU DORA
Digital Operational Resilience Act: ICT risk management, incident reporting, digital operational resilience testing, third-party risk
FCA
UK Financial Conduct Authority operational resilience, AI governance, consumer duty, systems and controls

Outside scope

ARCS does not govern financial product design, trading strategy, credit risk modeling, market conduct, capital adequacy, consumer protection enforcement, or prudential supervision. It governs the lifecycle and custody of records created by AI systems operating in environments subject to those regulatory disciplines. Separate framework-specific crosswalks may be published for individual regulatory instruments such as NYDFS 23 NYCRR 500 or EU DORA.