Rule · BCB · 26 Feb 2021 · Resolução CMN 4893

CMN Resolution No. 4,893 — Cybersecurity Policy and Cloud Computing Requirements for Institutions Authorized by the Central Bank of Brazil

In force from 1 Jul 2021Applies to: All regulated firms

Institutions must implement and maintain a cybersecurity policy including objectives, controls for data confidentiality, integrity, and availability, and incident recording and analysis. The policy must define procedures for third-party providers, cybersecurity culture dissemination, and sharing relevant incident information. Institutions must disclose a summary of the policy's general guidelines to the public.

BrazilBanco Central do Brasil
Annotations and obligations
250 obligations · 3 permissions · 30 definitions
  • Obligation 250
  • Permission 3
  • Definition / condition 30
  • background, boilerplate

Lineage: Amended

A newer document in RegAlert amends this one; it applies as amended.

Lei nº 6.099, de 12 de setembro de1974 — Dispõe sobre o tratamento …1974 · BR-LAWLei nº 6.099, de 12 de setembro de 1974 — Dispõe sobre o tratamento tributário das operações de arrendamento mercantil e dá outras providências (Law No. 6,099 of 12 September 1974 — tax treatment of financial leasing (arrendamento mercantil) operations) (1974-09-12)Lei nº 10.194, de 14 de fevereirode 2001 — Dispõe sobre a institui…2001 · BR-LAWLei nº 10.194, de 14 de fevereiro de 2001 — Dispõe sobre a instituição de sociedades de crédito ao microempreendedor, altera dispositivos das Leis nos 6.404, 8.029 e 8.934, e dá outras providências (Law No. 10,194 of 14 February 2001 on the establishment of microentrepreneur credit companies, amending Laws 6,404, 8,029 and 8,934) (2001-02-14)Complementary Law No. 130, ofApril 17, 2009 – National Coopera…2009 · BR-LAWComplementary Law No. 130, of April 17, 2009 – National Cooperative Credit System (2009-04-17)+2 moresee all below the graph+2 moreCMN Resolution No. 4658 —Cybersecurity Policy and Cloud Co…2018 · BCBCMN Resolution No. 4658 — Cybersecurity Policy and Cloud Computing Requirements for Financial Institutions (2018-04-26)Resolution No. 4752 dated2019-09-26Not in RegAlertResolution No. 4752 dated 2019-09-26 — Not in RegAlertCMN Resolution No. 4,893 —Cybersecurity Policy and Clou…2021-02-26 · this documentCMN Resolution No. 4,893 — Cybersecurity Policy and Cloud Computing Requirements for Institutions Authorized by the Central Bank of Brazil (2021-02-26)CMN Resolution No. 5117 — AmendingResolutions 4.595, 4.860, 4.879, …2024 · BCBCMN Resolution No. 5117 — Amending Resolutions 4.595, 4.860, 4.879, 4.893, 4.949, 4.968, and 4.984 (2024-01-25)Central Bank Resolution No. 5,274of December 18, 2025, Amending Re…2025 · BCBCentral Bank Resolution No. 5,274 of December 18, 2025, Amending Resolution CMN No. 4,893 on Cybersecurity Policy and Cloud Services (2025-12-18)Mentions (1)a document that mentions itopen the list below the graph ▾Mentions (1): a document that mentions it without changing it — open the list below the graphNormative Instruction BCB No. 330— Consolidates Procedures for Reg…2022 · BCBNormative Instruction BCB No. 330 — Consolidates Procedures for Registration of Cadastre Information in the Unicad System (2022-11-24)Normative Instruction BCB No. 590of February 5, 20252025 · BCBNormative Instruction BCB No. 590 of February 5, 2025 (2025-02-05)Central Bank of Brazil InstructionNormative No. 592 — Extends the E…2025 · BCBCentral Bank of Brazil Instruction Normative No. 592 — Extends the Effective Date of Instruction Normative No. 590 of February 5, 2025 (2025-03-19)
amendssupersedesissued underrefers todashed card: not in RegAlert (or proposed)arrows run from the older text to the one that changes it
The links and the sentences they come from (12)
Supersedes
Amended by
Issued under
Basis for
Mentions (1): 1 document mentions this one without changing it
Referred to by

What changed in the obligations

Against CMN Resolution No. 4658 — Cybersecurity Policy and Cloud Computing Requirements for Financial Institutions (2018-04-26)

69 new obligations · 1 deadline changed

122 obligations are the same in both texts.

Changed (1)
  • Deadline
    Before
    § 2. The communication referred to in the caput must be carried out, at minimum, sixty days before the contracting of the services.
    Now
    § 2º The communication referred to in the caput must be carried out within ten days after the hiring of the services.
New in this text (69)
  • I - authentication; (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • II - encryption mechanisms; (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • III - intrusion prevention and detection mechanisms; (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • IV - information leak prevention mechanisms; (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • V - protection mechanisms against malicious software; (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • VI - traceability mechanisms; (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • VII - data and information backup management; (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • VIII - assessment and correction of vulnerabilities of computing resources and information systems; (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • IX - access controls; (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • X - the definition and implementation of secure configuration profiles for technology assets; (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • XI - network protection mechanisms; (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • XII - digital certificate management; (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • XIII - security requirements for the integration of information systems through electronic interfaces; and (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • XIV - intelligence actions in the cyber environment, including monitoring information of interest to the institution on the internet, the Deep Web, and the Dark Web, as well as private communication groups.
  • I - in the development of secure information systems; and (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • § 6. The institution must verify the provision in item I of § 3, where applicable, in cases of information systems acquired by it or developed by third-party service providers, executed using the institution's own computing resources.
  • § 7. The traceability mechanisms referred to in item VI of § 2 must cover the traceability of transactions and operations, including, at a minimum: (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • I - end-to-end data and information processing audit trails, including the definition and generation of logs that enable the identification of processing failures or atypical behaviors, as well as supporting analyses; (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • II - definition of information retention time according to the type of processing performed; and (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • III - secure retention of audit trails.
  • § 8. The assessment and correction of vulnerabilities referred to in item VIII of § 2 must include, at a minimum: (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • I - periodic tests and analyses to detect vulnerabilities in information systems; (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • II - periodic scans of technological resources with the objective of identifying devices improperly connected to the corporate network that may establish connections with technology assets external to the institution; (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • III - periodic analyses of technological resources with the objective of identifying vulnerabilities that may compromise the security of the institution's technology assets; (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • IV - intrusion tests; and (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • V - timely correction of identified vulnerabilities.
  • § 9. The access controls referred to in item IX of § 2 must include, at a minimum: (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • I - mechanisms to limit access to the corporate network to credentialed users and authorized devices; (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • II - periodic and timely review of access permissions, especially for third-party employees with access to the institution's computing resources; and (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • III - implementation of multi-factor authentication for access to the corporate network from environments external to the institution.
  • § 10. The definition and implementation of secure configuration profiles referred to in item X of § 2 must provide, at a minimum: (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • I - the management of the lifecycle of the institution's computing resources; (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • II - the regular application of security patches; (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • III - the proper configuration of services to be supported by computing resources; and (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • IV - the change of passwords and other standards that may be used for unauthorized access to computing resources.
  • § 11. The network protection mechanisms referred to in item XI of § 2 must include, at a minimum: (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • I - computer network segmentation, safeguarding, in particular, the production environment and computing resources that support critical business processes; (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • II - the establishment of firewall rules, as well as the monitoring of connections, avoiding connection attempts to information systems originating from technology assets located outside the institution's corporate network; (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • III - the definition of criteria for the establishment and monitoring of connections with external environments, especially during nighttime and non-working days; (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • IV - measures to identify and prevent unauthorized connections with environments external to the institution originating from the institution's technological resources; (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • V - the implementation and maintenance of processes and tools for the identification, analysis, treatment, and control of atypical events in the institution's production environment, including, as examples, the establishment of virtual private networks – VPN and attempts at privileged access to computing resources, especially during nighttime and non-working days; and [(Added by CMN Resolution …
  • VI - the establishment of measures to restrict access to corporate networks only to duly authorized devices or technology assets.
  • § 12. The digital certificate management referred to in item XII of § 2 must provide, at a minimum: (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • I - the monitoring of the use of certificates and digital signatures, including the implementation of the traceability mechanisms referred to in § 7; (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • II - procedures for the storage of information, including physical and logical access controls to private keys under the institution's responsibility; (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • III - procedures and tools to prevent the unauthorized sharing of private keys associated with the institution's digital certificates; and (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • Art. 3-A. The institutions referred to in Art. 1 must establish the following additional security requirements, as an integral part of the procedures and controls provided for in their cybersecurity policy referred to in Art. 3: (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • a) use of multi-factor authentication for administrative access to the Pix environments and Reserve Transfer System – STR; (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • b) physical and logical isolation of the Pix environment from the institution's other systems, maintaining a dedicated and separate instance from other environments in cases of contracted cloud computing services; (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • c) physical and logical isolation of the STR environment from the institution's other systems, maintaining a dedicated and separate instance from other environments in cases of contracted cloud computing services; (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • d) monitoring of the use of credentials and digital certificates, as well as the establishment of controls for the storage of this information, especially those used within the scope of the Instant Payment System – SPI; (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • e) implementation of mechanisms for end-to-end validation of transaction integrity by the institution before the digital signature of associated messages, ensuring that the data has not been corrupted or manipulated during the generation process of these messages; and [(Added by CMN Resolution No. 5,274, of 12/18/2025.)](https://www.bcb.gov.br/estabilidadefinanceira/exibenormativo?tipo=Resolu%C3%…
  • f) prohibition of access by third-party service providers to the private keys associated with digital certificates used by the institution for message signing; and (Added by CMN Resolution No. 5,274, of 12/18/2025.)
  • - in the case of connection as a participant in Financial Market Systems – SMF authorized to operate, the implementation of security controls for the prevention, detection, and response to fraud, to be observed by the institution.
  • Institutions must observe this article in a manner compatible with the provisions of: (Included by CMN Resolution No. 5,274, of 12/18/2025.)
  • - in force regulation; and (Included by CMN Resolution No. 5,274, of 12/18/2025.)
  • - in all technical requirements of the RSFN provided for in the SFN Services Catalog, the SFN Network Manual, and the SFN Security Manual, published by the Central Bank of Brazil.
  • - the results of intrusion tests and the tests, scans, and periodic analyses for vulnerability detection referred to in Art. 3º, § 8º, and the action plans established for their corrections, observing the provisions of Art. 22-A, caput, item III.
  • - the hiring of the service, at least sixty days prior to the hiring, observing the provisions of Art. 15, § 1º, of this Resolution; and
  • Institutions must establish and document the criteria that constitute a crisis situation referred to in item III of the caput.

The first 60 of 69 are shown.

“Not carried over” means the sentence has no counterpart in this text; the rule can still be in force in another text.

Similar documents from other regulators

More like this from BCB

BCB published 10 documents in the last 30 days. We email you each new one the day it's published.

Source: Banco Central do Brasil — original document · Summary generated with machine assistance and reviewed before publication; the authoritative text is the regulator's original document. How RegAlert works

In RegAlert: added · updated