By NHI Mgmt Group Editorial TeamBased on CertiK: “From Rulebook to Roadmap: CertiK and Coins.ph on Brazil's New Rules for Virtual Asset Service Providers” (August 24, 2026)

TL;DR: Brazil’s emerging virtual asset framework is shifting compliance from a checkbox to an operating test for VASPs, according to CertiK, with regulators, operators and security providers expected to align on infrastructure, on-chain monitoring, incident response and local legal readiness. The decisive issue is no longer whether regulation exists, but whether governance, security and evidence can support market entry at scale.


At a glance

What this is: This is a discussion of Brazil’s virtual asset regulatory direction, with CertiK arguing that prepared operators will be separated by compliance evidence, infrastructure strength, monitoring and incident readiness rather than by a single rule.

Why it matters: For IAM, NHI and broader security practitioners, the lesson is that regulated market entry now depends on proving governance across access, operations and response, not just on meeting a policy checklist.

By the numbers:

  • About 70% of large institutions have some digital asset developments within their companies.

Context

Brazil’s virtual asset regime is becoming a practical governance test for regulated operators, especially where compliance, operational security and market access intersect. In that setting, the question is not whether a company can state a policy, but whether it can demonstrate the controls, evidence and response capability that regulators and institutional partners expect.

For identity and access practitioners, this matters because regulated entry is increasingly tied to proving who can act, what they can access and how quickly the organisation can contain incidents. That makes the governance layer as important as the technical stack, particularly when operations span cloud infrastructure, transaction monitoring and legal response.


Key questions

Q: How should security teams prove readiness for a regulated market entry?

A: They should show that compliance, infrastructure, monitoring and response work together as one operating model. Regulators and institutional partners usually want evidence that controls are localised, tested and owned, not just written down. The strongest programmes can explain who can act, how activity is monitored and what happens when an incident requires escalation.

Q: What breaks when compliance is treated as a checkbox in virtual asset markets?

A: The organisation usually discovers too late that policy does not equal operational readiness. Infrastructure may not scale locally, monitoring may not support oversight and incident response may not be able to handle reporting or asset freezing. That gap turns compliance into a business risk, not just a legal one.

Q: How do security teams know whether regulated market controls are actually working?

A: Look for evidence that controls can support real operations, not just pass a review. Good indicators include clear ownership, local infrastructure that performs under load, continuous transaction visibility and response procedures that can be executed without improvisation. If those elements are missing, readiness is probably overstated.

Q: Who is accountable when a VASP enters a regulated market without enough evidence?

A: Accountability sits with the business leadership that chose the operating model, but it extends into compliance, security and legal functions because each owns part of the evidence chain. In regulated markets, weak coordination across those teams can delay approvals, damage trust and create enforcement exposure.


Technical breakdown

Why regulatory clarity changes the control model for virtual asset firms

Regulatory clarity changes the control model because compliance stops being a static declaration and becomes a continuous operating condition. Virtual asset firms need to show that policy, infrastructure, monitoring and response are aligned to local requirements, not just globally standardised. In practice, that means governance has to reach into infrastructure resilience, transaction visibility and incident handling, because regulators judge whether the business can operate safely inside the market, not merely whether it can register there. Practical implication: treat regulation as an operational design constraint, not a legal afterthought. Read the Ultimate Guide to NHIs: Regulatory and Audit Perspectives.

Practical implication: Treat regulation as an operational design constraint, not a legal afterthought.

How evidence replaces claims of readiness in regulated market entry

Readiness evidence is broader than compliance documentation. In this case, the panel’s framework points to local compliance, regional infrastructure capacity, on-chain monitoring and incident procedures as separate proof points that together show maturity. That logic mirrors how many regulated ecosystems now assess trust: they want to see working controls, escalation paths and operational ownership, not marketing statements. For security teams, this means evidence must be testable and current, especially where systems can move assets, trigger freezes or involve legal escalation across platforms. Practical implication: build an evidence pack that maps controls to operational outcomes, not just to policies.

Practical implication: Build an evidence pack that maps controls to operational outcomes, not just to policies.

Brazil’s crypto compliance model is becoming a trust framework

Brazil’s emerging model shows how trust in digital asset markets increasingly depends on the combination of compliance, security and incident response. That is not the same as traditional IAM, but the identity lesson is clear: any entity that can move value or trigger action must be governed as a high-risk actor with defined authority and traceability. [[L7|NHI security]] becomes relevant here because the same operational pressure exists for machine-held keys, platform credentials and service accounts supporting trading, custody and monitoring workflows. Practical implication: apply identity governance to every operational actor that can move assets or affect regulated workflows.

Practical implication: Apply identity governance to every operational actor that can move assets or affect regulated workflows.


NHI Mgmt Group analysis

Brazil’s virtual asset rules are turning compliance into a live operating test, not a filing exercise. The article’s central point is that prepared firms will be separated by whether they can run secure infrastructure, monitor activity and respond to incidents inside a regulated market. That is a governance shift, not just a legal one, because the regulator is effectively evaluating operational maturity. Practitioners should read this as a demand for continuous evidence, not one-time compliance.

Operational trust now depends on control proof, not broad market claims. A company entering Brazil has to show local compliance, regional infrastructure strength, on-chain visibility and incident handling that can survive scrutiny. That is structurally similar to how mature security programmes prove access governance: the organisation must demonstrate that authority is bounded, monitored and reversible. For identity teams, the lesson is that regulated workflows need traceable actors, clear ownership and auditable escalation paths.

Brazil is signalling a model where security and compliance are inseparable market-entry requirements. The article describes a market in which regulators, operators and security providers are expected to work together, which means governance now extends beyond internal policy to external accountability. That matters because firms that treat compliance as a legal wrapper around weak operations will struggle to earn institutional confidence. Practitioners should expect market access to depend on both technical controls and explainable governance.

Trust is becoming the product in regulated digital asset markets. The discussion makes clear that security evidence, compliance posture and operational response all contribute to market credibility. That extends the identity governance lesson into the broader crypto stack: every credentialed system, monitoring workflow and incident playbook becomes part of the trust boundary. Practitioners should therefore manage operational identity with the same rigor they apply to financial controls.

What this signals

Market access is becoming a security governance problem as much as a legal one. Firms that enter regulated crypto markets now need controls that can be defended in operational terms, not just policy terms. That means security teams should expect licensing, monitoring and response requirements to shape architecture decisions early, especially where transaction workflows and privileged access are involved.

Operational identity will matter more inside regulated digital asset businesses. Service accounts, platform credentials and monitoring identities that can move value or trigger sensitive actions should be treated as part of the trust boundary. If those identities are not inventoried, scoped and governed, the organisation may be compliant on paper but fragile in practice.

Regulator engagement is now part of resilience planning. When licensing deadlines, supervisory guidance or enforcement expectations change, the security programme must be able to adapt without breaking evidence, ownership or incident response. Teams that build this flexibility early will be better placed to expand into tightly regulated markets without reworking their control model under pressure.


For practitioners

  • Define a market-entry control baseline Map local regulatory obligations to concrete operational controls for infrastructure, monitoring, incident response and legal escalation before launch.
  • Document evidence for readiness reviews Prepare a control evidence pack that shows how compliance, platform resilience and monitoring are actually implemented and tested.
  • Extend identity governance to operational actors Inventory the service accounts, platform credentials and monitoring identities that can move assets or trigger sensitive actions.
  • Build incident procedures for regulatory markets Pre-authorise steps for reporting, asset freezing and legal coordination so response does not depend on ad hoc decisions during a live event.
  • Track regulator communication as a governance input Treat deadline changes, licensing guidance and supervisory feedback as control inputs that can change implementation priorities.

Key takeaways

  • Brazil’s virtual asset framework is pushing firms to prove operational readiness, not just policy compliance.
  • The article highlights four evidence areas that matter most: local compliance, infrastructure, on-chain monitoring and incident procedures.
  • Security and identity governance now shape market access because regulators and partners judge whether controls can be demonstrated under real operating conditions.

Related NHI Mgmt Group resources: Ultimate Guide to NHIs: Regulatory and Audit Perspectives · MDR Guide


Standards & Framework Alignment

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

MITRE ATT&CK addresses the attack surface, NIST CSF 2.0 and CIS Controls v8 set the technical controls, and ISO/IEC 27001:2022 defines the regulatory obligations.

FrameworkControl / ReferenceRelevance
NIST CSF 2.0GV.RM-01 — Risk Management StrategyThe article is about governance decisions that shape regulated market entry and operational risk acceptance.
PR.AA-05 — Access Permissions, Entitlements and AuthorizationsOperational identity and platform access are part of the trust boundary for crypto workflows.
Recommendation — Align market-entry decisions to a documented risk management strategy that connects compliance, security and operations. Review privileged access for transaction, monitoring and response workflows so authority is traceable and bounded.
CIS Controls v8CIS-5 — Account ManagementThe post stresses governed actors and evidence for who can act in regulated environments.
Recommendation — Inventory and govern service and privileged accounts that can move assets or trigger sensitive actions.
MITRE ATT&CKTA0006; TA0040 — Credential Access; ImpactWeakly governed operational identities can enable abuse that disrupts regulated crypto operations.
Recommendation — Map privileged account abuse and operational disruption paths so response plans reflect real attack outcomes.
ISO/IEC 27001:2022A.5.29 — Information security during disruptionThe article emphasises incident handling and continuity under regulatory pressure.
Recommendation — Document disruption-handling procedures that preserve compliance and response capability during incidents.

Key terms

  • Virtual Asset Service Provider: A virtual asset service provider is a business that offers services involving crypto assets, such as exchange, transfer, custody, or related intermediated activity. In practice, VASP classification matters because it determines who must participate in regulated information exchange and which controls govern transfer approval.
  • On-Chain Monitoring: On-chain monitoring is the process of observing blockchain transactions and related activity for risk, compliance, or operational signals. In regulated environments, it must be linked to internal records and escalation workflows so teams can investigate activity, not just observe it.
  • Regulated Market Entry: Regulated market entry is the process of launching or expanding into a jurisdiction with formal supervisory, licensing or reporting requirements. The operational challenge is to align legal, security and infrastructure controls so the business can demonstrate readiness to regulators and partners.
  • Operational Trust Boundary: The set of systems and processes surrounding a transaction that can influence whether a legitimate action becomes a malicious one. In crypto, this includes DNS, front ends, build pipelines, admin panels, and RPC endpoints, all of which can redirect or alter authorised activity.

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 practitioners translate identity controls into evidence-based operating models for regulated environments.
NHIMG Editorial Note
Published by the NHIMG editorial team on October 22, 2026.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org