CMN Resolution No. 4,893/2021, issued by Brazil's National Monetary Council (CMN), is still the cybersecurity and cloud contracting rule for banks, credit cooperatives, consumer finance companies and other institutions authorised by the Central Bank of Brazil (BCB) that have not been carved out of its scope. The text that applies today, however, is not the one published in 2021: it was amended by CMN Resolution No. 5,117/2024, which narrowed the scope, and by CMN Resolution No. 5,274/2025, which set out controls in detail and added articles. This guide consolidates the current wording into an article-by-article map of each obligation, the provision behind it and the evidence that shows compliance.

Which text applies and who it covers
Resolution 4,893 was published in the Official Gazette on 1 March 2021, came into force on 1 July 2021 (art. 28) and revoked Resolution No. 4,658/2018 and Resolution No. 4,752/2019 (art. 27). The transition between the two is covered in the guide to what changed since Resolution 4,658. Since then, two rules have amended the text without replacing it:
- CMN Resolution No. 5,117/2024: from 1 March 2024, it reworded art. 1, sole paragraph, and removed from the scope consortium administrators, payment institutions, securities brokers and dealers and foreign exchange brokers, which follow Central Bank rules.
- CMN Resolution No. 5,274/2025, of 18 December 2025 (Official Gazette of 22/12/2025): it detailed the minimum controls in art. 3, created arts. 3-A, 22-A and 22-B, expanded the content of the annual report (art. 8) and the retention list (art. 23). Institutions already operating had until 1 March 2026 to adapt (art. 2 of Resolution 5,274). What each change means in practice is in the guide to CMN Resolution 5,274.
In the policy, the plan and contracts, the correct reference is “CMN Resolution No. 4,893/2021, as worded by CMN Resolution No. 5,274/2025”. The requirement is proportional: the policy must be compatible with the institution's size, risk profile and business model, with the nature and complexity of its operations and with the sensitivity of its data (art. 2, § 1). Prudential conglomerates and credit cooperative systems may adopt a single policy, provided each institution without its own policy formalises that choice at a meeting of the board of directors or, where there is none, of the executive board (art. 2, §§ 2 and 3).
Obligations map: article, requirement and evidence
The table follows the order of the resolution. In the last column, the tag “art. 23” marks a document the resolution itself requires to be kept available to the Central Bank for five years. The other items are the evidence we suggest for demonstrating compliance, because at those points the rule does not prescribe a format.
| Obligation | Article | Evidence |
|---|---|---|
| Cybersecurity policy proportional to size and risk profile | Art. 2 | Current policy document, with version and date (art. 23, I) |
| Choice of a single policy for a prudential conglomerate or cooperative system | Art. 2, §§ 2 and 3 | Minutes of the board of directors or executive board that formalised the choice (art. 23, II) |
| Minimum policy content: objectives, controls, incident register, guidelines for test scenarios, for service providers and for data classification, security culture and information sharing | Art. 3, I to VII | Policy index mapped to the seven items; data classification and incident relevance criteria |
| Fourteen minimum controls and the minimum content of six of them (traceability, vulnerabilities, access, secure configuration, network and certificates) | Art. 3, §§ 2 and 7 to 12 | Matrix linking each item to an internal control, with owner and evidence of operation |
| Controls applied to secure development and to new technologies, including third-party systems run on the institution's resources | Art. 3, §§ 3 and 6 | Security requirements in the development lifecycle and records of new technology assessments |
| Additional requirements for institutions communicating over the RSFN (National Financial System Network, covering the Pix instant payment and STR reserve transfer environments) and for participants in financial market systems | Art. 3-A | Evidence of administrative multi-factor authentication, environment isolation, key custody and integrity validation |
| Policy communicated to staff and service providers in clear language | Art. 4 | Records of communication, acknowledgement and training by audience |
| Public summary of the policy's main lines | Art. 5 | Published summary, with version date |
| Incident action and response plan, with adaptation actions, routines and technologies, and the area responsible for the incident register | Art. 6 | Plan document (art. 23, III) |
| Director accountable for the policy and for carrying out the plan | Art. 7 | Appointment record and conflict-of-interest analysis if the director holds other roles |
| Annual report on the implementation of the plan | Art. 8 | Report with a 31/12 reference date, proof of submission to the risk committee and presentation to the board by 31/03 (art. 23, IV) |
| Approval of the policy and plan by the board of directors or, where there is none, the executive board | Art. 9 | Approval minutes |
| Policy and plan documented and reviewed at least once a year | Art. 10 | Version history with review dates |
| Recording, cause and impact analysis and control of the effects of relevant incidents, including those reported by service providers | Art. 3, IV and § 4; art. 6, sole paragraph, III | Incident register, with the responsible area named in the plan |
| Contracting of data processing, storage and cloud services: risk management, prior assessment, notice to the Central Bank and contract clauses | Arts. 11 to 17 | Documented procedures (art. 23, V), documentation for services abroad (art. 23, VI) and contracts (art. 23, VII) |
| Business continuity: handling of incidents and of interruptions to contracted services, test scenarios and restart deadlines | Arts. 19 and 20, I and II | Risk management policy and business continuity test results |
| Crisis criteria and timely notice to the Central Bank | Art. 20, III and sole paragraph | Document setting out the crisis criteria (art. 23, IX) and record of notices sent |
| Monitoring and control mechanisms: processes, tests, audit trails, metrics and indicators and correction of deficiencies, tested by internal audit where applicable | Art. 21 | Data and records of those mechanisms (art. 23, VIII) and internal audit reports |
| Initiatives to share information on relevant incidents, available to the Central Bank | Art. 22 | Records of participation and of the information shared |
| Penetration test at least once a year, independent and with documented results | Art. 22-A | Test report and remediation plans (art. 23, X) |
| RSFN data communication service treated as a relevant service | Art. 22-B | Provider included in the inventory of relevant services and in the notice to the Central Bank |
Governance: director, board and the annual calendar
Four articles make up the governance cycle. Art. 7 requires a director accountable for the policy and for carrying out the incident action and response plan, who may hold other roles provided there is no conflict of interest. Art. 9 sends the policy and the plan for approval by the board of directors or, where there is none, by the executive board. Art. 10 requires both documents to be documented and reviewed at least once a year.
Art. 8 closes the cycle with the annual report. A detail that summaries of the rule often get wrong: the report covers the implementation of the incident action and response plan, not a general opinion on the policy. Its minimum content (§ 1) has five items:
- the effectiveness of the actions in the plan to adapt the organisational and operational structures;
- a summary of the results of the routines, procedures, controls and technologies used to prevent and respond to incidents;
- relevant cyber incidents that occurred during the period;
- business continuity test results, considering scenarios of unavailability caused by incidents;
- since Resolution 5,274, the results of penetration tests and of vulnerability tests, scans and analyses, with the action plans for remediation.
The calendar is fixed (§ 2): a 31 December reference date, submission to the risk committee where there is one, and presentation to the board of directors or the executive board by 31 March of the following year. For the report with a 31/12/2026 reference date, the deadline is 31/03/2027. Because the rule does not set a date for the annual review under art. 10, a practical option is to align it with the report cycle and take the report and the revised policy and plan to the board at the same meeting. How to turn this content into something the board understands is covered in the guide on how the CISO should report cyber risk to the board.
Incident register: one record, four uses
The resolution does not treat the incident register as a separate document, but it requires its content in several places. The policy must cover the recording, cause and impact analysis and control of the effects of relevant incidents (art. 3, IV), including information received from service providers (§ 4), and set the parameters for assessing incident relevance (art. 3, V, “d”). The plan must name the area responsible for that register (art. 6, sole paragraph, III). A well-kept register serves, in one go:
- the annual report, which must list the relevant incidents of the period (art. 8, § 1, III);
- the sharing of information on relevant incidents with other institutions, which must be available to the Central Bank (art. 22);
- business continuity, whose policies must address these incidents (art. 19, I);
- timely notice to the Central Bank of incidents that amount to a crisis, under documented criteria (art. 20, III and sole paragraph).
The resolution does not set a deadline in days for that notice. How it fits alongside the deadlines of the ANPD (Brazil's National Data Protection Authority) and SUSEP (the insurance regulator) is covered in the incident response plan template.
Cloud, third parties and data location, in brief
Chapter III (arts. 11 to 17) treats the contracting of relevant data processing, data storage and cloud computing services as a risk management decision: a documented prior assessment of the provider (art. 12), the contracting institution's responsibility for the service (art. 14), notice to the Central Bank within ten days of contracting or of a contract change (art. 15) and mandatory contract clauses (art. 17). Each step is covered in detail in the guide to third-party risk and CMN Resolution 4,893.
On data location, three provisions work together. Every contract for a relevant service must state the countries, and the regions within each country, where the service may be provided and the data stored, processed and managed (art. 17, I). For services abroad, this is defined before contracting (art. 16, III), goes into the notice to the Central Bank (art. 15, § 1, III) and depends on an information-sharing agreement between the Central Bank and the supervisory authorities of that country. Without such an agreement, authorisation must be requested at least sixty days in advance (art. 16, § 1). Two more points are worth noting: since Resolution 5,274, the RSFN data communication service counts as relevant whatever the type of connection (art. 22-B), and the Central Bank may veto or restrict a contract when it finds a breach of the rule (art. 26).
The file that must be available to the Central Bank
The resolution does not describe an inspection script. It does something more useful for anyone preparing evidence: art. 23 lists what must be kept available to the Central Bank for five years.
- the cybersecurity policy document;
- the minutes of the board of directors or executive board that formalised the choice of a single policy, where applicable;
- the incident action and response plan document;
- the annual report;
- documentation of the procedures carried out before contracting relevant services;
- documentation showing compliance with the requirements for services provided abroad;
- contracts for relevant services, with the period counted from the end of the contract;
- the data, records and information of the monitoring and control mechanisms under art. 21, with the period counted from the implementation of those mechanisms;
- documentation setting out the crisis criteria;
- penetration test results and vulnerability remediation plans, with the period counted from the test date (added by Resolution 5,274).
This has two practical consequences. First, the period does not always start on the same date: contracts count from termination, penetration tests from the test date and control records from implementation. An internal retention rule that applies “five years from creation” to everything may discard too early the contract for a service that ended less than five years ago. Second, item VIII is the broadest. The mechanisms in art. 21 include processes, tests, audit trails, metrics and indicators and the correction of deficiencies, and must be tested periodically by internal audit where applicable (art. 21, § 2). This is where day-to-day operations come in, not just approved documents. The guide to continuous internal audit shows how to keep those tests on a cycle.
Keeping the map in a GRC platform
The map has about twenty rows, with different owners, dates and retention periods. In a spreadsheet it works until the first amendment to the rule. After that, the hard part is showing which version of each control applied at each reference date. The Eagle GRC module, by Futture, was designed to centralise frameworks, requirements, policies, controls, evidence and action plans in a reusable model, and it accepts custom requirements, which makes it possible to register Resolution 4,893 in its current wording. The third-party risk module tracks suppliers with assessments, criticality, contracts and periodic reviews. Board approval, penetration testing, notices to the Central Bank and legal interpretation remain with the institution and its advisers.
Conclusion
Use the table as a checklist. For each row, point to the document or record that exists today, the date of its latest version and who owns it. Rows without evidence are the to-do list until next 31 December, and those tagged “art. 23” are the ones that cannot be missing when the Central Bank asks. Start with the three that Resolution 5,274 made more concrete: the minimum controls matrix, the independent penetration test and the new item V of the annual report.
Text consulted on 15/11/2026 in the Central Bank of Brazil's regulations database: CMN Resolution No. 4,893/2021 (consolidated version, with the amendments made by CMN Resolutions No. 5,117/2024 and No. 5,274/2025), CMN Resolution No. 5,117/2024 and CMN Resolution No. 5,274/2025. This article is for information only and does not constitute legal advice.
Further reading: Third-party risk and CMN Resolution 4,893; Brazil's CMN Resolution 5,274/2025: what changed for financial sector cybersecurity; Incident response plan: template and phases.
Frequently asked questions
Is CMN Resolution 4,893 still in force?
Yes. CMN Resolution No. 4,893/2021 has not been revoked. It was amended by CMN Resolution No. 5,117/2024, which changed its scope, and by CMN Resolution No. 5,274/2025, which set out minimum controls and added arts. 3-A, 22-A and 22-B. The correct reference is Resolution 4,893 as worded by Resolution 5,274.
Who does CMN Resolution 4,893 apply to?
Institutions authorised to operate by the Central Bank of Brazil, such as banks, credit cooperatives and consumer finance companies. Since 1 March 2024 it no longer covers consortium administrators, payment institutions, securities brokers and dealers or foreign exchange brokers, which follow Central Bank rules (art. 1, sole paragraph).
What are the annual report deadlines under CMN Resolution 4,893?
A 31 December reference date, submission to the risk committee where there is one, and presentation to the board of directors or, where there is none, to the executive board by 31 March of the following year (art. 8). The report covers the implementation of the incident action and response plan and, since Resolution 5,274, includes penetration test and vulnerability test results.
Can the director accountable for cybersecurity hold other roles?
Yes, provided there is no conflict of interest (art. 7, sole paragraph). The director is accountable for the cybersecurity policy and for carrying out the incident action and response plan.
How long must CMN Resolution 4,893 documents be kept?
Five years, available to the Central Bank (art. 23). The period runs from the end of the contract for relevant service contracts, from implementation for the records of monitoring and control mechanisms, and from the test date for penetration tests.
Official references
About the author
Founder, Futture.ai | CISSP
Cybersecurity, governance and risk management specialist with over 25 years of industry experience. CISSP-certified, founder of Network Secure and Futture.ai.