By NHI Mgmt Group Editorial TeamBased on CertiK: “Policy Pulse” (October 8, 2026)

TL;DR: September 2026 showed regulators moving ahead of Congress on digital asset oversight, according to CertiK, while the U.S. SEC’s proposed Regulation Crypto Assets framework and the CLARITY Act debate kept market structure, tokenized stocks, and enforcement in focus. The practical lesson is that governance, controls, and auditability now matter as much as policy positioning.


At a glance

What this is: This is CertiK’s September 2026 Policy Pulse roundup on U.S. digital asset regulation, centered on the gap between congressional action and regulator momentum.

Why it matters: It matters because firms building or operating in Web3 need to track how oversight, market structure, and security expectations are converging into operational control requirements.


Context

September 2026 was not a single-policy story. It was a signal that digital asset governance is being shaped by several overlapping tracks, including congressional drafting, regulator guidance, and institutional security expectations. For practitioners, that means compliance planning can no longer rely on a single legislative outcome or a narrow legal interpretation.

The primary governance gap is coordination. When market structure, enforcement, and security oversight evolve on different timelines, firms have to align controls before the final rulebook settles. That is especially relevant where digital assets intersect with custody, operational resilience, AML, and the identity and access controls that underpin regulated platforms.


Key questions

Q: How should digital asset firms respond when regulation changes faster than legislation?

A: They should design control frameworks that can absorb shifting interpretations without reworking core governance each time. That means defining accountable owners, maintaining evidence for custody and access decisions, and building policies that can map to multiple regulatory regimes. The goal is operational portability, not waiting for legal certainty before improving control maturity.

Q: Why do custody and access controls matter so much in crypto regulation?

A: Because regulated digital asset services depend on provable control over who can move assets, approve exceptions, and alter critical settings. If privileged access is loose or poorly evidenced, the firm may satisfy a paper policy but still fail a supervisory review. In practice, control quality becomes part of regulatory credibility.

Q: What governance gaps do digital asset regulators usually look for?

A: They look for missing ownership, weak audit trails, unclear approval authority, and poor linkage between policy and real-world controls. Those gaps matter because they show the firm cannot reliably explain how it protects customer assets or enforces accountability. Strong governance is visible in records, not only in statements.

Q: Should firms build one compliance model for all crypto jurisdictions?

A: No. A single model can create false confidence if it only matches one regulator’s expectations. Firms should instead build a core governance baseline that can be adapted by jurisdiction, then document where local rules require stricter evidence, controls, or reporting. That approach reduces rework and limits supervisory surprises.


Technical breakdown

Why digital asset regulation now depends on security controls

Digital asset policy is no longer limited to classification or market structure. Once regulators focus on oversight, resilience, and consumer protection, the practical question becomes whether firms can demonstrate control over access, operational risk, and incident handling. That shifts the burden from legal interpretation alone to evidence of secure operations, audit trails, and dependable governance across the full asset lifecycle.

Practical implication: Practitioners should treat policy tracking as a control-design exercise, not just a legal watch item.

How oversight converges with custody, AML, and access governance

Digital asset businesses often sit across multiple control domains at once. Custody creates operational resilience demands, AML creates traceability demands, and platform access creates identity governance demands. When those domains are regulated separately, gaps appear in handoffs, especially where privileges, transaction approvals, and exception handling are not tied together in a single governance model.

Practical implication: Teams should map regulatory obligations to the specific controls that prove custody integrity, access accountability, and transaction oversight.

What the policy shift means for identity and trust controls

Even though this article is about regulation, the identity angle is real: regulated crypto services depend on accountable human access, privileged approvals, and tightly governed machine or service credentials. If those identities are not lifecycle-managed, the organisation cannot credibly show who can move assets, approve exceptions, or alter operational settings. In that sense, governance failures become compliance failures.

Practical implication: Security and compliance teams should align identity governance with the controls they expect to evidence to regulators.


NHI Mgmt Group analysis

Regulatory fragmentation is now a security governance problem, not just a policy inconvenience. When Congress, the SEC, and other authorities move on different timelines, firms cannot wait for one final framework to justify control design. The practical effect is that digital asset firms must build governance that can survive changing interpretations. Practitioners should treat fragmented regulation as a reason to harden control evidence early.

Digital asset oversight is converging on operational proof, not narrative compliance. Regulators increasingly care about whether firms can show resilient controls, traceable approvals, and credible access governance. That makes board-level statements less important than demonstrable operating evidence. Practitioners should expect audits and examinations to reward control maturity over policy language.

Identity governance is becoming a hidden dependency of crypto regulation. Custody, transaction approvals, and exception handling all rely on accountable identities, yet many firms still separate compliance reporting from identity lifecycle governance. That split will not hold under closer scrutiny. Practitioners should connect privileged access, service accounts, and approval workflows to the regulatory evidence model.

Policy uncertainty is accelerating control standardisation across the sector. When the market cannot rely on a single legislative path, it tends to converge on repeatable internal controls that satisfy multiple regimes at once. That is the direction digital asset oversight appears to be heading. Practitioners should design for control portability across jurisdictions, not one-off compliance wins.

What this signals

Digital asset regulation is moving toward evidence-based governance. Firms should expect more scrutiny of operational controls, not just policy documents, especially where custody, approvals, and recovery intersect. That makes identity governance a compliance dependency rather than a separate IT concern.

The next planning step is to map each regulatory obligation to a control owner and an auditable artefact. If the firm cannot show who approved access, who can move assets, and how exceptions are tracked, the control story will be weak regardless of the legal stance.


For practitioners

  • Map policy changes to control owners Assign ownership for custody, AML, resilience, and access governance so regulatory changes translate into named control updates rather than ad hoc response.
  • Document evidence for operational resilience Maintain audit-ready records for privileged approvals, exception handling, incident response, and recovery testing because these are the artefacts regulators will ask for.
  • Align identity governance with regulated workflows Tie human approvals, privileged roles, and service credentials to the transaction and custody workflows they can affect, then review those mappings on a fixed cadence.
  • Track jurisdiction-specific control expectations Compare U.S. developments with other regulatory regimes to avoid building a compliance model that only works in one market.

Key takeaways

  • Digital asset oversight is increasingly defined by how well firms can prove operational control, not by how neatly they describe their policies.
  • The main governance risk is fragmentation between congressional action, regulator guidance, and internal control ownership.
  • Identity, custody, and audit evidence need to be managed together if crypto firms want durable compliance across jurisdictions.

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 and NIST SP 800-53 Rev 5 set the technical controls, while ISO/IEC 27001:2022 and DORA define the regulatory obligations.

FrameworkControl / ReferenceRelevance
NIST CSF 2.0GV.OC-01 — Organisational ContextThe article is about regulatory context shaping governance and control design.
GV.RM-01 — Risk Management StrategyThe piece stresses aligning controls to shifting regulatory risk.
PR.AA-05 — Access Permissions, Entitlements and AuthorizationsAccess governance underpins custody and regulated workflow accountability.
Recommendation — Map digital asset obligations to organisational context so policy changes translate into owned controls. Align crypto compliance planning to a documented risk strategy that can absorb regulatory change. Review privileged and service access so approvals and asset movements remain attributable.
NIST SP 800-53 Rev 5AC-6 — Least PrivilegeLeast privilege directly supports the identity governance issues raised by regulated crypto operations.
Recommendation — Enforce least privilege across custody, approval, and administrative paths to reduce compliance exposure.
ISO/IEC 27001:2022A.5.15 — Access controlAccess control is central to proving who can act within regulated asset workflows.
Recommendation — Document and enforce access control requirements for all regulated crypto workflows.
DORAArticle 9 — ICT risk managementOperational resilience and ICT governance are explicit themes in the article.
Recommendation — Use ICT risk management to evidence resilience across custody, approvals, and recovery processes.

Key terms

  • Regulatory Fragmentation: Regulatory fragmentation is the condition where legal and compliance obligations differ across countries, sectors, and use cases. For technology companies, it creates overlapping requirements that are hard to map into one internal control model, increasing operational burden and the chance of inconsistent or incomplete compliance.
  • Operational Resilience: Operational resilience is the ability to keep critical services running or recover them quickly after disruption. In identity-led environments, that depends on authentication services, privilege management, and recovery procedures that can be tested under realistic failure conditions.
  • Identity Governance: Identity governance is the set of controls that defines who approves access, who owns it, how it is reviewed, and when it is removed. In practice, it turns identity management from a deployment task into a durable control system that can withstand audits, organisational change, and operational growth.

Deepen your knowledge

NHI Foundation Level course, the industry's only accredited NHI security programme, covers NHI governance, machine identity security, and secrets management. It helps security and compliance practitioners connect identity controls to the evidence regulators expect.
NHIMG Editorial Note
Published by the NHIMG editorial team on October 16, 2026.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org