Crypto Compliance Assessment: Scope, Process and Cost
Part of our guide to crypto regulatory compliance

Quick answer. A crypto compliance assessment maps controls to applicable rules, tests the systems behind them and delivers evidence. No public fixed price exists; in Invadel's November 2026 US index, median published starting prices for single test types run from $4,950 to $9,750.
Video transcript
Licence files and exams ask for proof that controls work. A crypto compliance assessment produces that proof before a reviewer asks.
It has three layers: a gap analysis against the rules, control tests, and evidence that each control works.
Scope follows what you run. MiCA wants documented ICT security, DORA expects scanning and code testing, and Part 500 and VARA call for yearly pentests.
Once counsel sets the legal perimeter, Guardian's published process runs in four stages: scope, review and test, fix and retest, then deliver.
Each requirement should trace to a control, a test and a dated artifact, with findings, owners, retest results and risk acceptance records.
No public fixed price exists. In Invadel's November 2026 U.S. index, median starting prices for single test types run from four thousand nine hundred fifty to nine thousand seven hundred fifty dollars.
Invadel, which sells pentests, says these are starting points for a small, defined scope. Treat each as a floor. Wallet login, withdrawals, signing and requirement mapping all add work.
Quotes move with surfaces and roles, custody and signing, smart contracts, third parties, regimes, deadline and retest rounds.
Run one before a licence filing, an exam, a launch or material change, and on each regime's annual cadence.
Read the full guide, or talk to Guardian about testing the systems behind your licence file and mapping the evidence.
Why It Matters Now
Licence files and exams ask for proof that controls work, not only policies that describe them. An assessment produces that proof before a reviewer asks.
Review clocks are short. MiCA authorities check a CASP file for completeness within 25 working days, then decide within 40 working days of a complete file.[1]
DORA has applied since 17 January 2025. In New York, DFS guidance of 10 September 2026 expects documented, repeatable risk assessments.[2, 3]
This guide covers the assessment itself: scope, workflow, evidence and price. Regulator fees and capital sit in our MiCA license cost and VARA license cost guides.
Where this article discusses regulation, it covers the technical and security side only. It is not legal advice; confirm how the rules apply to you with counsel.
What It Covers
An assessment is a scoped review against your activities, systems, markets and the regimes that apply. Its scope follows what you run, not a fixed checklist.[4]
It has three layers: a gap analysis against the rule text, tests of the controls, and evidence that each control works.
The gap analysis reads each provision as a demand. MiCA Article 62 asks applicants for governance, internal control and risk procedures, business continuity and ICT security documentation.[5]
ESMA's 31 January 2025 supervisory briefing to national authorities covers governance, substance, outsourcing and staff. ESMA says it helps supervisors and applicants turn MiCA and RTS obligations into concrete controls and checks.[6]
Control testing then checks whether those controls hold under attack, in configuration and in operation. The table shows what that means in four regimes.
Our crypto regulatory compliance guide compares the security rules of more regimes side by side.
| Regime | What the review reads | Tests it implies |
|---|---|---|
| MiCA | Article 62 file: governance, controls, continuity, ICT security | Evidence the described ICT controls exist and work |
| DORA | ICT risk standards: assets, vulnerabilities, patching, code review | Risk-based scans and patching; static and dynamic code testing |
| NYDFS Part 500 | 500.5 vulnerability management; 500.9 risk assessment | Annual internal and external pentests; risk-based scans; exemptions under 500.19(a) |
| VARA | Technology rulebook, Testing and Audit | Independent yearly pentests; smart contract audits where relevant |
How It Runs
Settle the legal perimeter first. Which regimes apply, and through which route, is for your counsel and compliance team to decide before scoping.[4]
Then the review runs in stages, each feeding the next. Guardian's published process uses the four below.
Scoring needs a written method. DFS expects inherent and residual risk, a link from each risk to a control or compensating control, and recorded risk acceptance.[3]
For the 500.9 file itself, our NYDFS risk assessment template gives a scoring scale and register columns.
Under DORA, keep routine resilience testing apart from threat-led penetration testing. The advanced test applies only to selected entities.[2]
- Scope: agree activities, markets, systems, requirements and the deadline, and set test boundaries and the evidence list.
- Review and test: read documents and configurations, interview system owners, run the agreed tests and record what each finding means for each requirement.
- Fix and retest: engineers fix, testers confirm, and each unresolved issue gets a responsible team.
- Deliver: hand over the mapped pack and walk the compliance team through it.
What You Receive
A reviewer should be able to trace each requirement to a control, a test and a dated artifact. Agree the deliverable list at scoping, in writing.
DFS recommends a risk register that records results, tracks remediation and documents changes to residual risk over time.[3]
VARA expects documented evidence of its required testing to be available to it. Version and date every report in the pack.[7]
Policies sit beside the pack, not inside it. Our crypto compliance manual template gives one row per requirement to link them.
- Control-to-requirement matrix, one row per provision in scope.[4]
- Asset and dependency scope, including third parties and concentration points.
- Methodology, scope boundaries and test dates for each test.
- Risk-ranked, reproducible findings with remediation guidance.
- Remediation owners, target dates and retest results.
- Risk acceptance records for anything left open, with the approver.
- An executive summary for management and the board.
- An indexed evidence pack for your regulator, external assessor or partner.
Crypto Compliance Review Cost
Invadel's US index, checked 8 November 2026, covers 184 firms. Only 36 publish prices for human-led testing.[8]
Invadel, which sells pentests and leaves its own prices out of the medians, says published prices are starting points for a small, defined scope. Treat each as a floor for one surface.
Crypto scope sits above that floor. Wallet login, withdrawals, signing services and requirement mapping are all extra work.
Our Web3 pentest cost guide found no credible public price list for crypto-specific testing, only scattered anchors.[9]
These factors move an assessment quote:
- Surfaces: each application, API, cloud account and environment is its own test.[4]
- Roles: testers try every function at every privilege level.
- Custody and signing: running your own stack adds key generation, approvals, backups and recovery to test.
- Smart contracts: each relevant contract adds an audit or source code review.[7]
- Third parties: custodians, cloud and RPC providers need review and concentration analysis.[3]
- Source access: it adds reading time, but lets testers confirm every user-reachable function was covered.
- Regimes: each extra framework adds mapping, even when one test answers several rules.
- Deadline: a fixed submission date compresses the schedule and limits retest time.
- Retest rounds: each fix-and-retest cycle adds effort.
| Scope | Median published starting price | Firms publishing |
|---|---|---|
| Web application | $4,950 | 14 |
| API | $7,950 | 3 |
| Cloud | $9,750 | 12 |
| Compliance pentest package | $6,750 | 4 |
When You Need One
Four moments justify a review.
Several regimes at once? Set the calendar to the strictest cadence and reuse one test plan. Our NYDFS Part 500 penetration testing guide shows how to scope the annual test.
Fix known gaps before testing starts, so fewer findings need a retest.
- Before a licence filing: MiCA information requests can pause the assessment for up to 20 working days.[1]
- Before a regulator exam: arrive with dated test results and closed findings, not open questions.
- Before launch or a material change: VARA requires testing before new systems or products; DFS requires prompt scans after material changes.[7, 10]
- On the regime's cadence: Part 500 pentests and risk assessments, and VARA testing, recur at least annually.
Scope a compliance assessment before you file
Guardian tests the applications, APIs, infrastructure, custody and privileged access behind your licence file, retests the fixes and maps the evidence to the rules in scope.
Frequently Asked Questions
Is a compliance assessment the same as a SOC 2 report or ISO 27001 certificate?
No. An assessment tests controls against regulatory requirements and supplies evidence. SOC 2 attestations and ISO 27001 certification need their own appointed providers. Our SOC 2 cost guide covers what that audit adds to the budget.[4]
Does the DFS risk assessment letter create new obligations?
No. DFS says its 10 September 2026 guidance creates no new obligations. It explains how DFS expects the existing 500.9 assessment to be run and used, which makes it a practical yardstick for your file.[3]
What should we send to get an accurate quote?
Send the system inventory, every user role, repository access or a repository list, API documentation, cloud accounts, environments and chains, the regimes the report must map to, your submission date and the retest rounds you expect.[9]
Related reading
- mica compliance checklist security
- dora penetration testing requirements
- crypto exchange compliance
- soc 2 vs iso 27001 digital assets
Sources
- European Securities and Markets Authority: MiCA Article 63: Assessment of the application
- European Securities and Markets Authority: Digital Operational Resilience Act
- New York State Department of Financial Services: Guidance on How to Conduct and Use Risk Assessments Required by the DFS Cybersecurity Regulation
- Guardian Security: Compliance Audits for Digital Asset Businesses
- European Securities and Markets Authority: MiCA Article 62: Application for authorisation as a crypto-asset service provider
- European Securities and Markets Authority: ESMA provides guidance on MiCA best practices
- Virtual Assets Regulatory Authority: E. Testing and Audit
- Invadel: US Penetration Testing Price Index
- Guardian Security: Blockchain Penetration Testing Cost: Web3 Pentest Prices
- New York State Department of Financial Services: Cybersecurity Regulation 23 NYCRR Part 500
- European Commission: DORA ICT risk-management regulatory technical standards
- Virtual Assets Regulatory Authority: Schedule 2: Supervision and Authorisation Fees