Join our Newsletter — 33% off our NHI Course
Home› FAQ› Governance, Ownership & Risk› How should financial institutions evaluate cryptocurrency exposure without…
Governance, Ownership & Risk

How should financial institutions evaluate cryptocurrency exposure without weakening fraud and compliance controls?

← Back to all FAQ
By NHI Mgmt Group Editorial Team Updated November 2, 2026 Domain: Governance, Ownership & Risk

Financial institutions should evaluate cryptocurrency exposure through the lens of transaction risk, customer protection, sanctions screening, and operational oversight. The right response is not blanket adoption or rejection. Teams need clear rules for wallet monitoring, suspicious activity review, custody decisions, and auditability so they can support legitimate use while limiting illegal payments, theft, and financial instability.

How to frame cryptocurrency exposure as a control decision

Financial institutions should treat cryptocurrency as a controlled exposure question, not a binary policy choice. The practical issue is whether the activity can be monitored, screened, explained and reviewed with the same discipline used for other high-risk payment flows. That means defining what is permitted, what requires enhanced review, and what evidence must exist before activity is allowed.

Exposure assessment should start with the business model and then move to control fit. If the institution cannot tie a crypto-related activity to customer due diligence, transaction monitoring, sanctions review and escalation ownership, the exposure is usually too loose for a regulated environment. If those controls exist, the question becomes whether they are strong enough for the added speed, pseudonymity and irreversibility of the asset flow.

That is why institutions should separate “can we support this activity?” from “can we control it safely at scale?” Wallet monitoring, suspicious activity review, custody choices and audit trails are not optional add-ons, they are the evidence that the exposure is being governed rather than merely tolerated. FinCEN remains a useful reference point for the AML and suspicious activity expectations that typically shape that control design.

Where fraud and compliance controls tend to weaken

The main weakness is control drift. Teams often approve a crypto use case for strategic reasons, then relax the manual checks that were originally intended to make the activity defensible. Once that happens, transaction monitoring becomes inconsistent, sanctions screening becomes narrower than the risk warrants, and case review loses the context needed to distinguish legitimate customer behaviour from abuse.

Another common failure mode is assuming that custody or platform choice solves the problem. It does not. Even when the technical custody model is sound, fraud can still enter through onboarding, account takeover, mule activity, false source-of-funds claims or payment redirection. That is why fraud controls, compliance controls and operational oversight need to be evaluated together, not as separate workstreams.

For many institutions, the question is also about change control. New crypto products, new wallet providers and new third-party integrations can expand exposure faster than policies, logging and investigation playbooks are updated. The right response is to keep the control boundary visible and to require explicit sign-off when a new use case changes how funds move, who can authorise them or how they are traced after settlement. The GLBA Safeguards Rule Guide is a useful benchmark for thinking about how financial institutions tie risk assessment to protective controls, while the MAS Technology Risk Management Guide is helpful where board oversight, access control and incident accountability need to be made explicit.

What good crypto governance looks like in practice

Good governance starts with clear approval criteria. Institutions should define which crypto activities are allowed, which are prohibited and which require enhanced due diligence, then make those rules visible to operations, compliance and fraud teams. The strongest programmes do not rely on informal judgement, they use documented thresholds for wallet monitoring, sanctions screening, customer review and exception handling.

Auditability is the other non-negotiable. If a transaction, wallet relationship or custody decision cannot be reconstructed later, the institution will struggle to defend it to regulators, auditors or internal reviewers. That makes logging, evidence retention and review ownership part of the control itself, not merely a technical implementation detail. The FATF Recommendations are the most relevant external baseline for customer due diligence, suspicious activity reporting and virtual asset oversight.

Controls should also be proportionate to the use case. A retail-facing feature, an institutional custody arrangement and a treasury exposure are not the same risk, even if they all involve cryptocurrency. Practitioners should therefore distinguish between customer-facing monitoring, internal treasury controls and third-party provider oversight, because each one fails in a different way and each one needs a different review cadence. The CIS Controls Guide is a practical reference when translating that governance into repeatable safeguards.

Risk and Threat Considerations

Cryptocurrency exposure increases the risk of payment fraud, sanctions violations and weak traceability if institutions treat it as a novelty instead of a regulated funds movement problem. The same exposure can also create operational risk when custody, screening and exception handling are split across teams that do not share a common decision trail.

Failure mechanism: Control weakening usually occurs when new crypto flows are approved without extending the existing fraud review, sanctions screening and audit logging expectations to match the new payment path.

Impact: That creates room for illegal payments, stolen funds, mule activity and regulatory findings, while also making it harder to prove that the institution acted consistently and in good faith.

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 and CIS Controls v8 set the technical controls, while ISO/IEC 27001:2022 and DORA define the regulatory obligations.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5AU-6 — Audit Review, Analysis, and ReportingCrypto exposure must remain explainable through reviewable transaction evidence and exception handling.
Recommendation — Review audit trails and exception logs to verify crypto activity is traceable and reviewable.
CIS Controls v8CIS-8 — Audit Log ManagementMonitoring, investigation and accountability depend on retaining logs for wallet and payment activity.
Recommendation — Centralise and retain logs for crypto-related transactions and review activity.
ISO/IEC 27001:2022A.5.7 — Threat intelligenceThreat-led assessment is needed to track fraud, sanctions evasion and abuse patterns around crypto.
Recommendation — Use threat intelligence to update fraud and compliance controls for emerging crypto abuse patterns.
DORAICT third-party risk management — ICT third-party risk managementCrypto custody and monitoring often rely on external providers whose resilience affects financial control.
Recommendation — Assess third-party custody and monitoring providers as part of operational resilience oversight.

Practitioner Guidance

What to prioritise: Start with transaction monitoring, sanctions screening and source-of-funds logic before debating product expansion. If those three are not clearly designed for the exact crypto use case, the control model is not ready.

What to verify: Confirm that the institution can trace wallet relationships, review suspicious activity, evidence approval decisions and escalate exceptions without relying on tribal knowledge. If any of those steps depend on one team or one person, the exposure is too fragile.

Decision rule: If the crypto activity changes how funds are received, moved, held or redeemed, require a formal control review and keep the activity in a heightened-review state until the review is complete. Invoice Redirection and Supplier Bank Detail Fraud Guide is a useful analogue for the verification mindset, because the same discipline applies when a payment path or payee relationship changes.

Practitioner takeaway: The safest evaluation posture is not “approve crypto” or “ban crypto”, it is to prove that fraud, sanctions and audit controls still work when the payment path becomes harder to reverse, trace and explain.

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 2, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org