Organisations should align customer due diligence with the Danish rules for remote onboarding, using risk-based identity verification, document checks, and ongoing monitoring. The practical aim is to confirm who the customer is, understand the purpose of the relationship, and detect unusual patterns early. Controls should be proportionate to the customer risk, product risk, and delivery channel, especially when no in-person interaction occurs.
What customer due diligence must establish in a remote Danish onboarding flow
For non-face-to-face relationships, the core task is not just collecting an ID image, but building enough assurance that the person or entity opening the relationship is real, reachable, and appropriate for the stated risk profile. That means the file should show how identity was verified, how the relationship purpose was understood, and why the chosen checks were sufficient for the channel.
In practice, remote due diligence needs to answer three questions: who is the customer, why are they here, and does anything about the application look inconsistent with the expected risk. If any one of those remains weakly evidenced, the relationship should be treated as higher risk until the gap is closed.
For remote identity evidence, teams should rely on more than one check where the risk is higher, especially when onboarding is entirely digital. NHIMG’s Identity Proofing and KYC Guide is useful here because it separates document checks, liveness, and presentation-attack resistance from the broader onboarding decision.
How to calibrate controls to customer, product, and channel risk
A risk-based approach is the practical centre of gravity. Low-value, low-complexity relationships may justify lighter checks, but remote onboarding can also hide impersonation, synthetic identity, document tampering, and mule activity, so the control set should scale with the likelihood and impact of misuse.
One useful way to structure the review is to score the customer, the product, and the delivery channel separately. A simple consumer relationship with limited functionality is not the same as a business customer requesting faster payments, cash-like movement, or authority over multiple accounts. The channel matters because the absence of face-to-face interaction removes a natural authenticity check and increases dependence on document, device, and behavioural evidence.
Customer due diligence also needs a sanctions and PEP lens where the relationship or ownership structure warrants it. NHIMG’s CDD, EDD, PEP and sanctions screening is relevant because it shows how the onboarding decision depends on screening quality, match handling, and when enhanced checks are justified.
What ongoing monitoring should look for after onboarding
Remote onboarding should not be treated as a one-time verification event. Ongoing monitoring is what turns initial due diligence into a living control, especially when customer activity, device patterns, payment behaviour, beneficial ownership, or account access changes after approval.
The most important signal is inconsistency: transactions that do not fit the stated purpose of the relationship, repeated failed verification attempts, abrupt changes in device or location patterns, or account behaviour that suggests the original identity evidence may have been borrowed or fabricated. Where such signals appear, teams should be ready to refresh due diligence, not just open an alert and move on.
Risk and Threat Considerations
Remote onboarding weakens the natural assurance that comes from seeing the customer in person, so the main risk is identity misuse rather than just incomplete paperwork. If document checks, liveness testing, or purpose-of-relationship checks are shallow, organisations can approve accounts that later support fraud, laundering, or account takeover.
Failure mechanism: An attacker can combine stolen or fabricated identity evidence with a channel that never requires physical presence, then use the approved relationship to pass initial controls and establish a foothold for later misuse.
Impact: The organisation may onboard the wrong customer, miss unusual activity until after value has moved, and face remediation work across verification, monitoring, and possible account closure.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-63, NIST CSF 2.0 and CIS Controls v8 set the technical controls, while GDPR and ISO/IEC 27001:2022 define the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-63 | IAL — Identity Assurance Levels | Remote onboarding hinges on assurance strength for identity proofing and verification. |
| Recommendation — Set assurance levels by customer risk and require stronger proofing when remote evidence is weaker. | ||
| NIST CSF 2.0 | PR.AA-05 — Assets are authenticated commensurate with risk before gaining access | Customer onboarding is an access decision that should scale authentication to risk. |
| Recommendation — Align onboarding checks to the risk of the relationship before approving access. | ||
| CIS Controls v8 | CIS-5 — Account Management | CDD depends on strong account lifecycle controls, verification, and review of access changes. |
| Recommendation — Tie customer account creation and changes to verified identity and periodic review. | ||
| GDPR | Art. 5 — Principles relating to processing of personal data | Remote CDD processes personal data and must be limited, accurate, and purpose-bound. |
| Recommendation — Minimise collected identity data and keep it accurate, relevant, and purpose-specific. | ||
| ISO/IEC 27001:2022 | A.5.16 — Identity management | Identity management supports verifying who a remote customer is and governing that identity lifecycle. |
| Recommendation — Define identity proofing, approval, and review steps for remote customer onboarding. | ||
Practitioner Guidance
What to verify: Before trusting a remote onboarding decision, verify that the evidence trail shows how identity was checked, how the customer’s purpose was assessed, and why the level of assurance matched the risk. If the file only proves document collection, it is not yet a strong due diligence outcome.
Decision rule: If the customer profile, product use case, or channel raises the chance of impersonation or misuse, escalate to enhanced due diligence rather than trying to compensate with more of the same low-value checks. If the activity later deviates from the stated purpose, treat that as a trigger to revisit the original onboarding decision.
Practitioner takeaway: Remote due diligence works best when organisations treat onboarding as an evidence-based risk decision, not a form-filling exercise, and keep enough monitoring in place to catch when the original assurance no longer matches reality.
Related resources from NHI Mgmt Group
- How should compliance teams approach customer identification and due diligence for non-face-to-face business relationships in Latvia?
- How should organisations approach customer identification and due diligence for non-face-to-face business relationships in Argentina?
- How should organisations handle customer identification and due diligence for non-face-to-face business relationships in Thailand?
- How should organisations structure customer identification and due diligence for non-face-to-face business relationships in Germany?
Deepen Your Knowledge
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.
Reviewed and updated by the NHIMG editorial team on November 5, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org