We manage your security to weather the AI storm →

← Resource Hub

IIA Cybersecurity Topical Requirement for Crypto Audits

By Owen ThurmPublished 6 min read

Part of our guide to digital asset security for banks

IIA Cybersecurity Topical Requirement for Crypto Audits

Quick answer. Since February 5, 2026, the IIA cybersecurity topical requirement has been mandatory for conforming cyber assurance work. Auditors must assess governance, risk management and controls, and document why any requirement is excluded. At exchanges and custodians, coverage should reach wallets, keys, signers and smart contracts.

Watch: IIA Cybersecurity Topical Requirement for Crypto Audits 1:49
Video transcript

Since February fifth, 2026, the IIA cybersecurity topical requirement has been mandatory for conforming cyber assurance. At exchanges and custodians, coverage should reach wallets, keys and smart contracts.

For assurance work, it applies when cyber is the engagement's subject, surfaces in another audit, or is requested outside the plan.

It is a minimum baseline, not a regulator's rule, and prescribes no wallet design. The crypto mapping here is Guardian analysis.

For governance, test the custody security budget, signer policies, role separation, and who may approve contract upgrades.

For risk, test response and recovery against crypto scenarios, not only ransomware: a compromised key or signer, upgrade abuse, chain disruption and vendor outage.

Controls map directly: encryption to key generation and backup, access to signer quorums, DevSecOps to contract audits. Vendor controls overlap the IIA third-party requirement, effective September fifteenth, 2026.

Design review is not enough. Ask for records proving each control operated throughout the audit period, then confirm a test wallet blocks a single-signer transfer.

Assess every requirement for applicability, document the rationale for each exclusion, and record where coverage sits. Outsourcing is allowed when expertise is lacking, but the chief audit executive owns conformance.

Read the full guide for evidence tables. To co-source testing, Guardian's Digital Asset Assurance Pilot reviews custody and key ceremonies, audits smart contracts and pentests signing services. Talk to Guardian.

Why It Matters Now

At an exchange or custodian, cyber risk is custody risk. The US banking agencies tie safekeeping to control of cryptographic keys.[1]

Their July 14, 2025 safekeeping statement adds no new supervisory expectations.

That statement says a safekeeping audit should assess key generation, storage and deletion, transfer and settlement controls, and the sufficiency of relevant IT systems, with third-party risk management as applicable. Audits may also assess management and staff expertise.

In the EU, DORA has applied since January 17, 2025. For covered entities other than microenterprises, it requires regular internal audit of the ICT risk framework by auditors with ICT expertise and appropriate independence.[2]

Skip wallets and signers, and most control requirements go untested where the assets sit.

Our guide to digital asset security for banks explains how digital asset security differs from bank IT. This one turns the IIA baseline into an audit program.

What It Is and When It Applies

The Cybersecurity Topical Requirement is part of the IIA's International Professional Practices Framework. It is a professional standard, not a statute or a regulator's rule.[3, 4]

The IIA issued it on February 5, 2025, and it took effect a year later, on February 5, 2026.[5]

It sets a minimum baseline. Where the risk profile warrants it, auditors may need to assess more than it lists.

It prescribes no wallet architecture, HSM or MPC design, or smart contract audit method. The crypto mapping in this guide is Guardian analysis.

It creates no license, charter or supervisory duty; laws and supervisory rules apply separately.

The requirement is mandatory for assurance work in three cases. For advisory work, the IIA recommends it but does not require it.

  • Cybersecurity is the subject of the engagement, such as a custody security audit.
  • Cybersecurity risk is identified during another engagement, such as a treasury or withdrawals audit.
  • Cybersecurity work is requested outside the approved audit plan.

Governance Requirements

Auditors must assess a formal strategy and objectives, updated periodically, and the policies and procedures that carry them out.[3]

They must also check that the board periodically reviews progress against the objectives, including resources and budget.

Auditors must also assess defined roles, how competency is assessed, and how stakeholders are engaged on vulnerabilities and emerging threats.

The US agencies say smart contracts that support safekeeping need governance and oversight throughout their life cycle.[1]

For board reporting, our cybersecurity board report template gives a one-page format with onchain metrics such as signer health and hot wallet exposure.

At an exchange or custodian, test governance against these points:

  • A budget for custody security, signing infrastructure and contract review, approved with the strategy.
  • Written policies for wallet tiers, signer onboarding and offboarding, key ceremonies and withdrawal approval.
  • Role separation among custody operations, security, compliance and vendors, so no one person can both approve and sign.
  • Documented authority to approve smart contract deployments, upgrades and pauses.

Risk Management Requirements

Risk management coverage asks whether cyber threats are identified, analyzed, mitigated and monitored, with participation across the organization and accountability assigned.[3]

Auditors must also assess rapid escalation of unacceptable risk, risk communication and remediation, and incident response and recovery that has been tested.

The IIA says escalation should weigh financial and nonfinancial impacts. Set thresholds for halted withdrawals or a regulator notice, as well as dollar loss.

Test response and recovery against crypto scenarios, not only ransomware: a compromised key or signer, abuse of a contract upgrade, a chain disruption and a vendor outage.

Plan ahead for the IIA Organizational Resilience Topical Requirement, effective April 30, 2027. Auditors must assess whether management periodically tests response and recovery, and whether critical data is backed up and recoverable.[6, 7]

It does not name cryptographic keys. Key recovery drills and signer compromise exercises are the natural evidence for both requirements.

Check that the risk register maps where customer assets move:

  • Hot, warm and cold wallets, with balances against approved limits.
  • HSM or MPC components, signer devices and each wallet's quorum, plus withdrawal APIs, approval engines and address allowlists.
  • Key ceremonies, backups and recovery paths, including who can start a recovery.
  • Nodes or RPC providers, smart contracts, and the oracles and bridges they depend on.
  • Sub-custodians and critical vendors with any access to keys or signing.[1]

Control Processes

The control section covers internal and vendor controls, cybersecurity talent management, and continuous threat and vulnerability monitoring.[3]

Vendor controls now overlap a second standard. The IIA Third-Party Topical Requirement took effect on September 15, 2026, for assurance over third-party governance, risk management and controls.[8]

It reaches subcontractors and fourth parties, prioritized by risk. Its controls run from due diligence and contracts through inventory, monitoring and corrective action to offboarding with access revoked.[9]

Scope an external sub-custodian or MPC wallet provider as a covered third party. Offboarding then means a tested asset transfer and revoked signing access.

Our crypto custody for banks guide sets out the key, sub-custodian and resilience controls examiners expect, with the evidence for each.

IIA control areaAt an exchange or custodian
IT asset life cycleInventory of wallets, keys, shares, signer devices and deployed contracts
EncryptionKey generation, storage, backup and deletion in HSM, MPC or multisig
Access managementSigner quorums, console access, API keys and leaver revocation
ConfigurationPolicy engine rules, withdrawal limits, allowlists and contract parameters
DevSecOpsContract audits, deployment checks and upgrade approvals
Threat monitoringOnchain alerts on outflows, role changes and upgrades, alongside the SOC
Vendor controlsSub-custodians, wallet or MPC providers, node and oracle vendors

Evidence for Keys, Wallets and Contracts

Design review is not enough for keys. Ask for records showing each control operated throughout the audit period.

Reperform where you can. On a test wallet, attempt a single-signer transfer and confirm the policy blocks it.

CheckEvidence to ask forRed flag
Key generationDated, witnessed ceremony records on controlled hardwareNo record of who was present
Quorum and dual controlWallet policy export and current signer listOne person or vendor can sign alone
Backup and recoveryDated recovery test with timingsRecovery never rehearsed
Transaction approvalApproval logs sampled against withdrawalsTransfers outside the policy engine
Contract changesDeployment and upgrade records matched to audited codeDeployed code differs from audited code
VendorsAssurance reports with signing systems in scopeSigning excluded from report scope

Documenting Conformance and Exclusions

The user guide asks auditors to keep evidence that every requirement was assessed for applicability.[4]

Coverage can be spread across several engagements. Record where each requirement is covered, in the audit plan or the workpapers.

The user guide's optional Appendix C tool has three columns: the requirement, the coverage executed or the rationale for exclusion, and the documentation reference.

The user guide allows outsourcing when the team lacks the cybersecurity knowledge. The chief audit executive still owns conformance. If resources are insufficient, the CAE must tell the board the impact and how the shortfall will be addressed.

RequirementCoverage executed or exclusion rationaleDocumentation reference
Governance A: strategy and objectivesExecuted: board custody reporting tested in custody auditCustody workpaper 2.1
Control E: encryptionExecuted: key ceremony and recovery records sampledCustody workpaper 4.3
Control E: DevSecOpsExcluded: covered by the contract change audit in the planAudit plan reference

Co-Source the Technical Testing

Guardian's Digital Asset Assurance Pilot reviews custody and key ceremonies, audits the smart contracts in scope, and pentests the consoles, APIs and signing services that can reach your keys.

Frequently Asked Questions

Does the requirement apply to a crypto exchange that is not a bank?

Yes, if its internal audit function conforms with the IIA's standards: it applies at a bank, an exchange or a custodian alike. Out-of-plan cyber engagements requested by the board, management or a regulator, for example after an attack, also trigger it.[3, 4]

Which framework should the audit map to?

The IIA's user guide maps the requirement to NIST CSF 2.0, NIST SP 800-53 and COBIT 2019, but does not require adopting any of them. Our NIST CSF 2.0 controls list adds digital asset mappings.[4]

How is conformance checked?

Through quality assessments. Topical requirements fall under the internal audit function's quality assurance and improvement program, and the program's results, including conformance, must be reported to the board and senior management.[3, 4]

Sources

  1. Office of the Comptroller of the Currency, Federal Reserve Board and FDIC: Crypto-Asset Safekeeping by Banking Organizations
  2. European Union: Regulation (EU) 2022/2554, Digital Operational Resilience Act
  3. The Institute of Internal Auditors: Cybersecurity Topical Requirement PDF
  4. The Institute of Internal Auditors: Cybersecurity Topical Requirement User Guide
  5. The Institute of Internal Auditors: Cybersecurity Topical Requirement
  6. The Institute of Internal Auditors: Organizational Resilience Topical Requirement
  7. The Institute of Internal Auditors: Organizational Resilience Topical Requirement PDF
  8. The Institute of Internal Auditors: Third-Party Topical Requirement
  9. The Institute of Internal Auditors: Third-Party Topical Requirement PDF
  10. Guardian Security: Digital Asset Assurance Pilot