Special Measures under Section 311 of the USA PATRIOT Act let U.S. authorities designate a foreign financial institution, class, or jurisdiction as a primary money laundering concern. The result can restrict or sever access to the U.S. financial system and force stronger due diligence across correspondent and payment flows.
Expanded Definition
Special Measures under Section 311 are a U.S. financial crime tool that sits between supervisory pressure and full exclusion from the market. They allow authorities to treat a foreign financial institution, class, or jurisdiction as a primary money laundering concern and then impose targeted restrictions, enhanced recordkeeping, or correspondent banking limits. In practice, the measure is not a generic sanctions label. It is a risk-based intervention aimed at interrupting laundering pathways, payment opacity, and weak controls in cross-border finance. For governance teams, the key issue is scope: the designation can attach to one institution, an entire class of entities, or a jurisdiction, so remediation often extends beyond the named party. Public compliance expectations around customer identification, due diligence, transaction monitoring, and escalation are often shaped by broader control principles reflected in NIST SP 800-63 Digital Identity Guidelines and NIST SP 800-53 Rev 5 Security and Privacy Controls, even though Section 311 itself is a financial integrity mechanism rather than an identity standard. The most common misapplication is treating Section 311 as if it were a conventional sanctions designation, which occurs when organisations apply blanket blocking rules without first understanding the specific measure, scope, and compliance obligation.
Examples and Use Cases
Implementing Section 311 responses rigorously often introduces correspondent-banking friction, requiring institutions to weigh faster de-risking against continued access to legitimate cross-border payments.
- A bank flags incoming payments from a jurisdiction subject to enhanced Section 311 scrutiny and applies stricter onboarding, source-of-funds checks, and transaction review.
- A correspondent institution reassesses whether to maintain a relationship with a foreign bank after receiving notice of special measures that limit payable-through activity.
- A compliance team updates its financial crime controls to require senior approval for new counterparties linked to a designated class of institutions.
- A payments provider strengthens monitoring for nested relationships and indirect exposure when a lower-tier institution connects to a named foreign bank.
- A risk function documents why a customer or intermediary was subject to additional due diligence rather than automatic account closure, preserving auditability and escalation logic.
These use cases show that Section 311 is often about control precision, not just refusal. A well-run program distinguishes between direct exposure, indirect exposure, and no material exposure, then applies proportionate controls rather than defaulting to indiscriminate blocking. That distinction matters because overreaction can sever legitimate trade flows, while underreaction can leave the institution exposed to money laundering risk and regulatory criticism. For teams building financial crime governance, the practical question is how quickly monitoring logic can detect a newly designated counterparty and route it to escalation without relying on manual interpretation alone.
Why It Matters for Security Teams
Section 311 matters because it can create rapid operational change across onboarding, payments, screening, and third-party risk management. If a foreign institution or jurisdiction is designated, security and compliance teams may need to update rules, tune monitoring thresholds, adjust correspondent access, and preserve evidence that the institution acted promptly. The governance challenge is not just policy enforcement; it is traceability. Teams must be able to explain why a relationship was restricted, what review occurred, and which controls were applied at each stage. That is why control discipline from frameworks such as NIST SP 800-63 Digital Identity Guidelines and NIST SP 800-53 Rev 5 Security and Privacy Controls is useful when designing identity proofing, access governance, logging, and escalation workflows that support financial crime response. Section 311 also has an identity-adjacent dimension: correspondent banking depends on trusted counterparties, verified entities, and accountable access to financial infrastructure. Organisations typically encounter the operational cost only after a designation forces rapid de-risking, at which point Section 311 becomes operationally unavoidable to address.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST CSF 2.0, NIST SP 800-53 Rev 5 and NIST SP 800-63 set the technical controls, while DORA and NIS2 define the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST CSF 2.0 | GV.RM-01 | Risk governance supports response to designated financial crime exposure. |
| NIST SP 800-53 Rev 5 | AU-2 | Audit events and records support traceability for compliance actions. |
| NIST SP 800-63 | IAL2 | Identity assurance informs stronger due diligence and entity verification. |
| DORA | Operational resilience planning helps absorb abrupt restrictions on financial connectivity. | |
| NIS2 | Governance and incident handling principles support escalation and accountability. |
Increase verification rigor for counterparties and beneficial owners before permitting access.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Reviewed and updated by the NHIMG editorial team on August 24, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org
