Join our Newsletter — 33% off our NHI Course
Foundations & NHI Taxonomy

CDD

← Back to Glossary
By NHI Mgmt Group Updated November 3, 2026 Domain: Foundations & NHI Taxonomy

CDD is customer due diligence, the identity and risk checks a regulated business performs before or during a customer relationship. It usually includes verifying identity, understanding the customer profile, and monitoring for unusual activity so the organisation can meet anti-money laundering and sanctions obligations.

What CDD Covers in Practice

CDD is not a one-off identity check, it is an ongoing customer risk process. The core job is to establish who the customer is, whether they can be accepted under the firm’s policy, and what level of scrutiny the relationship needs as it moves forward.

That usually means confirming identity details, understanding beneficial ownership where relevant, and collecting enough context to judge whether the customer’s expected activity fits the stated profile. The better the initial assessment, the easier it is to spot when later behaviour looks inconsistent.

Why CDD Matters to AML and Sanctions Controls

CDD sits at the front end of financial crime control because weak onboarding decisions create blind spots that persist for the life of the relationship. It supports anti-money laundering, sanctions compliance, fraud prevention, and suspicious activity detection by giving the organisation a baseline against which later activity can be compared.

Where the customer profile is incomplete or inaccurate, unusual payments, ownership structures, geography, or transaction patterns may not stand out soon enough. That is why CDD is closely tied to screening, risk rating, and escalation decisions rather than treated as a formality.

For a formal global baseline on why customer due diligence is part of the AML/KYC control stack, see the FATF Recommendations, AML and KYC Framework.

CDD Checks, Monitoring, and Escalation Triggers

Effective CDD does not stop at account opening. It typically extends into periodic refresh, event-driven review, and transaction monitoring so the organisation can detect when the customer no longer matches the original risk assumption.

Typical escalation triggers include inconsistent identity data, opaque ownership, adverse media, sanctions proximity, unusual source of funds, or activity that does not fit the expected business model. At that point, the issue is often not just data quality, but whether the relationship should move to enhanced due diligence, tighter review, or restriction.

The practical point is that CDD only works when the firm can connect onboarding evidence, customer risk scoring, and ongoing monitoring into one lifecycle rather than separate silos.

For a deeper walkthrough of who to check and how to handle triggers, CDD, EDD, PEP and sanctions screening covers the operational decision points behind the control.

CDD and the Identity Evidence Behind Customer Risk

CDD is sometimes described as an AML control, but at its core it depends on identity evidence. The business must know enough about the person or entity to distinguish legitimate customers from higher-risk, misrepresented, or concealed relationships, especially where beneficial ownership or control is not obvious.

That makes document quality, verification strength, and record consistency important. If the identity basis is weak, every downstream judgment, from risk rating to sanctions screening, becomes less reliable. In practice, CDD is strongest when it is treated as evidence-driven risk assessment rather than a checkbox exercise.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-53 Rev 5, CIS Controls v8 and NIST CSF 2.0 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5IA-8 — Identification and Authentication (Non-Organizational Users)CDD verifies customer identity before and during a business relationship.
AC-2 — Account ManagementCDD supports customer lifecycle decisions, including opening, review, restriction, and closure.
Recommendation — Apply IA-8 to verify external customer identities before granting account access. Use AC-2 to govern customer account creation, review, and removal decisions.
ISO/IEC 27001:2022A.5.16 — Identity managementCDD relies on maintaining reliable identity records for customers and beneficial owners.
Recommendation — Establish identity management processes to keep customer records accurate and current.
CIS Controls v8CIS-5 — Account ManagementCDD aligns with managing who is onboarded, reviewed, and removed from customer systems.
Recommendation — Implement account management controls to review and restrict customer access consistently.
NIST CSF 2.0PR.AA-01 — Identities and credentials are issued, managed, verified, revoked, and audited for authorized users, devices, and services.CDD depends on verified identity evidence and lifecycle review for customer relationships.
Recommendation — Manage customer identities and related evidence through issuance, verification, and revocation processes.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 3, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org