Rule · BCRA · 10 Mar 2023 · A 7724
The Board of Directors, Senior Management, technology and information security heads, and governance committees of entities must establish governance, risk management, segregation of duties, and an information technology strategy; technology and information security functions may not be combined with Human Resources, Institutional Relations, Accounting Administration, Financial Management, Commercial Management, Marketing, Comprehensive Risk Management or Internal Audit, and must be performed in the Argentine Republic. Entities must define at least one technology and information security governance committee, meeting at a minimum frequency consistent with its operations, with formal minutes for each meeting.
1983/2023 - 40 YEARS OF DEMOCRACY
TO FINANCIAL INSTITUTIONS:
Ref.: Circular
RUNOR 1-1785:
We address you to inform you that this Institution adopted the following resolution:
“1. Repeal the rules on “Minimum requirements for the management, implementation and control of risks related to computer technology, information systems and associated resources for financial institutions”.
2. Approve the rules on “Minimum requirements for the management and control of technology and information security risks” contained in the annex and forming part of this communication.
3. Establish that this communication shall be effective 180 calendar days from its dissemination.”
We greet you attentively.
CENTRAL BANK OF THE ARGENTINE REPUBLIC
Mara I. Misto Macias
Principal Manager of Security Standards of Information in Entities María D. Bossio Deputy General Manager of Financial Regulation
B.C.R.A.
CONSOLIDATED TEXT OF THE RULES ON
“MINIMUM REQUIREMENTS FOR THE MANAGEMENT AND CONTROL OF TECHNOLOGY AND INFORMATION SECURITY RISKS”
Annex to
Comm. “A”
7724
-Index-
Section 1. General provisions.
1.1. Obligated subjects.
1.2. General aspects.
Section 2. Technology and information security governance.
2.1. Governance roles, responsibilities and functions.
2.2. Segregation of duties.
2.3. Regulatory framework.
Section 3. Technology and information security risk management.
Section 4. Information technology management.
4.1. Information technology strategy.
4.2. Enterprise architecture.
4.3. Budget, investments and portfolio management.
4.4. Data management.
4.5. Information asset management.
4.6. Artificial intelligence or machine learning.
4.7. Management control and reports.
Section 5. Information security management.
5.1. Information security management framework.
5.2. Information security strategy.
5.3. Standards and procedures.
5.4. Budget, investments and project management.
5.5. Training and awareness programs.
5.6. Management control and reports.
5.7. Physical, systems and data access control.
5.8. Security operations.
Section 6. Business continuity management.
6.1. Continuity management framework.
6.2. Cyber resilience in business continuity.
6.3. Impact analysis and risk assessment.
6.4. Business continuity strategies.
6.5. Training and awareness program.
6.6. Exercises and tests of business continuity plans.
6.7. Maintenance of business continuity plans.
6.8. Management control and reports.
CENTRAL BANK OF THE ARGENTINE REPUBLIC
Section 7. Technological infrastructure and processing.
7.1. Management of technological infrastructure.
7.2. Change management.
7.3. Updating of technological infrastructure.
7.4. Communications management.
7.5. Data processing.
7.6. Management of data backup copies.
7.7. Monitoring of technological infrastructure and processing.
Section 8. Cyber incident management.
8.1. Preparation of response to cyber incidents.
8.2. Exercises and tests of response to cyber incidents.
8.3. Management control and reports.
Section 9. Development, acquisition and maintenance of "software".
9.1. Requirements for systems and applications.
9.2. Management of the "software" life cycle.
Section 10. Management of the relationship with third parties
10.1. Framework for managing the relationship with third parties.
10.2. Formalization of the relationship.
10.3. Control and monitoring
10.4. Internal and external audit reports.
Section 11. Electronic Channels.
11.1. Scope.
11.2. Reference processes.
11.3. General requirements.
11.4. Electronic Channel scenarios.
11.5. Scenario matrix.
11.6. Glossary.
11.7. Tables of technical-operational requirements.
Section 12. Glossary of terms.
CENTRAL BANK
OF THE ARGENTINE REPUBLIC
Section 1. General provisions
The obligated subjects indicated in point 1.1., which for the purposes of this regulation shall hereinafter be called "entities", must ensure the implementation of effective practices for internal control and risk management of their technology and information security operating environment. To this end, they must demonstrate an understanding of the risks and establish a framework for their management in accordance with the complexity of the financial services offered and of the technology that supports them.
The following sections establish a set of minimum requirements, applicable to processes, structures and information assets, which the entities must implement for the purpose of:
Define and implement a technology and information security risk management framework as part of the entity's comprehensive risk management.
Define frameworks for the governance and management of technology and information security, in accordance with risk management.
Align with operational resilience objectives.
Include continuous improvement processes in the management frameworks.
Additionally, the entities must promote:
A culture of technology and information security risk management that allows them to identify and implement additional controls to these minimum requirements.
The adoption of the "three lines model" in the definition of roles and responsibilities.
The adoption of reference frameworks and international standards that allow complementing the minimum requirements related to risks, technology and information security.
CENTRAL BANK
OF THE ARGENTINE REPUBLIC
Section 2. Governance of technology and information security
The entities must establish a governance framework for technology and information security in accordance with their operations, processes and structure that allows compliance with the following objectives:
Comprehensive management and optimization of technological resources.
Alignment with business needs.
Adequate supervision of information technology activities.
Management of risks related to technology and information security.
In turn, they must establish management frameworks that allow coordination of activities, in order to measure and compare the results obtained with the proposed objectives.
In addition to the provisions established in the Ordered Texts "Authorities of Financial Entities", "Guidelines on Corporate Governance in Financial Entities" and "Minimum Standards on Internal Controls for Financial Entities", the entities must formally define the specific roles and responsibilities for the hierarchical levels indicated below.
The Board of Directors or equivalent authority of the entity (Board of Directors, in the case of cooperative financial entities, or the representative in charge of the first hierarchical level, in the case of branches of foreign financial entities), shall be responsible for the following:
Establish and maintain governance components coordinated with respect to authority and responsibilities to achieve the mission, goals and objectives of the business.
Approve and oversee the organizational structures and high-level policies related to the technology and information security governance framework.
Continuously monitor the performance of technology and information security governance, in order to comply with the established goals and objectives.
Promote and oversee strategic technology and information security projects.
Ensure the availability of adequate and sufficient resources for the areas related to technology management and information security.
Approve and oversee the risk management framework, and the information technology risk appetite.
Foster a culture of technology and information security risk management that encompasses the entire entity.
Promote the implementation of an information security management framework and oversee its effectiveness.
Approve the business continuity management framework and the mechanisms that ensure cyber resilience, and oversee its performance.
Approve the policies for managing the relationship with third parties.
Approve the policies for reporting significant cyber incidents to government agencies.
Approve policies for reporting incidents that compromise customer data.
2.1.2. Senior Management
Entities shall establish the responsibilities of Senior Management or Executive Management regarding technology and information security. Senior Management shall be responsible for the following:
Design information technology strategies and plans and define the necessary budget to fulfill them.
Know and understand the risks related to technology and information security, ensure that they are contemplated in the established management programs and define mitigation plans for the identified risks.
Design information security strategies, plans and measures, and define the necessary budget to fulfill them.
Define and ensure the implementation and maintenance of high-level policies.
Define the roles and responsibilities necessary for the technology and information security processes in a coordinated and effective manner.
Establish an information security management framework that allows ensuring the identification, prevention, detection, response and recovery against cyber incidents.
Implement internal control and risk management practices, and ensure that information technology decisions are made in accordance with the entity's risk appetite.
Outline a business continuity management framework, its associated documents and the resulting reports.
Define and implement a scheme for continuous control and monitoring of the processes, services and/or activities delegated to third parties.
Ensure the management of knowledge, skills and capabilities in accordance with the technologies used.
Establish communication and coordination mechanisms among the risk management, technology and information security areas for the fulfillment of their objectives.
Ensure the incorporation of the security by design principle in information technology projects.
Ensure the performance of impact assessments and definition of risk appetites for the use of artificial intelligence.
Approve the communication protocols and responsibilities in situations of crisis and/or emergency scenarios.
Ensure that the requirements related to the protection of users of financial services are contemplated in the corresponding technology processes.
Accept the residual risks derived from technology and security risk management
Senior Management, whether established in the Argentine Republic, in dependencies of the parent company or economic controller, shall keep the Board of Directors informed regarding the results of technology and information security management, and the level of risk exposure.
The heads of the technology and information security management areas shall coordinate, monitor and report the execution of activities, based on the guidelines defined by Senior Management. These functions shall be performed in the Argentine Republic.
In the cases of entities that have decentralized activities abroad, these functions may report directly:
In Argentina, to Senior Management or Executive Management.
In dependencies of the Parent Company or Economic Controller, to hierarchical levels that pos- sess responsibilities in matters of technology and information security.
Entities shall define at least one technology and information security governance committee. This committee shall be composed of, at least, one member of the Board of Directors or equivalent authority, members of Senior Management, and the heads of the technology and information security areas. In turn, the participation of high-level officials from the other areas shall be sought in accordance with the topics to be addressed.
Its responsibilities shall include, at a minimum:
Monitor and evaluate the functioning of the information technology management framework and contribute to the improvement of its effectiveness.
Monitor and evaluate the operation of the information security management framework and its effectiveness.
Oversee the definitions, prioritization and compliance of technology and information security plans.
Oversee the effectiveness of the business continuity management framework and the mechanisms that ensure technological resilience.
Oversee the execution of corrective actions aimed at regularizing or minimizing the observations arising from audit reports on technology and information security aspects.
Monitor the results of the risk management framework related to technology and information security and verify that mitigation plans are executed in accordance with the defined schedules.
Oversee the comprehensive management of cyber incidents and the associated reports.
Keep the Board of Directors informed of the matters discussed and the decisions made.
This committee must meet at a minimum frequency that is consistent with its operations, processes and structure. Formal minutes must be prepared for each meeting held, detailing the matters discussed, as well as the actions for subsequent follow-up.
Entities must formally establish a delimitation of roles and responsibilities that mitigates the risks associated with an overlap of functions and the absence of controls due to conflicts of interest. This definition must be extendable to the roles and responsibilities delegated to third parties.
The functions related to the governance and management of technology and information security may not be accumulated with the functions linked to: Human Resources, Institutional Relations, Accounting Administration, Financial Management, Commercial Management, Marketing, Comprehensive Risk Management and Internal Audit.
When the areas related to technology and information security assume functions of the first and second lines, entities must document the risks arising from the lack of independence of the second line.
BANCO CENTRAL
DE LA REPÚBLICA ARGENTINA
In those exceptional cases, in which any of the functions cannot be segregated, the Board of Directors must formally assume the risk and the formal and documented existence of compensating controls performed by independent sectors must be evidenced.
Entities must establish a formalized regulatory framework that includes the policies, standards and procedures for the effective management, oversight and control of the processes of risk management, technology, information security, business continuity, cyber incident management and third-party management.
Mechanisms must be implemented for their publication and formal communication to all those involved, both within the entity and third parties. In addition, a process must be established for their standardization and periodic updating.
Entities must establish an area or a risk management function related to technology and information security, in correspondence with the ordered texts on "Guidelines for Risk Management in Financial Entities" and "Data Aggregation on Risks and Preparation of Reports".
This area or function must be part of the unit responsible for operational risk management and be independent from the areas that originate the risks, from the business lines and from internal audit. It will have, among others, the following responsibilities:
Coordinate the definition, implementation and updating of the methodological framework.
Define, review and periodically update the technology and information security risk management framework.
Ensure the identification, evaluation, monitoring, control, mitigation, and communication of technology and information security risks.
Keep information updated and available for decision-making.
Promote a culture of technology and information security risk management and provide training aligned with the objectives.
The framework for technology and information security risk management must be aligned with the policies and practices established for comprehensive risk management. Within said framework, entities must:
Determine risk tolerance based on the established risk appetite.
Establish the policies and methodology for risk management.
Establish procedures for the identification and evaluation of risks, including those linked to third parties.
Establish procedures for the treatment of risks and evaluate their effectiveness.
Formalize and submit for approval the residual risks arising from technology and security risk management.
Carry out continuous monitoring of the levels of exposure to technology and information security risks.
Establish indicators linked to risk management.
Establish that the results of the management be communicated to the Board of Directors and the corresponding committees.
The technology and information security areas will be responsible for carrying out the identification of risks, and the technical definition and implementation of treatment measures.
The entity must ensure that the risk management framework is subject to an internal and external audit process. In addition, other duly qualified independent third parties may be involved.
Among the risks related to technology and information security included in the evaluation, those related to the following must be especially considered:
Scenarios that affect technological resilience.
The obsolescence of technology and systems.
The management of the relationship with third parties.
The development and use of artificial intelligence or machine learning algorithms.
The adoption of new or emerging technology.
Software or applications used by users who were not formally authorized.
CENTRAL BANK OF THE ARGENTINE REPUBLIC
The aspects of personal data protection in the use of distributed ledger technologies (Distributed Ledger Technology - DLT).
Cyber incident scenarios related to personal data.
Additionally, specific risk assessments must be carried out:
Before the launch of new products or services that cause significant changes in information systems, processes, services and/or information technology and security activities.
Before the delegation to third parties of processes, services and/or activities.
Section 4: Information technology management
Entities must establish an information technology strategy, in accordance with their operations, processes and structure, that allows achieving alignment between the results of information technology management and business and security requirements.
To this end, the results of risk management and the objectives of the security strategy must be considered. Additionally, entities must:
Establish strategic objectives and goals linked to the information technology strategy.
Define action plans that include the measures to be adopted to achieve the objective of the information technology strategy.
Review the action plans regularly to ensure that they are relevant and appropriate.
Establish processes to monitor and measure the effectiveness of the implementation of their information technology strategy.
In accordance with their operations, processes and structure, entities must establish an enterprise architecture model that allows coordinating the data strategy, the technology and applications architecture with business processes. Principles, standards and practices must be included to:
Support the Board of Directors and Senior Management in decision-making regarding technology investments.
Favor the evaluation of information security measures, operational resilience, data management, external connectivity and alignment with the entity's objectives.
Manage the complexity of the business and technology environment in order to improve the impact of changes in the organization.
Favor interoperability and integration with own or third-party services.
Compare the existing architecture with long-term objectives, future needs and planned changes.
Entities must establish effective practices for the preparation of information technology budgets and for the continuous evaluation of investments made. Formal communication channels must be established to timely notify deviations in their execution.
In addition, the information technology areas, together with the business areas, must define and implement a portfolio management process that allows capturing, evaluating, prioritizing, scheduling and executing business requirements. This process must take into account the following objectives:
CENTRAL BANK OF THE ARGENTINE REPUBLIC
Contribute to the strategic planning of information technology, in accordance with business needs.
Provide the necessary information for activity planning, taking into consideration projects, resources, costs and priorities.
Be accountable regarding the use of the technology budget.
The established processes must be aligned with the information technology strategy, the enterprise architecture, the budget management process and project management.
Entities must establish a framework for project management that covers its entire life cycle and ensures its alignment with the entity's strategic objectives. Standards must be defined that include:
The assignment of roles and responsibilities for the direction, execution and supervision of activities.
The definition of the project management methodologies used.
The evaluation of risks throughout the entire life cycle, in accordance with the provisions of Section 3: Technology and information security risk management.
Criteria for monitoring and communicating deviations and risks.
The documentation and management reports to be prepared.
Detailed plans must be prepared for all information technology projects, including, among other aspects: the definition of scopes, activities, milestones, expected results for each phase, roles and responsibilities of the participants. Additionally, when the project includes the development or acquisition of software, the requirements of Section 9. Software development, acquisition and maintenance must be considered.
When it is not possible to delimit the functions involved in any of the projects, the requirements established in Section 2. Technology and information security governance regarding segregation of duties must be considered.
Entities must notify the External Systems Audit Management of those projects that involve the implementation of new digital financial services or changes in the modality of existing services, when they process data of clients and users of financial services, accounting and/or transactional data.
Entities must define a process that establishes responsibilities, policies and procedures for data management, covering all stages of its life cycle and consistent with their operations, processes and structure.
Data management must be aligned with the business strategy, the enterprise architecture, and the information security management framework. In addition, criteria must be established to:
Identify data, both structured and unstructured.
Control the use of data in the activities of the entity and third parties.
Ensure data quality management throughout the entire life cycle.
Define the requirements for the retention, storage and backup of data based on the classification.
BANCO CENTRAL
DE LA REPÚBLICA ARGENTINA
Arrange for the deletion of data at the end of its life cycle in such a way as to prevent its recovery.
Supervise compliance with data management policies and procedures.
Control the execution of data management projects and services.
Additionally, processes and procedures must be established for obtaining and identifying the data processed by the entity that consider, at a minimum, customer data, accounting data and transactional data. Furthermore, mechanisms must be defined for the exchange of these types of data with other entities or third parties.
Entities must define policies and procedures for the classification of data and information in accordance with data management, which consider:
The participation of the data or information owner.
The criteria of integrity, availability, confidentiality and value to the business.
The frequency and recurrence of the use of the data and information, the modality, the format and the time during which it must be stored.
Entities must define a process that establishes responsibilities, policies and procedures for the management of information assets that support the business and the services of the entity, both own and delegated to third parties. Among other aspects, the following must be considered:
The definition of criteria for decision-making related to asset management.
Maintenance, use and obsolescence.
Vulnerabilities and needs for updating or replacement.
Compliance with internal configuration and security standards.
Entities must maintain a detailed and updated inventory of their information assets, in accordance with the objectives and the asset management policy. The inventories must contain information that allows identifying, at a minimum, aspects related to:
The identification of the owners of the information assets.
The location, configuration, internal and external interconnections, and interdependencies of each of the information assets.
The classification of the asset considered.
On the other hand, a process must be defined for the classification of information assets, in accordance with the classification of data required in the preceding section. The classification must be kept updated throughout the entire life cycle of the information assets and must be reviewed when changes occur in the processes, their owners or other organizational changes.
4.6. Artificial intelligence or machine learning
Entities must identify and document the purpose of the use, by themselves or by third parties, of software that uses artificial intelligence or machine learning algorithms in their projects or processes. In addition, they must establish roles and responsibilities for defining the context in which artificial intelligence or machine learning systems operate, the identification of the models, algorithms and data sets used, and the definition of precise metrics and thresholds to evaluate the reliability of the implemented solutions.
The corresponding risk analyses must consider, at a minimum:
The models adopted, their training and possible discrepancies with the reality of the context;
The data used for training, its volume, complexity and obsolescence.
Privacy and the impact on users in their capacity as consumers.
The level of maturity of software testing standards and the difficulties in documenting AI-based practices.
Additionally, processes must be implemented that promote reliability in the use of this type of algorithms and include at least:
Measures to prevent the existence of biases or discrimination against groups or segments of customers or users of financial products and/or services.
Documentation regarding transparency, the explainability of the models used and the interpretability of the results.
The execution of periodic reviews of the results with respect to the defined risk tolerance.
Communication to the customer when using services supported by this type of technology.
Entities must define a control process over the management of information technology areas, through procedures, tools and metrics that allow monitoring and evaluation of the tasks carried out and compliance with objectives. Likewise, they must include the identification of improvement opportunities.
The metrics must include indicators or thresholds that allow controlling deviations from what was planned, both for operational and management tasks, and establish corrective action plans when necessary.
In accordance with their operations, processes and structure, entities must promote the implementation of automated indicators, as well as the generation of alerts upon exceeding thresholds.
Monitoring of management effectiveness must consider the results of cyber incident response and recovery exercises, and vulnerability management. Additionally, the results of continuous improvement activities must be evaluated.
Management reports from technology areas must consider evaluations of process effectiveness that include, at least:
BANCO CENTRAL
DE LA REPÚBLICA ARGENTINA
Monitoring of capacity in communications, processing, virtualization, hardware.
Information on system performance (availability, response and processing times).
Change management.
Evaluation of compliance with service level agreements, including those provided by third parties.
Progress, deviations and relevant project risks.
Supervision of action plans for non-compliance or management deviations.
Management of technological infrastructure.
Furthermore, the frequency and formal communication channels for reporting the results of area management to the Board of Directors and Senior Management must be established.
CENTRAL BANK OF THE ARGENTINE REPUBLIC
Entities must establish an information security management framework that contemplates:
The strategic business and technology objectives, data management, data and information classification, information assets and risks.
The protection of information assets to ensure service delivery and contain the impact of security events.
The identification and detection of events that could lead to a cyber incident, and the design and implementation of measures to respond in a planned and timely manner.
The design of measures aimed at providing information security to processes and services in cyber incident recovery.
Entities must define an information security strategy aligned with the business strategy and in accordance with their operations, processes and structure. It must be consistent with the information technology strategy, enterprise architecture and the results of technology and security risk management. Likewise, it must consider:
The threats and vulnerabilities associated with each technological environment, their impact on the business and current international standards.
The entity's own human and technological resources.
Requirements of regulatory and control bodies, and other external entities directly or indirectly linked.
Dependencies on third parties.
In developing the strategy, entities must:
Establish strategic objectives and goals for project management and for information security processes, including training and awareness needs.
Create action plans that include measures to achieve the objectives of the information security strategy.
Consider threat and vulnerability management, and the classification of data and information and information assets.
Define objectives and guidelines for event and threat detection processes.
Consider cyber incident management.
Entities must establish, as part of the regulatory framework, standards and procedures that allow managing, controlling and documenting the activities of processes for information security management. At a minimum, those referring to the following must be included:
Access control.
Passwords.
Vulnerability management.
Detection and monitoring.
Criteria for sharing information related to threats and vulnerabilities.
Entity devices assigned to users.
User-owned devices used at the entity.
Threat modeling.
Specific aspects of secure development in accordance with the methodologies used.
Detection and regularization of unauthorized user software.
Digital forensics standards.
Furthermore, in accordance with their operations, processes and structure, entities must establish security standards that address the following aspects, at a minimum:
The implementation of secure configurations.
The adoption, review and implementation of cryptography algorithms.
Entities must establish effective practices for preparing information security budgets and for the continuous evaluation of investments made. Formal communication channels must be established to timely notify deviations in their execution.
Detailed plans must be prepared for all projects that include, among other aspects: the definition of scopes, activities, milestones, expected results for each phase, roles and responsibilities of participants. The definition of scopes must be consistent with business needs and aligned with the strategic business and technology projects, the enterprise architecture and the data management model.
Entities must establish training and awareness programs on information security, measurable and verifiable, that reach the entire organization, third parties, clients and users of financial services. These programs must contemplate technology and information security risks, and aspects related to cyberincident management.
For the definition of the objectives of the training and awareness programs and plans, at least the following must be contemplated:
Minimum contents to be developed, timeframes and target audience.
The link with information security plans.
The incorporation of lessons learned from previous cyberincidents, or through tests and exercises.
The updated publication of security information for clients and users of financial services.
For the development of the plans, at least the following aspects must be taken into account:
Segmentation of audiences and preparation of specific contents that include:
For internal and third-party users, the applicable regulatory framework and security practices.
For clients and users of financial services, the information security practices necessary for the safe use of the services provided by the entity.
Permanent updating based on the results of vulnerability and cyberincident management.
The training and awareness programs must be reviewed at least annually, with the objective of evaluating and informing Senior Management about the effectiveness of the activities carried out.
The content of the training plans intended for internal and third-party users must consider, at least:
The risks in the use of own devices in the organization.
The risks in the use of devices assigned by the entity.
The specific aspects of the secure development methodology.
The risks in the use of unauthorized software or applications.
The risks of incorporating unauthorized technologies (shadow IT).
Entities must define a control process over the management of information security areas, through procedures, tools and metrics that allow monitoring and evaluation of the tasks carried out, and of compliance with objectives. Likewise, they must include the identification of improvement opportunities.
The metrics must include indicators or thresholds that allow controlling deviations from what was planned, both for operational and management tasks, and establish corrective action plans when necessary. Additionally, the results of continuous improvement activities must be evaluated.
In accordance with their operations, processes and structure, entities must promote the implementation of automated indicators, as well as the generation of alerts upon deviations from thresholds.
The management reports of the information security areas must especially consider evaluations of the effectiveness of the processes that include, at least:
BANCO CENTRAL
DE LA REPÚBLICA ARGENTINA
Results of response and recovery management for cyberincidents and of the exercises.
Access control.
Security operations.
Vulnerability management.
Evaluation of service level agreements, including those provided by third parties.
Supervision of action plans for non-compliance or management deviations.
In addition, the frequency and formal communication channels for reporting the results of the areas' management to the Board of Directors and Senior Management must be established.
Entities must design and implement controls that allow them to avoid the existence of single points of failure and mitigate risks related to the physical security of the areas intended for the processing, transmission and storage of information to prevent unauthorized access or detect it. Procedures must be established for:
Preventive maintenance and periodic testing of environmental control devices and redundant power equipment.
The application of techniques for the destruction of assets in accordance with their classification.
The authorization and recording of the removal and transfer of assets from the facilities.
Permanent monitoring of the effectiveness of the protection measures implemented.
The prevention, detection and correction measures established must be aligned with the results of technology and information security risk analyses, standards and good practices. In addition, they must include, at least:
Adequate mounting installations for electrical supply systems and measures for electrical power redundancy.
Measures to control ambient temperature and humidity levels.
Use of non-flammable or fireproof construction materials.
Alarms and systems for fire detection and extinguishing.
Video and event recording systems.
Systems for access control to facilities that allow segregation of permissions and recording of entries.
Systems for monitoring and control of the protection measures implemented;
Measures to control the exposure of workstations, communications and network devices.
In accordance with the information security policy, entities must define a management process that allows requesting, approving, assigning, modifying, monitoring and revoking access rights to information assets. This process must:
Reach all information assets, including physical access to the facilities of data processing, storage and transmission centers.
Ensure the application of the principles of segregation of duties and least privilege.
Identify the functions that require the intervention of more than one user and define the pertinent controls.
Establish criteria for the assignment of access rights in accordance with the roles, functions and responsibilities of the entity's personnel and third parties.
Ensure the timely adequacy of user access rights and privileges based on changes in job positions or terminations.
Establish circuits for the authorization of accesses and privileges that include the participation of the owners of information assets.
Identify and revoke expired, inactive accounts or those that fail to comply with security policies.
Define periodic reviews of access levels and privileges assigned on information assets, with the participation of the owners of information assets.
Establish procedures for the assignment and monitoring of the use of generic, privileged and service accounts.
Implement automated controls over the functions of creation, modification, enabling, revocation and deletion of accounts.
Entities must implement measures that allow maintaining control over privileged and service accounts. Among others, they must:
Establish and maintain an inventory of service and privileged accounts.
Restrict administrative access to privileged accounts.
Implement controls over default accounts to prevent their unauthorized use.
Promote the implementation of multi-factor authentication for privileged accounts.
Use processes and tools to manage the assignment of access rights on privileged and service accounts.
Entities must implement measures that allow maintaining control over assigned access rights. Among others, and in accordance with their operations, processes and structure, they must consider:
Automation of the process of creation, enabling, modification, revocation and deletion of user accounts.
Automatic notifications of changes.
Dynamic privilege management processes.
Mechanisms must be implemented to ensure that the activities of all accounts are uniquely identified and recorded, and provide sufficient information for audit and investigation purposes.
5.7.2.1. Access control measures
Entities must establish security directives for access to information assets based on vulnerability and threat management, and on the classification of information assets. These directives must define, at a minimum, the methods used for authentication.
In addition, they must define access models for users that consider authentication factors, behavior in the use of services and different sources of information that allow validating their identity.
Entities must establish procedures for:
The implementation, periodic review and updating of access control rules for network devices, ensuring that they remain up to date.
The establishment of controls that allow detecting and preventing the connection of unauthorized devices on networks.
The management and implementation of authentication methods in information exchange services with third parties.
The implementation of measures for the security of remote access connections, enabled devices and the information accessed or used.
For the selection and implementation of authentication methods and their factors, entities must consider the results of risk analyses, and compliance with access control policies and procedures.
In the definition and implementation of the technical specifications of authentication methods, the following must be considered: authentication factors, validation and the channel used. Protection measures must be established to ensure the integrity and confidentiality of authentication factors throughout their life cycle. In particular, entities must:
Implement additional measures to safeguard confidentiality in authentication data that must be secrets of the client or user of the service.
Define controls to prevent loss, theft or unauthorized duplication.
Establish criteria and controls on the expiration periods of credentials.
Evaluate the frequency in the presentation of authentication factors together with session management.
In the implementation of authentication factors, entities must apply the minimum controls established below. Additionally, and based on the results of risk analyses, and threat and vulnerability management, complementary controls may be applied.
Memorized secret: For the secure use of memorized secrets, entities must establish minimum requirements and controls that include:
Establish a minimum length and composition rules in accordance with the specific risks of the service.
Allow the concatenation of several words to create long secrets.
Limit the use of user data or their context that are easily guessable (such as names or dates).
Restrict the reuse of secrets previously used by the user.
Provide functionality that allows replacement when there is suspicion that they have been compromised.
Define the validity and expiration time.
Revoke passwords more than one year old.
Limit the maximum number of failed authentication attempts, and establish a mechanism for counting and blocking after reaching the maximum.
Use a protected channel in the verification process.
Establish measures for the security of stored secrets that reduce the risk of offline attacks, including the use of hash or encryption algorithms.
Establish controls that limit the use of easily deducible secrets, widely used or previously compromised.
Out-of-band authentication: Entities must consider the implementation of the following minimum controls:
The use of a different and encrypted communication channel for sending authentication messages.
The use of methods that prove possession and control over the device.
Out-of-band authentication via SMS must have restricted use, in accordance with the associated risks, and requires the application of complementary controls.
Cryptographic devices or cryptographic key stores: For the secure use of cryptographic devices or cryptographic key stores, entities must consider the implementation of at least the following controls:
Keys will be stored securely and their extraction will not be permitted.
The requirement of user intervention for the use of the cryptographic device or key store.
Strong protection measures on the keys.
The use of secure algorithms for key generation.
Generation of one-time passwords (OTP): In their use, at a minimum, the application of the following controls must be considered:
The implementation of strong protection measures on the keys kept by the entity.
The use of secure cryptographic algorithms to generate, exchange or obtain the data in the association of the device with the user's account.
The use of protected and authenticated channels for the presentation of the codes.
The definition of a lifetime for each generated value.
The single use of each generated value.
The limitation of failed attempts to enter the codes.
Use of secure algorithms for key generation.
Definition of a seed length that ensures the generation of unique values throughout the life of the device.
Use of biometric data: In the implementation of authentication methods that use biometric data, the risks derived from the following characteristics must be evaluated and mitigated:
The limitations to ensure subscriber authentication due to the probabilistic nature of the method, the false match rate (FMR) and the lack of secrecy of the biometric data.
The need to establish a process for the revocation of credentials of this type.
The possible vulnerabilities in the devices and systems used for the capture and validation of credentials.
The impact on user privacy.
Furthermore, in accordance with the classification of the data, information and assets to which access is provided, controls must be implemented that include:
The combined use with at least one additional authentication factor of another type.
The use of protected channels for the transmission (transfer) of information.
The definition of trust thresholds.
The implementation of controls that mitigate the risk of attacks at the credential presentation stage.
The application of controls for failed authentication attempts.
The application of measures that allow the identification of the devices used for the capture and validation of credentials.
Entities must evaluate the use of multi-factor authentication for access to information assets in accordance with their classification, and the management of threats and vulnerabilities. Furthermore, entities must evaluate the robustness of the method together with usability and efficiency.
In the implementation of multi-factor authentication, at least two factors of different categories or a multi-factor authenticator must be used.
A multi-factor authenticator shall be considered to be software or hardware for generating one-time passwords (OTP), or cryptographic devices, when it complies with the following requirements:
Access to the generator must require an authentication factor of the memorized secret or biometric data type.
When a memorized secret is used for access, it must have at least 6 characters.
If biometric factors are used, the considerations of the preceding para- graph must be taken into account.
Failed access attempts must be limited.
Security controls must be established for the entity's own devices assigned to internal users in accordance with the classification of data and information, as well as vulnerability and threat management, which contemplate, at a minimum:
The security configurations of the devices.
The encryption of information.
The limitation of installation of unauthorized software.
Likewise, security controls must be implemented to limit the connection and access to networks, systems and information to the devices owned by internal users or contractors.
In accordance with the classification of data and information, and the management of vulnerabilities and threats, financial entities must implement measures that allow them to detect and prevent unauthorized access, modification, copying or transmission of information. The implemented controls must:
Encrypt information in transit, stored in systems, or on users' devices, in accordance with its classification.
Segment the processing, transmission and storage of information.
Establish measures to limit access rights to data in production environments.
Establish measures for the masking and protection of data in non-production environments, in accordance with the results of their classification.
Apply secure deletion measures to eliminate information from storage media, systems, and devices assigned to users before their disposal or reuse.
Implement mechanisms for protection against malicious code.
In addition, entities must implement controls to identify unauthorized transfer or processing of information classified as confidential or critical.
Entities must establish a process for the recording and analysis of information related to security events of systems, networks and technological infrastructure. This process must allow the detection of anomalies and events, the identification of incidents, and the linkage with the cyberincident management process in accordance with the classification of data and information and that of information assets. In addition, at least the following activities must be considered:
Collect, process, control and preserve the records of events and activities of users in the information systems and the infrastructure that supports them.
Define measures for the continuous improvement of the process.
Establish and review behavior profiles of users and information systems that allow identifying usual activities.
Correlate different events included in activity logs to identify pat- terns of suspicious or unusual activity.
As part of this process, entities must define:
Metrics for the execution of system monitoring activities and their alignment with the strategy.
Continuous evaluations of risks and controls based on monitoring.
Frequencies for the execution of monitoring and for the evaluation of the effectiveness of controls.
Actions to validate that policies and configuration standards are implement- ed and function consistently.
Thresholds for the categorization and handling of alerts.
Alerts for the use of privileged access.
Measures aimed at ensuring the availability, accuracy and validity of the results of monitoring.
Controls for the protection of activity logs in order to prevent unautho- rized access.
Measures for the preservation of event and audit logs.
Entities must establish a process to collect, process, analyze and interpret information related to threats through proactive and reactive methods, which provides information for decision-making related to cyberincident management.
In addition, they must implement actions for the detection and elimination of unauthorized profiles on social networks, e-commerce platforms, among others.
On the other hand, entities must establish a vulnerability management process for all systems and applications, whether their own or third-party, in accordance with risk management and linked to incident management, which contemplates the following activities:
Establish points of contact for the notification of vulnerabilities of both internal and external services of the entity.
Perform an analysis and an evaluation of the impact of security vulnerabilities pub- lished or reported to the entity, which affect its information assets.
Establish a risk mitigation plan and schedule according to its criticality.
Define alternative mitigation measures when no updates are available or their implementation implies a greater risk.
Provide timely information to the security update management process, which in- cludes the criticality of the vulnerability.
BANCO CENTRAL
DE LA REPÚBLICA ARGENTINA
Entities must establish a business continuity management framework that considers:
The provisions in force on "Guidelines for Risk Management in Financial Entities", "Data Aggregation on Risks and Reporting" and "Guidelines for response and recovery to cyberincidents (RRCI)".
The principles for operational resilience.
The results of comprehensive risk management, and the defined risk appetite.
The strategic objectives of the business.
The management of technology and information security, and the enterprise architecture model.
This management framework must establish at least:
Criteria for conducting impact analyses and defining continuity strategies.
Guidelines for the preparation of recovery plans.
Measures for the continuous improvement of the management framework.
A program of exercises and testing aligned with those carried out in cyberincident management.
Training and awareness plans.
The management of resources linked to this management framework.
Depending on the entity's operations, processes and structure, an area, sector or person responsible for coordinating the activities related to business continuity management must be designated. Likewise, roles and responsibilities must be defined for the different activities that make up the management framework.
Entities must establish proactive measures in the design of operations and processes that allow them to mitigate the risk of disruptive events and maintain confidentiality, integrity and availability.
In accordance with the business's strategic objectives, the results of risk management and lessons learned, measures must be applied that strengthen the entity's recovery capabilities against disruptive events with respect to:
Facilities, technology architecture and infrastructure.
Cyberattacks.
Data backup strategies and replication mechanisms.
Availability of essential personnel.
Services provided by third parties, interconnections and dependencies.
Energy and supply provisions.
Emergency change management.
6.3. Impact analysis and risk assessment
Entities must consider as a basis for business continuity management the business impact analysis (BIA), the results of technology and information security risk management, and the entity's comprehensive risk management.
The business impact analysis and risk assessments must be reviewed periodically or upon significant changes in the entity or in its operating context.
Entities must implement a process for preparing business impact analyses (BIA) that involves all areas of the entity and allows the needs and recovery priorities to be defined.
This process must include:
The definition of criteria for impact assessment relevant to resilience and continuity.
The identification of the activities that support the provision of products and services.
The identification of process interdependencies.
The identification of process dependencies on third parties.
The identification of possible disruptive incidents and the assessment of their impact.
Recovery objectives in relation to time and data loss. (RTO/RPO).
The reasonableness of the recovery objectives
Communication of the results obtained to Senior Management.
Entities must carry out periodic assessments of the risks of disruptive scenarios. In accordance with the framework established for comprehensive risk management, treatment plans must be established in line with the risk appetite.
The risks associated with the geographic location, susceptibility to threats and proximity to critical infrastructures of all facilities, including those provided by third parties, must be analyzed. Furthermore, for the applicable scenarios, the interruption threats that could simultaneously affect the different sites must be assessed.
Entities must develop business continuity strategies to meet the defined resilience and recovery objectives, based on the identified threat scenarios and business processes.
Within their scope, the following points must be considered:
Detail of the information technology infrastructure, resources involved and processing facilities.
Backup, replication and storage schemes for data protection.
The existence of isolated recovery environments.
Levels of redundancy in the telecommunications infrastructure.
Inclusion of non-technology risks (for example, transaction, liquidity and reputa- tion risks).
Based on the defined strategies, entities must establish and implement business continuity plans that allow operations to continue during the period of restoration of the affected service.
The plans must contemplate the defined continuity strategies and include, at a minimum:
The procedures for declaring a crisis situation and the criteria for activating related plans.
The assignment of responsibilities for the execution of recovery plans.
The detailed recovery procedures, the identification of critical infrastructure, systems and components, and their recovery priority.
The procedures for relocating essential activities to alternative locations.
The establishment of alternative customer service channels.
Measures that ensure the integrity and confidentiality of critical information during recovery processes.
Depending on their operations, processes and structure, entities must establish automated procedures that allow mitigating the risks associated with manual recovery processes.
The entity must designate persons responsible for decision-making and for preparing crisis management plans. Furthermore, it must establish procedures for crisis situations that are linked to incident management and consider disruption scenarios.
Likewise, they must define communication strategies that reach:
The participants in the execution of the procedures, both from the entity and from third parties.
The corresponding authorities and other interested parties.
Communication procedures must be established that ensure notification to interested parties, the definition of contact lists, and the participation of technical areas in defining the content of the communication.
Entities must establish a training program and plans that reach the entire organization and consider, at a minimum, operational resilience, business continuity objectives, the impact of possible disruptive scenarios, staff roles and responsibilities, and lessons learned.
For the development of the plans that make up the program, account must be taken, at a minimum, of the identification and segmentation of audiences, including the Board of Directors, Senior Management and the areas responsible for customer service.
CENTRAL BANK OF THE ARGENTINE REPUBLIC
The plans must be reviewed periodically, with the aim of evaluating and informing Senior Management about the effectiveness of the activities carried out.
Entities must develop an exercise and testing plan in order to verify that the defined continuity strategies and the established plans adequately support the business continuity objectives.
The plan must contain a formalized annual schedule, in accordance with its operations, processes and structure, indicating the scenarios contemplated, dates, areas involved, business processes and systems covered, among other aspects. The schedule must contemplate at least one of the highest criticality scenarios.
The exercises and tests of the continuity plans must involve, at a minimum, the person responsible for business continuity management, the technology and information security areas, the user areas related to the business processes, the linked third parties and the internal audit areas.
In addition, the results must allow the evaluation of:
The effectiveness of the continuity strategies adopted.
The performance of the participants' activities according to their roles and responsibilities.
The technical, logistical and administrative aspects.
The operation of the recovery infrastructure.
The feasibility of the staff relocation processes.
The deficiencies and opportunities for improvement of the continuity plans.
The effectiveness of the communication strategies.
A detailed record must be kept of the results of each exercise, the observations and problems detected, and the action plans defined for their correction.
Entities must periodically review and update the business continuity plans and their related procedures in order to ensure their alignment with business objectives, considering, at a minimum:
Changes in business strategies.
The implementation of new products, services and/or technological infrastructures.
Changes in the products and services of third parties.
Emergence of new threat scenarios.
Regulatory changes.
Key risk indicators.
Results of the exercises and tests carried out.
Results of audit activities or internal or external evaluations.
CENTRAL BANK OF THE ARGENTINE REPUBLIC
6.8. Control and management reports
Entities must define a control process over business continuity management, through procedures, tools and metrics that allow monitoring and evaluation of the tasks carried out and compliance with objectives.
The metrics must include indicators or thresholds that allow controlling deviations from what was planned, both for continuity plans, training plans and testing plans.
Among the continuous improvement activities, lessons learned from the execution of the plans, the business impact analysis, the risk assessment and the exercises and tests carried out must be documented, analyzed and included.
The frequency and formal channels of communication of the results of the areas' management to the Board of Directors and Senior Management must be established. In turn, Senior Management must report on business continuity management to the Board of Directors or equivalent authority.
BANCO CENTRAL
DE LA REPÚBLICA ARGENTINA
Section 7. Technological infrastructure and processing
Entities must define structures, processes and procedures for the activities of managing updates and configurations, implementing changes, monitoring the infrastructure, operating the systems and managing communications. The established processes must ensure:
The alignment of infrastructure, operations and communications with the enterprise architecture and resilience objectives.
The preservation of the confidentiality, integrity and availability of the information affected.
The implementation of measures to avoid the existence of single points of failure.
The application of mechanisms that allow ensuring the traceability of the management activities carried out.
Incident management aligned with the provisions of Section 8.
The alignment of controls with the provisions of Section 5.
On the other hand, entities must establish processes for the planned and centralized management of the registration and response of the demand for technology services that allow them to:
Capture requests for updates, help, fault resolution, or similar.
Establish planned circuits for processing and response.
Define and communicate contact points.
Monitor and keep a record of requests and actions taken.
Identify deviations from the circuits planned for processing and response.
Entities must establish a process that allows them to record, evaluate, plan, review, approve and communicate changes to information assets before implementation in production environments. The procedures governing the change management process must include:
A definition of roles and responsibilities that mitigates the risks associated with inadequate segregation of duties.
The implementation of controls based on conflicts of interest in accordance with the identified risk levels.
Controls for the separation of the environments used in the different stages of the development, acquisition and maintenance life cycle.
The definition of approval criteria and escalation mechanisms aligned with the impact of the changes and the results of risk analyses.
The performance of an analysis of the impact of the changes on the information assets involved.
The implementation of controls that ensure the separation of the production environment from the rest of the environments.
The definition of procedures for the administration of specific services (APIs, hardware virtualization, etc.)
BANCO CENTRAL
DE LA REPÚBLICA ARGENTINA
The implementation of changes in production environments.
The establishment of measures that allow changes to be reverted upon detection of failures or problems associated with their implementation.
The application of mechanisms that ensure the traceability of the activities carried out and the integrity of the changes implemented between the different environments.
The definition of specific procedures for the processing, subsequent control and identification of the causes of emergency changes.
The change management process must be in accordance with the provisions of Section 9: Software development, acquisition and maintenance of this consolidated text.
In accordance with the criteria established for change management, entities must establish a process for managing technological infrastructure updates, in accordance with the defined enterprise architecture, that allows them to:
Develop an information asset update plan that considers possible vulnerabilities due to obsolescence.
Establish a process for the implementation and recording of changes, in accordance with information asset management.
Evaluate the risks of using obsolete assets and implement effective mitigation measures.
In addition, entities must implement a configuration management process that contemplates the security standards required in Section 5. This process must allow:
Establish and update configuration standards for hardware and software components.
Maintain accurate and up-to-date information on the configurations of the hardware and software that make up their systems.
Review and verify configurations on a regular basis, monitor unauthorized changes and configuration errors, and apply the corresponding adjustments.
Establish mechanisms to verify software integrity and detect unauthorized changes in configurations.
Likewise, a security update management process must be established in line with threat and vulnerability management. These updates must be tested before their implementation in production environments to ensure compatibility with existing systems.
Entities must establish a process for communications management that allows them to:
BANCO CENTRAL
DE LA REPÚBLICA ARGENTINA
Maintain detailed and up-to-date documentation of the network design, interfaces, connec- tions and security elements.
Ensure the generation and preservation of activity logs of network devices.
Establish measures for real-time network monitoring and network traffic analysis.
Define metrics for anomaly detection and evaluation of the quality and availa- bility level of network services.
Perform periodic reviews of the communications infrastructure that allow them to identify possible weaknesses.
Entities must establish management processes for the planning, execution, monitoring and control of technology operations that allow:
Define roles and responsibilities that mitigate the risks associated with inadequate segregation of duties.
Define mechanisms that ensure the traceability of process execution.
Implement controls that ensure that the efficiency of their operations aligns with business needs.
Define controls that allow processing to be resumed upon detection of failures or problems in the normal execution flow.
Ensure that all activities are documented.
In addition, entities must establish measures for the detection, analysis, recording and correction of errors and exceptions.
In accordance with the established business continuity strategies and the data management model, entities must define a strategy for performing backups that guarantees the availability and integrity of data and information systems.
Additionally, a process must be established to manage the life cycle of these backups, which includes:
The definition of procedures for performing, testing and restoring backups that indicate, at a minimum: the scope, frequency, types of media, retention periods and the number of backup copies.
The application of controls in the performance and preservation of backups that mitigate the risks of modification or deletion of information during the retention period.
The implementation of access controls, protection mechanisms and encryption for backup copies, in accordance with the classification of information and the management of vulnerabilities and threats.
Measures that provide protection against malware replication and data corruption.
The preservation of offline copies, in accordance with the classification of data and information.
Based on legal and regulatory requirements, entities must establish the retention periods for historical backup copies, and make at least two copies of customer, accounting-financial and transactional information. In addition, procedures and resources must be defined that allow the use of the safeguarded information at any point in its life cycle.
Entities must implement processes for monitoring the technological infrastructure and the processing of operations to prevent, detect and respond in a timely manner to unwanted events, as well as to obtain information on the performance of capacities and operation.
Indicators must be established that allow measuring the performance of the technological infrastructure and processing, both for internal services and those provided by third parties.
The following must be considered, at a minimum:
Use of resources and availability of own and third-party services.
Response time or average connection time per service.
System failures.
Efficiency of transaction processing.
Change and update management metrics.
Technology service management metrics.
The results of infrastructure and processing monitoring must be considered for continuous improvement and update planning in accordance with the enterprise architecture. Likewise, the results of monitoring management must be periodically reported to Senior Management.
CENTRAL BANK
OF THE ARGENTINE REPUBLIC
Section 8: Cyber incident management
In accordance with the consolidated texts on "Response and recovery guidelines for cyber incidents" and "Protection of users of Financial Services", entities must establish a cyber incident management framework that includes technical and organizational measures that allow them to minimize impacts and contain their propagation through the application of controls for response and recovery.
The management framework must be aligned with:
The strategic objectives of the business.
Technology and information security risk management.
The information security management framework.
The business continuity management framework.
The technological infrastructure management processes.
The critical processes of the entity and those associated with the regulations for the protection of users of financial services.
Policies for cyber incident management must define, at a minimum:
The scope and participating areas of the response to cyber incidents for the entity, indicating the roles and responsibilities of each area.
The objectives and priorities of the response aligned with risk management and business continuity.
The principles for prioritizing and escalating cyber incidents.
The metrics for carrying out controls for effective management.
Entities must establish rules and procedures that allow them to manage, control and document cyber incident management activities; contain the impact and restore capabilities and services, and prevent new incidents and investigate causes.
The rules and procedures must contain, at a minimum:
The circuits and flows of activities to be followed by the entity in the event of cyber incidents, and the criteria for prioritization and escalation.
The definition of a taxonomy that contains the identification and description of the cyber incidents considered by the entity.
The description of the responsibilities of the areas participating in the response to cyber incidents, including the evaluation of legal aspects, the coordination of internal and external communication, and the investigation of the root cause.
Criteria for prioritizing the attention of cyber incidents based on the criticality or impact for the business, services, processes or affected persons.
The alignment of activities with the business continuity policy when applicable.
Criteria for forensic analysis and investigation and for the preservation of evidence.
Internal and external communication circuits.
In accordance with the risk assessment, definitions referring to the preservation of evidence for subsequent investigation in compliance with adopted forensic practices.
8.1.1. Registry and repository of cyber incidents
Entities must establish and maintain a complete record of their cyber incidents that allows the identification, traceability and evidence of the actions taken until their closure.
For this purpose, a repository must be established for the registration of the cyber incident and the evidence that allows ensuring its integrity, traceability, availability and confidentiality.
In addition, entities must keep a record of the monitoring of activities until the identification of the root cause of cyber incidents in order to ensure their resolution and prevent their recurrence. When the source is not under the entity's control, evidence of the actions taken to manage its monitoring must also be left.
The recorded information must be analyzed in order to detect the correlation between them to prevent new cyber incidents or for the investigation of root causes.
When cyber incidents are related to or arise from customer claims or possible frauds, the respective records must be linked in order to carry out joint monitoring and identify all actions executed.
The procedures related to cyber incident investigation must allow:
Identify those incidents that will require the preservation of evidence for subsequent investigation.
The preservation of evidence for investigation by the authorities in line with good practices in computer forensics.
The communication and notification procedures must allow effective communication of cyber incidents so that the response is timely and planned. Entities must define:
Roles for the attention to different incidents or scenarios.
Mechanisms for communication with third parties, for the management and reporting of cyber incidents to the authorities.
A point of contact to report cyber incidents for employees, third parties and the general public, in order to mitigate the impact in a timely manner.
Entities must establish a testing plan for the activities provided for cyber incident response that includes, at least, the periodicity, objectives and scope of the test.
Different types of tests must be defined that allow evaluating technical capabilities, and the coordination and timely communication between areas. The results must be documented and the lessons learned incorporated into the corresponding plans and procedures.
8.3. Control and management reports
Entities must define a control process over cyber incident management, through procedures, tools and metrics that allow monitoring and evaluation of the tasks carried out, and the identification of improvement opportunities.
The metrics must include indicators or thresholds that allow controlling deviations from what was planned and establishing corrective action plans when necessary. Additionally, the results of continuous improvement activities must be evaluated.
In accordance with their operations, processes and structure, entities must promote the implementation of automated indicators, as well as the generation of alerts upon deviations from the thresholds.
Furthermore, the frequency and formal communication channels for the results of the management of the areas to the Board of Directors and Senior Management must be established.
Section 9: Development, acquisition and maintenance of "software"
Entities must design and implement information systems that allow them to record and process all of their business operations. Systems and applications must include automated controls that:
Ensure integrity and reliability in the entry, processing, updating and consolidation of information.
Limit the modification and deletion of data of completed operations, movements and balances.
Ensure consistency between operating and accounting balances.
Allow the administration of parameters that limit data entry.
Provide adequate integration between the systems that process the entity's information.
Controls must be implemented for the unique identification of the customer and the recording of mandatory data in accordance with current regulations. Additionally, periodic control and cleansing processes must be carried out.
In all systems and applications, authorization schemes must be implemented in accordance with the access control policy for the entry, modification and deletion of operations and parameters.
Functionality must be implemented for the management of users and profiles, and the assignment of permissions on system functions. Additionally, functions must be defined that allow exercising control over the assignment of profiles in accordance with the roles and functions established in the entity.
All systems must generate audit logs that allow ensuring the traceability of each of the actions carried out and contain, at least:
A unique identification.
The type of event or action carried out.
The date and time.
The identification of the users involved.
The identification of the device, application or channel of origin.
In case of modification of parameters, the value before and after the update.
Controls must be established for the preservation of the integrity, availability and confidentiality of all audit logs.
The information that supports the accounting records and the audit logs must be kept in conditions to be recovered for a term of no less than six (6) years. Additionally, they must be available immediately in case the External Systems Audit Management of the Superintendency of Financial and Exchange Entities requires them.
Entities must have updated functional, technical and user documentation of their information systems, which considers aspects such as:
Diagram of the system and of the programs that compose it.
Description of the "hardware" and "software", and programming language used.
Interfaces with other systems.
Their interrelation with telecommunications networks.
Description of the main functions and options of the system.
User guides on system functionalities, procedures and outputs.
Entities must have automated systems or processes for the generation of the reporting regimes required by the Banco Central de la República Argentina.
In addition, controls must be implemented to limit manual intervention by users in the process and the making of adjustments to automatically generated information.
When there is information that must be entered manually, the following must be implemented:
Specific programs with an adequate authorization scheme.
Controls over the values entered.
Restrictions that prevent the alteration of automatically generated information.
Complete traceability of operations.
Entities must establish a framework for managing the lifecycle of software development, acquisition and maintenance that contemplates:
Strategic business objectives.
The enterprise architecture.
Risk assessment and the implementation of mitigation controls in accordance with guidelines established in section 3. Technology and information security risk management.
The established project management methodologies and the applicable aspects of Section 4. Information Technology Management.
The applicable aspects of Section 5. Information security management.
The change management requirements defined in Section 7. Technological infrastructure and processing.
This management framework must establish at a minimum:
The assignment of roles and responsibilities.
The documentation describing the methodologies to be used in the software lifecycle.
Criteria for the evaluation of requirements.
Procedures for the evaluation and selection of suppliers.
Evaluation procedures for the incorporation or integration of third-party components in the software lifecycle. This includes open source, APIs and artificial intelligence or machine learning algorithms.
Criteria for the construction and use of artificial intelligence models, the processes of collecting and preparing training data, the activities of verification and validation of responses.
Standards that establish good practices for the development and maintenance of softwa- re.
Controls to ensure the availability and updating of source programs, and the do- cumentation technical and functional.
Procedures for the implementation of threat modeling.
Procedures that establish the criteria for conducting software testing and for code review.
Training and awareness plans in accordance with the defined roles and responsibilities.
Procedures for security assessments in the acquisition of software and in the in- corporation of third-party software components into own developments.
Procedures that establish criteria for software quality and its assurance.
Within the management framework of the software development, acquisition and maintenance lifecycle, the functional, regulatory and security requirements of the software must be identified, defined and documented.
Additionally, the results of the security and functionality assessments carried out must be documented, especially:
When software components developed by third parties are integrated into the lifecycle.
When the systems or applications integrate services that allow the exchange of data with third parties.
Entities must adhere to the standards and procedures defined for secure development and threat modeling. In addition, each project must have the documentation established in the methodology used. Mechanisms must be defined to verify the integrity of the software throughout the entire lifecycle.
Entities must establish and execute software or component testing plans that are in accordance with the results of risk analyses and allow:
To determine and document the scope based on the identified risks.
To combine different approaches of automated and manual testing.
To determine the risks linked to the testing processes and the difficulty in documenting and predicting AI responses, which justify the need for continuous monitoring with metrics previously established in the system operation stage (post-implementation).
To document the design, creation and preparation of test data that consider the protection of personal or sensitive data.
To review and periodically update the software validation and testing rules.
To perform and document specific tests before the implementation of changes or new versions of own and third-party software.
To evaluate and accept the test results before the implementation of changes in production environments.
To communicate the test results to contribute to continuous improvement.
On the other hand, entities must have vulnerability tests performed by independent third parties on the applications that handle customer, transactional or financial data.
The findings detected in the source code review and in the security tests must be documented. In addition, risks must be recorded and evaluated, and measures for their treatment and acceptance must be established.
For the implementation of software in production environments, the requirements established for change management must be considered and controls must be established to ensure the integrity and traceability of software code versions.
Entities must establish procedures for the maintenance and control of the systems and applications they consider:
Evaluation and updating of obsolete components, both own and third-party.
Changes in third-party services consumed by the entity's systems.
The results of vulnerability management.
The evolution of systems and applications that use artificial intelligence and machine learning algorithms.
Entities must define a process with the objective that software complies with quality and security standards, good practices, and the legal and regulatory framework. The roles and responsibilities related to quality assurance must be independent of the development and testing areas.
This process must include, at a minimum, standards and procedures related to the review and inspection of:
Compliance with procedures and the application of defined methodologies.
The execution of defined test plans.
The training of team members based on tools, technologies, and security aspects.
In addition, metrics and indicators must be established to evaluate software management and monitoring activities against defined thresholds.
Entities must consider the results of the quality assurance process for the continuous improvement of the management framework for the software development, acquisition, and maintenance lifecycle.
BANCO CENTRAL
DE LA REPÚBLICA ARGENTINA
Section 10. Management of the relationship with third parties
Entities may delegate to third parties processes, services and/or activities related to technology and information security processes, in accordance with the provisions of section 2 of the Ordered Text "Expansion of financial entities".
The following are not covered by the requirements of this section:
Services that provide general information about financial markets.
Services of mandatory adoption by regulation of the financial system.
Services provided by State agencies.
Banking correspondent activities.
Credit card payment processing services.
Processes, services and/or activities may not be delegated to third parties that perform internal and/or external audit functions at the entity.
Delegations of processes, services or activities to third parties do not imply the transfer of the primary responsibilities set forth in this regulation.
Based on their operations, processes and structure, entities must consider establishing a sector or function responsible for managing the relationship with third parties.
Prior to the start of the relationship, entities must inform the characteristics of the process, service and/or activity to be delegated to the External Systems Audit Management of the Superintendence of Financial and Exchange Entities.
Entities must establish a policy and framework for the management of processes, services and/or activities delegated to third parties that considers:
The definition of roles and responsibilities for the different management activities.
Security measures in accordance with the results of technology and security risk management; and the risks inherent to the delegation.
Procedures for the selection and contracting of third parties.
The identification and documentation of delegated services and activities.
The identification of contact points for legal aspects and those related to technology, information security and cyber incident management.
The preparation and maintenance of a catalog with information on services and activities delegated to third parties.
The continuity of services in accordance with the results of risk analyses.
Mechanisms for managing conflicts of interest.
Mechanisms for managing cyber incidents.
The preparation of procedures for monitoring compliance with formalized agreements.
The implementation of independent audits on services and activities managed by third parties that allow evaluating risk management and alignment with the entity's technology and information security processes.
On the other hand, entities must evaluate possible scenarios of planned or forced termination of the processes, services or activities provided by third parties, and establish termination plans that allow them to mitigate the risks of interruption, non-compliance with legal and regulatory requirements, or degradation of quality. The termination plans must consider the obtaining of data, source programs, and the documentation of the systems and applications.
Entities must in all cases formalize relationships with third parties that provide delegated processes, services and/or activities in accordance with established procedures. At a minimum, the following must be established:
The nature, scope of the processes, services and/or activities to be delegated and the responsibilities of the parties.
The duration of the contracting or delegation and specific clauses that regulate automatic renewal.
The minimum service levels and performance metrics.
The existence of continuity plans.
The rights to conduct audits by the entity.
The communication mechanisms regarding changes that may affect the conditions in the provision of the service.
Confidentiality agreements.
Mechanisms for dispute resolution.
Coordinated procedures for cyber incident management.
Compliance with the applicable legal and regulatory framework.
Provisions that allow unrestricted access by the Superintendency of Financial and Exchange Entities to the facilities, control areas and related documentation.
The notification mechanisms regarding changes in share control and changes in management levels of third parties.
Responsibilities in the complaint circuits of clients or users of financial services of the entity.
Communication procedures and protocols that allow effective compliance with controls over delegated processes, services and activities.
The formal designation of a responsible person representing the third party for handling aspects related to the delegation, in accordance with the characteristics of the service and the results of the risk analyses.
The mechanisms for the elimination of the entity's data managed by third parties, once the relationship is terminated.
The procedures for the termination of services in accordance with the risk assessment.
The documents that formalize the contracting or delegation must contain provisions that ensure that the processes, services and activities delegated to third parties comply with the requirements demanded in this regulation, in accordance with their risk assessment.
SWIFT and EUROCLEAR financial messaging services will be evaluated taking into account their particular contracting conditions.
The documents that formalize the contracting or delegation with third parties must formally establish the responsibility of the primary provider regarding:
All processes, services and/or activities provided by itself or through subcontractors, regardless of geographic location.
Notification to the entity of all subcontracting with the identification of the services and activities involved.
In addition, all subcontractors must formally assume:
The responsibility to comply with the applicable legal and regulatory framework.
The assignment of access and audit rights, both for the entity and for the Superintendency of Financial and Exchange Entities.
Entities must define a control process that allows them to monitor and evaluate the technology and information security processes, services and activities delegated to third parties.
There must be procedures for the execution of controls over third parties, the evaluation of compliance with regulatory requirements and agreed service levels, and the follow-up of requests for remediation, in case of non-compliance.
The frequency of control and monitoring activities must be defined in accordance with the level of risk and the criticality of the delegated processes, services or activities.
Reports of evaluations carried out by independent third parties on the processes, services and activities delegated to third parties will be considered complementary to the entity's control and monitoring activities, provided that:
They are prepared in accordance with internationally accepted processes.
The scopes and results allow verifying the implemented controls.
Additional audits or review activities are carried out when the scope does not cover all the regulatory requirements and identified risks.
Internal audits must be carried out on the processes, services and activities delegated to third parties, including reviews of compliance with legal and regulatory requirements. The reports must be sent to the External Systems Audit Management of the Superintendency of Financial and Exchange Entities.
The frequency of the audit reports must be defined in accordance with the level of risk and the criticality of the delegated services or activities.
CENTRAL BANK OF THE ARGENTINE REPUBLIC
Additionally, the reports of the external auditors carried out on the occasion of their reviews of the services and activities delegated to third parties must be sent to the External Systems Audit Management.
Section 11: Electronic Channels
Financial entities that participate in the provision, by themselves or by third parties on their behalf, of financial services through any of the following Electronic Channels (EC), whose definition and characteristics are in the Glossary of point 11.6., are covered:
11.1.1. Automated Teller Machines (ATM).
11.1.2. Self-Service Terminals (SST).
11.1.3. Mobile Banking (MB).
11.1.4. Telephone Banking (TB).
11.1.5. Internet Banking (IB).
11.1.6. Point of Sale (POS).
11.1.7. Mobile Payment Platform (MPP).
By way of reference and with the aim of facilitating the implementation of the security requirements determined in this section, Electronic Channel Security Management is understood as the cycle of processes that bring together different tasks, specialties and functions, in an integrated and interrelated, repeatable and constant manner for the administration, planning, control and continuous improvement of computer security in Electronic Channels.
The Reference Processes indicated here bring together the set of tasks and specialties that entities may have, with these or other denominations and in the organic composition that best serves their interests and satisfies the functionalities and purposes described. On the other hand, they must inform the External Systems Audit Management of the organic and operational structure and interrelations that correspond in their organizations:
Process related to the acquisition and delivery of knowledge in security practices, their dissemination, training and education, for the development of preventive, detective and corrective tasks for security incidents in Electronic Channels.
Process related to the evaluation, development and implementation of security measures for the protection of identity, authentication mechanisms, segregation of roles and functions and other characteristics of access to Electronic Channels.
11.2.3. Integrity and Logging (IL)
Process aimed at the use of techniques for controlling the integrity and logging of data and transactions, as well as the handling of sensitive information of Electronic Channels and the techniques that provide traceability and allow its verification. Includes, but is not limited to transactions, audit logs and validation schemes.
Process related to the collection, analysis and control of events in the face of failures, unavailability, intrusions and other situations that affect the services offered by Electronic Channels, and that may generate eventual damage to the infrastructure and information.
Process related to the treatment of events and consequent security incidents in Electronic Channels, their detection, evaluation, containment and response, as well as escalation and correction activities of the technical and operational environment.
In addition to the technical-operational requirements indicated, financial entities must satisfy the following general requirements regardless of the nature, composition and structure of the services they provide through their Electronic Channels.
11.3.1.1. They must frame the operation of the Electronic Channels they manage within the scenarios included in the Scenario Matrix of point 11.5., implementing at a minimum and according to the criticality established, the requirements indicated for each applicable scenario.
11.3.1.2. In light of the rules on "Guidelines for Risk Management in Financial Entities", entities must include in their operational risk analysis all IT assets related to the applicable scenarios, establishing a level of criticality equivalent to that indicated by this Central Bank for each scenario or, when not indicated, by the provisions of point 11.4.2.
11.3.1.3. The provisions of point 11.3.1.2. must be documented and form part of the operational risk management methodology of the financial entity. In turn, it is complementary to the periodic risk analyses and the IT security mechanisms implemented to minimize the risks detected.
11.3.1.4. Framing errors detected by internal and/or external audits oblige entities to make the corresponding adjustments within a period no greater than 180 calendar days following their notification, and they must submit to the Superintendency of Financial and Exchange Entities a report of the adjustments made, endorsed by a conformity verification of their
CENTRAL BANK
OF THE ARGENTINE REPUBLIC
Internal Audit, after the expiration of the indicated period. The Superinten- dency of Financial and Exchange Entities may carry out a verification of the actions taken
11.3.2.1. Entities must develop, plan and execute a protection plan for their assets, processes, technical and human resources related to the Electronic Channels under their responsibility, based on a risk analysis with a minimum annual update, on its correspondence with the Scenario Matrix and on the technical-operational requirements detailed in points 11.7. and subsequent.
11.3.2.2. Within security management tasks, and regardless of the area, persons or third parties in charge of the function and execution of the tasks, entities must have functions and tasks related to the following strategic security processes for their Electronic Channels:
11.3.2.2.1. Awareness and Training. In addition to the provisions of point 11.2.1., entities must have an annual, measurable and verifiable IT security awareness and training program, whose contents contemplate all internal and external needs in the use, knowledge, prevention and reporting of incidents, escalation and responsibility of the Electronic Channels they have.
11.3.2.2.2. Access Control. In addition to the provisions of point 11.2.2., entities must acquire, develop and/or adapt the mechanisms implemented for the verification of the identity and privileges of internal and external users, establishing a strategy based on the interoperability of the financial system, the reduction of complexity of use and the maximization of the protection of the user of financial services.
11.3.2.2.3. Integrity and Logging. In addition to the provisions of point 11.2.3., entities must guarantee complete logging and traceability of the activities of the Electronic Channels in a secure environment for their generation, storage, transport, custody and recovery.
11.3.2.2.4. Monitoring and Control. In addition to the provisions of point 11.2.4. entities must have technical and human resources available to ensure permanent and continuous control of all their Electronic Channels and a classification of recordable events, as well as search and correlation patterns.
11.3.2.2.5. Incident Management. In addition to the provisions of point 11.2.5., entities must make the necessary efforts to have in their organizations or through third parties under their own coordination and control, work teams specialized in the attention, diagnosis, analysis, containment, resolution, escalation and reporting of security incidents of all their Electronic Channels, in a formal and integrated manner.
11.3.3. On the responsibility over Electronic Channels
11.3.3.1. The Board of Directors or equivalent authority of the entity is the primary responsible for the IT security management of the operation of Electronic Channels from the first moment in which its clients subscribe to the services offered through them or receive means of payment issued by them or on their behalf for their use within the scope established in the service agreement.
11.3.3.2. The responsibility of financial entities in the services and operations carried out through Electronic Channels includes, but is not limited to, the operational, physical and logical means of access and exchange of information with users, the infrastructure for processing, transport and custody of operational and financial information. It excludes those physical or logical means owned and exclusively held by clients, provided that they allow limiting their use and availability to compatibility with the mechanisms necessary to provide a secure financial service.
11.3.3.3. Companies providing processing, transport, custody and/or IT security tasks or processes related to the Electronic Channels of financial entities, including owners of licenses or trademarks that by agreement with financial entities facilitate the use of their resources and infrastructure, are covered by the conditions established in Section 2. of the rules on “Expansion of financial entities” and in other complementary technical regulations.
11.3.3.4. Financial entities must establish and inform this Central Bank of the organizational structure arranged and the list of persons responsible for tasks related to the Reference Processes indicated in point 11.2. and report any news or change made to it within a period no greater than 10 business days after the event occurred. This information includes: the processes, tasks and responsible parties in service provider companies where part or all of the Electronic Channel services are decentralized.
11.3.3.5. Proposals for the implementation of a new EC or a different modality from those contemplated in this section, following a risk analysis by the financial entity, must be reported at least 60 days in advance to the Principal Information Security Management, so that, together with the Principal Payment Systems and Checking Accounts Management, they analyze the particular scope, technical characteristics and impact of the implementation and, if applicable, provide any recommendations they consider necessary or make the corresponding regulatory adjustments.
Each scenario is composed of: a thematic grouping category, a situation considered within the category, a determination of the applicability of the scenario in the Electronic Channels considered, a criticality value that indicates the relative importance of the scenario and that affects the minimum requirements considered and, finally, a set of technical-operational requirements to control the described situation.
A scenario is presented as a row within the matrix. Three categories are used, which group the main scenarios of interest:
Credentials and Means of Payment (CM). It refers to the elements provided for the identification, authentication and authorization of access/use of the means and devices of the Electronic Channels. It includes those physical and logical elements that function as consumption mechanisms, cash substitutes, which allow generating financial debit or credit transactions in client accounts.
Device/Application (DA). It refers to the characteristics of the devices and physical and logical pieces involved in the operation of the respective Electronic Channels.
Transactions (TR). It refers to the nature of the financial, operational and inquiry operations that the Electronic Channel allows to perform.
The situations describe the particular scenario subject to treatment and for which particular minimum technical-operational requirements have been determined.
Applicability is determined for the Electronic Channels considered in the rule and in the particular scenario. Not all channels are subject to the same described scenario.
Criticality is a weighting factor that establishes the level of relative importance of a scenario and its regulatory needs. Entities must implement the necessary mechanisms to consider the applicability of the scenario to their particular context and its inclusion in the operational technology risk matrix used in their operational risk management in accordance with the provisions of points 11.4.1. and subsequent.
The level of obligation of entities to comply with the technical-operational requirements is determined by three elements: the assigned criticality, the validity determined in each technical-operational requirement and the results of the risk management of the financial entities.
The criticality values, the criteria used for their assignment to each scenario and compliance are determined as indicated in the following table.
CENTRAL BANK OF THE ARGENTINE REPUBLIC
Value Description Assignment criteria Compliance 1 High exposure to risk whose lack or deficiency of treatment affects in an extended manner the availability of the services and the reliability of the CE(s), the financial entity and the financial system in general. Exposure to systemic risk and propagation of the negative effect. Economic im- pact on customers and the financial entity. Level of pene- tration of the Elec- tronic Channel and associated Payment Method. Interoperability and effects on other CE. Mandatory. Financial entities must satisfy the technical- operational requirements of each sce- nario in accordance with the corres- ponding Requirements Table (point 11.7). 2 Moderate exposure to risk whose lack or deficiency of treat- ment affects in a limited manner the availability and reliability of the CE(s) involved, the financial entity and the financial system in general. Aligned. Entities must make their best efforts to satisfy the technical-operational requirements of each scenario, implementing com- pensatory and/or alternative meas- ures in those requirements that do not satisfy those indicated in the Requirements Table corresponding (point 11.7). 3 Low exposure to risk whose lack or deficiency of treatment affects in a limited manner the availa- bility and reliability in the CE(s) involved, the entity or the financial system in gene- ral. Expected. Entities may satis- fy the requirements in accordance with the formal results of their risk management
The assignment of the values in each scenario is a power of this Central Bank. However, when a value is not assigned to a given scenario, financial entities must assign it following the criteria established in the table and the formal results of their operational risk management. This Central Bank may carry out periodic updates of these values, adapting them in accordance with the result of its verifications, the behavior of the financial system and the national context.
| Scenario Matrix | |||||
|---|---|---|---|---|---|
| Category | Scenario | Situation | Applicability | Criticality | Requirements |
| Credentials and Payment Methods | ECM001 | Generation, distribution, and disposal of credentials that include TC/TD. | ATM; TAS and POS. | RCC001; RCC005; RCC006; RCC007; RCC008; RCC010; RCC013; RCC014; RCA001; RCA003; RCA009; RCA011; RCA012; RCA015; RCA016; RCA017; RCA018; RCA019; RCA020; RCA021; RCA031; RCA037; RCA038; RCA043; RCA044; RCA045; RIR002; RIR003; RIR005; RIR009; RGI001; RGI002; RGI003 and RGI005. | |
| ECM002 | Generation, distribution, and disposal of Credentials that do not include TC/TD. | BI; BM; PPM and BT. | RCC001; RCC005; RCC006; RCC007; RCC008; RCC010; RCC013; RCC014; RCA001; RCA003; RCA009; RCA011; RCA012; RCA014; RCA016; RCA017; RCA018; RCA019; RCA028; RCA029; RCA037; RCA043; RIR002; RIR003; RIR005; RIR009; RGI001, RGI002; RGI003 and RGI005. | ||
| ECM003 | Subscription, presentation, use, renewal, and cancellation of credentials that include TD/TC. | ATM; TAS; PPM and POS. | 1 | RCC001; RCC002; RCC003; RCC004; RCC005; RCC006; RCC007; RCC008; RCC009; RCC013; RCC014; RCA002; RCA003; RCA004; RCA005; RCA006; RCA007; RCA008; RCA009; RCA010; RCA011; RCA012; RCA013; RCA015; RCA017; RCA018; RCA022; RCA023; RCA025; RCA026; RCA030; RCA031; RCA036; RCA040; RCA041; RCA044; RCA045; RCA048; RIR001; RIR002; RIR003; RIR004; RIR005; RIR006; RIR007; RIR008; RIR009; RIR015; RIR016; RMC005; RMC006; RMC007; RMC008; RMC009; RMC010; RGI001, RGI002; RGI003 and RGI005. | |
| ECM004 | Subscription, submission, use, renewal and deactivation of credentials without TD/TC. | BI; BM; PPM; TAS and BT. | 1 | RCC001; RCC002; RCC005; RCC006; RCC007; RCC008; RCC009; RCC011; RCC013; RCC014; RCA002; RCA003; RCA004; RCA005; RCA007; RCA008; RCA009; RCA010; RCA011; RCA012; RCA014; RCA017; RCA018; RCA022; RCA023, RCA024; RCA026; RCA027; RCA028; RCA030; RCA039; RCA040; RCA041; RCA042; RIR001; RIR002; RIR003; RIR004; RIR005; RIR007; RIR009; RIR015; RIR016; RMC001; RMC005; RMC006; RMC008; RMC010; RGI001, RGI002; RGI003 and RGI005. |
Scenario Matrix (continued)
| Category | Scenario | Situation | Applicability | Criticality | Requirements |
|---|---|---|---|---|---|
| Devices/Applications | EDA001 | Design, functionality and approval of devices supplied by the entity or the operator. | ATM; POS and TAS. | RCC006; RCC012; RCC010; RCC013; RCA020; RCA033; RCA034; RCA036; RCA037; RCA038; RIR001; RIR002; RIR003; RIR004; RIR005; RIR009; RIR010 and RIR011. | |
| EDA002 | Compatibility of the user's own devices. | BI; BT; PPM and BM. | 2 | RCC006; RCC010; RCC011; RCC013; RCA034; RCA035; RCA037; RIR012; RIR017 and RIR019. | |
| EDA003 | Design, functionality and approval of applications for user interaction with the CE, supplied by the entity/operator. | BI; BT; PPM and BM. | RCC006; RCC010; RCC012; RCC013; RCA027; RCA033; RCA034; RCA037; RIR001; RIR002; RIR003; RIR004; RIR005; RIR009; RIR010; RIR011; RIR012 and RIR017. | ||
| EDA004 | Operations and maintenance of devices/applications with physical handling of valuables. | ATM; TAS and POS. | RCC001; RCC005; RCC006; RCC007; RCC008; RCC009; RCC010; RCC012; RCC013; RCA012; RCA013; RCA015; RCA018; RCA023; RCA026; RCA033; RCA037; RCA040; RIR002; RIR003; RIR004; RIR005; RIR006; RIR007; RIR008; RIR009; RIR010; RIR014; RIR015; RIR018; RMC003; RMC006; RMC007; RMC009; RMC010; RMC012; RMC013; RGI001; RGI002; RGI003 and RGI005. | ||
| EDA005 | Operations and maintenance of devices/applications without physical handling of valuables. | BI; BT; PPM and BM. | RCC001; RCC005; RCC006; RCC007; RCC008; RCC009; RCC010; RCC012; RCC013; RCA012; RCA013; RCA014; RCA018; RCA023; RCA026; RCA033; RCA037; RCA040; RIR002; RIR003; RIR004; RIR005; RIR007; RIR009; RIR010; RIR014; RIR015; RMC001; RMC003; RMC006; RGI001; RGI002; RGI003 and RGI005. |
Scenario Matrix (continued)
| Category | Scenario | Situation | Applicability | Criticality | Requirements |
|---|---|---|---|---|---|
| Transactions | ETR001 | Deposit of physical securities at the CE for direct destination to accounts or payments for goods and services. | ATM and TAS. | RCC001; RCC002; RCC003; RCC004; RCC005; RCC006; RCC007; RCC008; RCC009; RCC013; RIR002; RIR003; RIR004; RIR005; RIR006; RIR007; RIR008; RIR009; RIR014; RIR015; RIR016; RMC001; RMC002; RMC006; RMC008; RMC009; RGI001; RGI002; RGI003 and RGI005. | |
| ETR002 | Cash withdrawal by CE. | ATM. | 1 | RCC001; RCC002; RCC003; RCC004; RCC005; RCC006; RCC007; RCC008; RCC009; RCC013; RCA032; RCA040; RCA046; RCA047 RIR002; RIR003; RIR004; RIR005; RIR006; RIR007; RIR008; RIR009; RIR014; RIR015; RIR016; RMC001; RMC002; RMC004; RMC005; RMC006; RMC008; RMC009; RMC011; RGI001; RGI002; RGI003 and RGI005. | |
| ETR003 | Payment for goods or services. | ATM; TAS; POS; BI; BM; PPM and BT. | 2 | RCC001; RCC002; RCC003; RCC004; RCC005; RCC006; RCC007; RCC008; RCC009; RCC011; RCC013; RCA032; RCA040; RCA046; RCA047; RIR002; RIR003; RIR004; RIR005; RIR006; RIR007; RIR008; RIR009; RIR013; RIR014; RIR015; RIR016; RMC001; RMC002; RMC004; RMC005; RMC006; RMC008; RMC009; RMC011; RGI001; RGI002; RGI003 and RGI005. | |
| ETR004 | Transfers of funds between accounts of the same holder and same financial institution. | ATM; TAS; BI; BM and BT. | RCC001; RCC002; RCC003; RCC004; RCC005; RCC006; RCC007; RCC008; RCC009; RCC011; RCC013; RCA040; RCA046; RCA047; RIR002; RIR003; RIR004; RIR005; RIR006; RIR007; RIR008; RIR009; RIR014; RIR015; RIR016; RMC001; RMC002; RMC004; RMC005; RMC006; RMC008; RMC009; RMC011; RGI001; RGI002; RGI003 and RGI005. | ||
| ETR005 | Immediate Transfers. | ATM ; BM and BI. | 1 | RCC001; RCC002; RCC003; RCC004; RCC005; RCC006; RCC007; RCC008; RCC009; RCC011; RCC013; RCA032; RCA040; RCA046; RCA047; RIR002; RIR003; RIR004; RIR005; RIR006; RIR007; RIR008; RIR009; RIR013; RIR014; RIR015; RIR016; RMC001; RMC002; RMC004; RMC005; RMC006; RMC008; RMC009; RMC011; RGI001; RGI002; RGI003 and RGI005. | |
| ETR006 | Ordinary transfers | ATM; TAS; BI and BM. | 1 | RCC001; RCC002; RCC003; RCC004; RCC005; RCC006; RCC007; RCC008; RCC009; RCC011; RCC013; RCA032; RCA040; RCA046; RCA047; RIR002; RIR003; RIR004; RIR005; RIR006; RIR007; RIR008; RIR009; RIR013; RIR014; RIR015; RIR016; RMC001; RMC002; RMC004; RMC005; RMC006; RMC008; RMC009; RMC011; RGI001; RGI002; RGI003 and RGI005. |
CENTRAL BANK OF THE ARGENTINE REPUBLIC
Scenario Matrix (continued)
| Category | Scenario | Situation | Applicability | Criticality | Requirements |
|---|---|---|---|---|---|
| ETR007 | Application, formalization and accreditation of credit operations. For pre-approved credits, RMC012 applies with criticality 1. | ATM; TAS; BI and BM. | RCC001; RCC002; RCC003; RCC004; RCC005; RCC006; RCC007; RCC008; RCC009; RCC011; RCC013; RCA032; RCA040; RIR002; RIR003; RIR004; RIR005; RIR006; RIR007; RIR008; RIR009; RIR014; RIR015; RIR016; RMC001; RMC002; RMC004; RMC005; RMC006; RMC008; RMC009; RMC011; RMC012; RGI001; RGI002; RGI003 and RGI005. | ||
| ETR008 | Query transactions, operational instruction or financial instruction with confirmation via traditional channel. | ATM; TAS; BI; BT and BM. | RCC001; RCC002; RCC003; RCC004; RCC005; RCC006; RCC007; RCC008; RCC009; RCC011; RCC013; RIR002; RIR003; RIR004; RIR005; RIR006; RIR007; RIR008; RIR009; RIR014; RIR015; RIR016; RMC001; RMC006; RMC008; RMC009; RGI001; RGI002; RGI003 and RGI005. | ||
| ETR009 | New transactional operations not contemplated in other scenarios, with or without movement of funds. | ATM; TAS; POS; BI; BT; PPM and BM. | 2 | RCC001; RCC002; RCC003; RCC004; RCC005; RCC006; RCC007; RCC008; RCC009; RCC011; RCC013; RCA032, RCA040; RCA046; RCA047; RIR002; RIR003; RIR004; RIR005; RIR006; RIR007; RIR008; RIR009; RIR013; RIR014; RIR015; RIR016; RMC001; RMC002; RMC004; RMC005; RMC006; RMC008; RMC009; RMC011; RGI001; RGI002; RGI003 and RGI005. | |
| ETR010 | Low Value transactions: cash withdrawals, payment for goods and/or services and immediate transfers. | ATM; POS; BI; BM and PPM | 2 | RCC001; RCC002; RCC003; RCC004; RCC005; RCC006; RCC007; RCC008; RCC009; RCC011; RCC013; RCA040; RCA046; RCA047; RIR002; RIR003; RIR004; RIR005; RIR006; RIR007; RIR008; RIR009; RIR013; RIR014; RIR015; RIR016; RMC001; RMC002; RMC004; RMC005; RMC006; RMC008; RMC009; RMC011; RGI001; RGI002; RGI003; RGI005. |
11.6. Glossary
The definition applicable to the terms and acronyms used in this section is included, in alphabetical order, in order to facilitate interpretation and offer greater clarity to the contents.
Asset. It comprises the resources, people and means indispensable for the execution of one or more business processes that are relevant in the expected results of the latter.
Strong Authentication - Two Factor. It comprises the combined use of two authentication factors, that is, two elements of the credentials of different factor. Additionally, consider what is stated about Authentication Factors and Credentials.
Electronic Banking. It comprises any financial service offered by an entity and based on the use of technology for the execution of operations and transactions by a user of financial services, with minimal or no assistance or participation of a human operator. Electronic Banking includes but is not limited to the implementation of Electronic Channels with the characteristics indicated in this standard.
Mobile Banking (MB). It comprises the networks, devices, computer, operational and service environments intended for the user of financial services, which are based on the use of computer applications (programs) designed for their implementation and operation on the user's own mobile devices, which link the device, the application and the client's credentials uniquely to a financial services platform, in a processing center of the entity (own or of a third party) and communicate, through public communication networks suitable and approved by competent authority for the transmission of voice and data under the administration of a public or private operator.
Internet Banking (IB). It comprises the networks, devices, computer, operational and service environments intended for the user of financial services, which are based on the use of computer programs designed for their operation through access to sites published on the Internet, under the administration of an entity or operator and the use of navigation engines installed on the user's own devices, which communicate with a processing center of the entity (own or of a third party) through public communication networks suitable and approved by competent authority for the transmission of data under the administration of a public or private operator.
Telephone Banking (TB). It comprises the networks, devices, computer, operational and service environments intended for the user of financial services, which are based on the use of computer programs designed for their operation with telephones owned or not by the financial consumer and which communicate with a processing center of the entity (own or of a third party) through public communication networks suitable and approved by competent authority for the transmission of voice and data under the administration of a public or private operator.
Automated Teller Machines (ATM). It comprises the networks, devices, computer, operational and service environments intended for the user of financial services, which are based on the use of devices known as Automated Teller Machines or ATM ("Automated Teller Machine") in their different modalities: Cash Dispensers, Digital Kiosks, among others and that allow at least, the withdrawal of cash without intervention of a human operator.
Electronic Channels (EC). It comprises the means, devices, networks and computer services provided by financial entities, by themselves or through third parties as associated providers, for the instruction of financial operations, with effect on the accounts of one or more users of financial services and/or clients of those entities.
Client - user of financial services - user. The terms "client" and "user of financial services" are equivalent and refer to the natural or legal person who is identifie- ed and subscribed to the services of one or more financial entities. The term "user" is a gene- ric denomination applicable to clients and non-clients.
Countermeasures. It comprises all actions, plans, operational tasks, software or hardware mechanisms arranged to mitigate the risk of occurrence of attack or compromise of a known vulnerability.
Password. Element of the credentials based on a piece of information composed of a sequence of characters or symbols only known by the holder user (factor based on "something he knows") or generated by device (factor based on "something he has").
Dual control. It comprises the process that uses two or more participants separately (individuals, organizations, among others), who operate in concert to protect functions or information of a confidential nature, ensuring that no participant can carry out the function without the intervention of the rest of the participants.
Credentials. It comprises all physical or logical elements provided by the entity/operator, necessary for some or all of the following actions during the use of a specific Electronic Channel: presentation/identification, authentication, request, verification, confirmation/authorization. Additionally, consider what is stated about Authentication Factors.
Public personal data. It comprises data of natural persons that can be obtained from public sources, such as names and surnames, dates of birth, national and labor identification numbers, among others.
Devices. It comprises the physical elements specifically designed and arranged for direct interaction between clients and the Electronic Channel, as well as other users qualified for maintenance and control on site. It includes the logical elements and/or applications necessary to provide functionality and operation to the physical elements.
Encryption - methods. It comprises the methods for the encryption of information with the purpose of achieving confidentiality of its content and limiting its disclosure to the application of a planned decryption mechanism. Some methods considered in this standard include, but are not limited to DES ("Data Encryption Standard"), 3DES (triple encryption of DES), among others.
Escalation - Incident escalation. It comprises the formal protocol and specific procedures for the execution flow and reporting of the activities of reception, diagnosis, analysis, containment, correction and reporting of security incidents in the Electronic Channels.
Security event. It comprises the event that has occurred and been identified regarding the state of a system, service or network that indicates a deviation from the established security policy, a failure of the implemented security measures or a previously unknown situation that may be relevant to security.
Authentication Factors. The credentials used in the Electronic Channels may be of the following type or factor: "something you know" (Password, personal data, among others), "something you have" (Credit/Debit Card, Token, among others), "something you are" (Biometric characteristic).
Positive identification. It comprises the identity verification and validation processes that reduce uncertainty through the use of techniques complementary to those usually used in the presentation of credentials or for their delivery or renewal. Included, but
CENTRAL BANK OF THE ARGENTINE REPUBLIC
not limited to actions related to: in-person identity verification, by me- ans of holographic signature and presentation of identity document, by means of a series of questions challenge of variable context, among others.
Security incident in Electronic Channels. It is made up of the event or series of interrelated security, operational and technological events that generate an unwanted or expected exposure of credentials, transactions, customer data and the associated financial service and that have a significant probability of compromising operations and threatening information security.
Network infrastructure. It comprises all the computing, operational and information resources arranged for the administration, operation, maintenance and transport of voice and data that interconnect and integrate the resources of the technology and systems infrastructure.
Security infrastructure. It comprises all the computing, operational and information resources arranged for the administration, operation, maintenance and control of the technological platform associated with the security of the Electronic Channels.
Technology and systems infrastructure. It comprises all the computing, operational and information resources arranged for the administration, operation, maintenance, processing and control of the information technology services associated with the Electronic Channels.
Journal or Audit Trail. It comprises the physical and/or logical mechanisms arranged for recording the activity of the devices of the Electronic Channels associated with access to services and instruction of operations.
Digital kiosk. It comprises devices with location and physical characteristics similar to ATMs ("Automated Teller Machine") that provide a range of services greater than that provided for these, including but not limited to the services offered by the TAS.
Payment Methods in Electronic Channels. It comprises the physical or electronic means or elements representative and useful for the arrangement of financial operations in Electronic Channels, which include, but are not limited to: payment, debit or credit cards.
"Online" or "offline" operations. The "online" operation occurs when the activity of the electronic service or channel is in a synchronous active state between the different authorization and response points, the device and the operator and/or financial institution, with the validation, authentication and confirmation of credentials and financial transactions being perfected in each transaction. The "offline" operation occurs when the activity of the electronic service or channel is in an asynchronous state between the different authorization and response resolution points, with the perfection of the validation, authentication and confirmation of credentials being necessary regardless of the moment of the validation, authentication and confirmation of the financial transaction.
Operators. The term is used indistinctly to indicate the companies providing financial services within those indicated in this section, that have a service agreement with the financial entities or act on their behalf or whose operations affect the credit and/or deposit accounts of their clients.
Mobile Payment Platform (PPM). Application or computer service for all types of mobile devices and personal computers owned by the user, which allows the association of cards linked in turn to credit or debit accounts, without limit of number, entities or operators, for the instruction of payments and transfers by credit to accounts of third parties adhered or
immediate transfers in demand accounts with agreement of the financial entities and opera- tors of financial transactions of the National Financial System.
Point of compromise. It comprises the individual, company or acquiring merchant of POS in which a similar pattern of suspicious or fraudulent operations with Debit/Credit Cards is detected.
Points of sale (POS). It comprises the networks, devices, computer, operational and financial consumer service environments, which are based on the use of different electronic payment means (Debit/Credit Cards) for the payment of services or financial operations that generate a debit or a credit in the accounts that the client holds with the issuer and that confirm such operations through local or remote communication with a processing center of the issuing entity or third party interested with prior agreement of the issuer, through public communication networks suitable and approved by competent authority for the transmission of data under the administration of a public or private operator.
Private and public networks. Communications infrastructure is considered private when it is administered by a financial entity or a third party on its behalf and accessible exclusively and solely for the technology and systems infrastructure of the financial entity. It is considered public when the communications infrastructure is managed by an independent operator and accessible through prior subscription by multiple companies or individuals.
Financial Services. It includes the provision of foreign exchange and/or financial operations, of legal instruction by financial means or payment for goods and services.
Session on Electronic Channels. It comprises the period during which a consumer (person or business) can carry out financial, operational transactions or permitted inquiries on an Electronic Channel. It shall be understood as composed of the following stages: Presentation (Entry of Credentials, also referred to as Login), Authentication (Validation and authentication of the entered credential values), Request (Selection of the option or transaction chosen by the person/business and the composition of the corresponding message), Verification (Alternative stage for identity verification and revalidation of credentials before a certain type or characteristics of the chosen transaction), Confirmation (Validation and authorization of the transaction and cycle closure). The aforementioned stages are consecutive with the exception of the Authentication stage, which may occur continuing the request stage and before the Verification stage.
Debit/Credit Cards (DC/CC). It comprises elements associated with the access credentials to some Electronic Channels, usually based on plastic pieces whose inscriptions and physical characteristics make them suitable for presentation and reading in authentication and authorization devices for the same. In this regulation they are mentioned in two usual modes of use, as primary means of commercial credit/debit transactions or as primary means of access to financial operations via ATM ("Automated Teller Machine").
Fixed telephony. Communication services offered by telecommunications companies that use the fixed or landline telephony spectra authorized at the national level, and that include voice and data link and exchange services. It requires a personal or commercial subscription with the service leased at a specific domicile.
Mobile telephony. Communication services offered by telecommunications companies that use the mobile telephony spectra authorized at the national level, and that include voice and data link and exchange services. It requires a personal or commercial subscription but is independent of the subscriber's location.
Self-service terminals (SST). It comprises the networks, devices, computer, operational and customer service environments, which are based on the use of the devices known as
CENTRAL BANK OF THE ARGENTINE REPUBLIC
Self-Service Terminals or others of a similar nature, linked to the institutional network of the enti- ty responsible, whether by direct or indirect connection (branch, provider) to a pro- cessing center and that allow at least the deposit and transfer of funds and exclude the with- drawal of cash without the intervention of a human operator.
Low-Value Transactions. Financial transactions through Electronic Channels enabled up to the maximum established in Communication "A" 5982 and its amendments.
BANCO CENTRAL
DE LA REPÚBLICA ARGENTINA
| Awareness and Training requirements table | ||
|---|---|---|
| Requirement code | Requirement description | Scope |
| RCC001 | The contents of the CC program must be formulated and kept updated based on an analysis of vulnerabilities and the results of Incident Management, and include, but not be limited to incidents: reported, detected and known. | |
| RCC002 | The contents of the CC program must include: techniques for the detection and prevention of appropriation of personal data and credentials through attacks of the type "social engineering", "phishing", "vishing" and others of similar characteristics. | |
| RCC003 | The contents of the CC program must include: techniques for the detection and prevention of "skimming" and appropriation of credential data through physical intervention techniques. | |
| RCC004 | The contents of the CC program must include: techniques for the detection of suspicious situations in the premises or environment of access to the EC. | |
| RCC005 | Keep internal personnel, personnel responsible for the management of the EC, third-party personnel involved in operational tasks and clients informed about the communication channels for the receipt of complaints or problems in the circuit associated with the described scenario. | |
| RCC006 | Regarding the audience of the CC program, the following criteria must be applied: a. Characteristics and segmentation of the audience, according to the level of intervention in the process and nature of the function or role held by each participant. b. All necessary participants in the complete flow of the activity indicated in the scenario must be covered. c. Oriented but not limited to: internal personnel, personnel responsible for the management of the EC, providers and clients. | |
| RCC007 | With a minimum annual periodicity, an analysis of the executed CC Program must be carried out that measures the evolution of incidents, with respect to the CC activities carried out, including at least: a. A report of the quantity and segmentation of recipients and contents of the CC program. b. A comparison between the contents covered by the CC program and the quantity and type of security incidents reported/detected/known. | |
| RCC008 | The contents of the CC program must include: measures and techniques for the protection of the privacy of credentials. | |
| RCC009 | The contents of the CC program must include: specific recommendations on the safe use of the user's own devices and the devices provided by the entity/operator. | |
| RCC010 | The contents of the CC program must include: specific recommendations on security practices on the CE support platform. | |
| RCC011 | The contents of the CC program must include: specific user actions for the configuration of their own devices for communication with the CE (phones, personal computers, electronic tablets, among others). It includes but is not limited to device-differentiated features for data storage, automatic rest/lock, deletion of information before disposal or replacement of the device, updating of operating systems and software pieces provided by the entity for CE use. | |
| RCC012 | The contents of the CC program must include specific techniques for the development/acquisition/manufacturing, implementation, homologation and testing of security features of the devices and software pieces provided by the entity/operator, ensuring that the internal/external personnel involved are duly trained to reduce implementation failures of the security features. | |
| RCC013 | The entities/operators must have a communication mechanism for the contents of their awareness and training program that ensures: a. That the recipients are continuously informed. b. That the recipients can make inquiries and clear up doubts. | |
| RCC014 | In the selection/change, by the client, of the values of the authentication elements based on the "something you know" factor, the entity/operator must recommend to the holder that the values not be composed of at least: a. A sequence of numbers associated with public personal data. b. A series of equal characters or numbers. c. Increment or decrement of consecutive numbers. d. Dates of historical significance. |
| Access Control requirements table | ||
|---|---|---|
| Requirement code | Requirement description | Scope |
| RCA001 | The distribution processes of identification and authentication elements based on the "something you know" factor must always be separated from the distribution of elements based on the "something you have" factor. | |
| RCA002 | The renewal of identification and authentication factors based on "something you know" must allow client self-management or minimal operator intervention during the process, ensuring that only the client will know the assigned values. | |
| RCA003 | The authentication elements based on the "something you know" factor must not be known before or during their generation and use by the officials, employees, representatives or third parties linked to the activities corresponding to the scenario. | |
| RCA004 | The storage of values corresponding to the clients' authentication factors will only be permitted when they are protected by techniques that prevent their knowledge by anyone other than the client and only for purposes of automatic verification of the credentials presented by the client to access and/or confirm operations in the CE. | |
| RCA005 | The enabling and re-enabling of identification and authentication elements based on the "something you have" factor must be carried out through a process that guarantees the positive identification of the holder (RCA040). Likewise, these elements may only be linked during their use to a single person individually and non-transferably. | |
| RCA006 | In the devices provided by the entity/operator that use physical keyboards (PIN PAD) or virtual keyboards (on-screen image) for entering the factor based on something you know, the entered value must be encrypted immediately after its entry using an algorithm no less than: a. 3DES for devices that allow transactions established with level 1 criticality in the scenarios of point 11.5. b. DES for devices that allow transactions established with criticality other than level 1 in the scenarios of point 11.5. | As of 01/03/2013, it is applicable to new acquisitions/developments, replacements or updates of devices/applications provided by the entity/operator. |
| RCA007 | The access and credential verification systems of the CEs contemplated in the described scenario must guarantee the non-reuse of the last generated value of the authentication elements based on the "something you know" factor. | |
| RCA008 | The expiration of the authentication elements based on "something you know" must be established according to the risk analysis of each entity or upon the expiration of the "something you have" factor associated with the channel, when applicable. However, financial entities must implement the necessary mechanisms so that clients can voluntarily make the change even before that period, as well as prevent their presentation after the period that determines their validity has expired. | |
| RCA009 | The authentication elements based on the "something you have" factor, provided they use dynamic authentication mechanisms (Token, coordinate card, among others), must have at least two of the following characteristics: a. Mechanisms that prevent their duplication or alteration (Anti tampering). b. Control of the unique relationship between client/account and device. c. Unique manufacturing identification. d. Biannual replacement. | |
| RCA010 | Entities/operators must apply protection techniques, according to their risk analysis, that minimize the exposure of identification and authentication factors based on "something you have", when they are presented to devices or means that reveal confidential data or security codes of credentials to third parties, in non-face-to-face operations (Internet, WebPos, Telephone Sales, unattended devices), considering but not limited to the following techniques: a. Use of complementary verification schemes through secure channels (second factor, shared secrets, techniques considered in requirement RCA040). b. Random identification values of TD/TC (PAN or variable CVC/CVV). | |
| RCA011 | The exposure of credential identification data must be limited to those users authorized by the entity/operator who, due to usage/knowledge needs, are qualified to access this information. | |
| RCA012 | At the login/credential presentation stage, entities/operators must execute specific actions to protect the strength of identification and authentication factors, optionally using: a. Two authentication factors of different types (strong authentication), in one of the combinations: "something you have" and "something you know", "something you know" and "something you are", or "something you have" and "something you are". b. Two authentication factors of the same type (simple authentication), where one of them uniquely identifies the user. |
Access Control Requirements Table
| Requirement Code | Requirement Description | Scope |
|---|---|---|
| RCA013 | In the event of failure or total or partial unavailability of the security mechanisms (Access Control, Monitoring, Integrity and Logging) on the device provided by the entity/operator, it must remain fully disabled, informing and warning the user to avoid presenting credentials and receiving or delivering values. | |
| RCA014 | Authentication elements based on the "something you know" factor, used in the CE, must have a length of no less than 8 characters for BI, 6 characters for BM and 4 characters for BT. | |
| RCA015 | Authentication elements based on the "something you know" factor that are strictly "numeric" must: a. Be limited to elements of the PIN type ("Personal Identification Number"). b. Have a minimum length of 4 digits. | |
| RCA016 | Throughout the entire cycle of tasks associated with the scenario, a customer's data and credentials must not be in the complete possession of the same person or group of persons or be associated with the customer's data except by the customers themselves. | |
| RCA017 | Authentication elements based on the "something you know" factor during their generation, use and transport processes must be protected by means of any of the following techniques: a. Encryption no less than 3DES. b. Irreversible digest or "hashing" functions. In BT, when none of the described techniques is used, it must be guaranteed that the authentication mechanism of the factor is different from the one used for other CEs of the same customer and financial entity. | As of 01/03/2013 it is applicable to new acquisitions/developments, replacements or updates of devices/applications provided by the entity/operator. |
| RCA018 | Authentication elements based on the "something you know" factor must limit their exposure during entry or reproduction, in the generation, renewal and use processes, considering, but not limited to, the alternative implementation of: a. Visual masks on the screen of devices provided by the entity/operator. b. Virtual keyboards in applications provided by the entity/operator. Protective display panels on devices provided by the entity/operator (example: PCI PIN - Security Requirement 2.0). | |
| RCA019 | The generation processes of identification and authentication elements based on the "something you have" factor must be carried out under a separation of duties scheme such that prevents them from being combined with the generation of identification and authentication elements based on the "something you know" factor. Examples: card embossing and PIN generation; the synchronization instance of a token is differentiated from its distribution. | |
| RCA020 | Identification and authentication elements based on TD/TC must have at least the following characteristics: a. Customer's first and last name. b. Internal enrollment number (card number). c. Holographic or handwritten signature. d. Effective date. e. Expiration date. f. Complaint reporting number. | As of 01/03/2013 and only for renewals and new TD/TC. |
| RCA021 | The distribution processes of identification and authentication elements, based on the "something you have" factor, must guarantee the positive identification of the holder before delivery. | |
| RCA022 | Identification and authentication elements based on the "something you have" factor, after their retention, must have a validity of no more than 30 business days for their disposal or unlinking from the customer and their accounts after the determined time in case they are not returned to the customer. | |
| RCA023 | Authentication elements based on the "something you know" and "something you are" factors must block access to the CE after no more than five consecutive failed login attempts, inform the user through the implemented early warning scheme (RCA041) and apply a positive authentication mechanism for unlocking within those considered in requirement RCA040. After a time no greater than 30 minutes from the last recorded failed attempt, except in cases of blocking, the recording of failed attempts may be restarted. | |
| RCA024 | In the event of failure or partial or total unavailability of the security mechanisms (Access Control, Monitoring, Integrity and Logging) in the service provided by and from the entity/operator, the service must remain fully disabled, informing and warning the user to avoid presenting credentials from their own device. | |
| RCA025 | In the devices provided by the entity/operator that accept the entry (traction mechanism) of TD/TC, and that due to mechanical failure or user oversight retain a TD/TC in the device, the entity/operator must proceed to return the TD/TC to the holder or, if this is not carried out, to its destruction within no more than 10 business days after its extraction in the device balancing or maintenance processes. |
BANCO CENTRAL
DE LA REPÚBLICA ARGENTINA
Access Control Requirements Table
| Requirement Code | Requirement Description | Scope |
|---|---|---|
| RCA026 | In all cases of authentication factors based on "something you know" that have been generated by the entity/operator, mechanisms must be implemented to ensure that the client modifies the values generated upon their first presentation at the CE. In all cases of authentication factors based on "something you know" that have been generated by the entity/operator, mechanisms must be implemented to ensure that the financial client modifies the values generated upon their first presentation at the CE. Such change may be made through a CE different from the one considered in the scenario, provided that strong authentication is used. | |
| RCA027 | In all cases of user identification factors generated by the entity/operator, the user must be offered the possibility of modifying said value to one chosen by the user. | |
| RCA028 | The authentication elements based on the "something you know" factor, used for logging into the CE, must have an alphanumeric composition and a complexity such that it includes at least the combination of three of the following attributes: a. Special characters. b. Uppercase letters. c. Lowercase letters. d. Numbers. e. Not contain more than two identical and consecutive alphanumeric characters. f. Be composed of non-trivial data (phone numbers, proper names, among others, are discarded). Only in the BM and BT channels may exclusively numeric characters be established, with a complexity such that it prevents the selection of: g. Series of characters of the same number. h. Increment or decrement of consecutive number. | |
| RCA029 | The authentication elements of the credentials based on the "something you know" factor and used in the CE login must prevent being associated with public personal data of the client or of the financial entity. | |
| RCA030 | Subscription to a CE must be carried out for its approval from a medium that uses positive identification in accordance with the techniques described in requirement RCA040. | |
| RCA031 | The generation and renewal of the personal key (PIN) associated with a TD/TC card based exclusively on magnetic stripe, according to RCA044 point a. must guarantee at least one of the following conditions: a. Two personal keys (PIN), one for the use of the ATM channel and another for the POS channels and PPM implementations based on readers for cell phones (dongle), with values different from each other. b. A single personal key (PIN) for all channels and the immediate return of the amounts involved in case of the client's disavowal of a transaction carried out under these conditions. c. A personal key (PIN) exclusive for the ATM channel and the immediate return of the amounts involved in case of the client's disavowal of a transaction carried out under these conditions in the POS and PPM channels. | |
| RCA032 | The entity/operator must execute the following actions for the protection of the transactions involved in the scenario: a. In the case of applying at the login/credential presentation stage any of the techniques described in requirement RCA012 point a. and before the confirmation of an individual banking transaction or interrelated group of commercial banking transactions, complementary authentication techniques must be applied to revalidate the identity of the authorized user, including but not limited to: shared secrets, simple authentication mechanisms, callback or use of an alternative channel. b. In the case of applying at the login/credential presentation stage the technique described in requirement RCA012 point b. and before the confirmation of an individual banking transaction or interrelated group of commercial banking transactions, one of the techniques described in requirement RCA012 point a. must be applied to revalidate the identity of the authorized user, including but not limited to: usb tokens, token with password generation or coordinate cards. c. After the confirmation of the transaction and only when predetermined patterns are exceeded in their transactional monitoring systems, at least one of the techniques described in requirement RCA040 must be applied. For the ATM channel, when operating through the use of a card with integrated circuit (CHIP) under the EMV standard and provided that compliance with requirement RCA012 point a. is satisfied, compliance with point a of requirement RCA032 will not be required. |
Access Control Requirements Table
| Requirement Code | Requirement Description | Scope |
|---|---|---|
| RCA033 | The information referring to mechanisms implemented by an entity/operator for the security of the CE and that is an essential piece in its protection must be kept protected against the exposure of its content to unauthorized persons. | |
| RCA034 | The processes of implementation, testing and homologation of devices provided by the entity/operator and/or specific applications for devices not provided by the entity/operator for the use of the CE, when required, may only use credentials under the administration of the entity/operator, not related to customers and not enabled for production environments. | |
| RCA035 | The software pieces provided by the entity/operator for the use of the CE through a customer's own device may not compromise the privacy of the customers or the customer data contained therein, even when the customer's authorization is given. | |
| RCA036 | The devices provided by the entity/operator must have physical characteristics that reduce copying, obstruction, viewing by third parties or illegal retention of credentials and monetary values, considering but not limited to the alternative application of: a. Detectors of objects attached to devices provided by the entity/operator. b. Mechanisms for explicit information to the user about the characteristics of the device provided by the entity/operator. c. Anti-skimming components at the entry of credentials. d. Mechanisms for detecting opening, violation or alteration of the physical conditions of the device (“tampering detection”). | |
| RCA037 | The groups, roles and responsibilities for the logical administration of the components of the service network of each CE must be described. | |
| RCA038 | The identification/authentication elements based on Debit/Credit Cards must have the following complementary protection characteristics: a. Printing of Card data in low or embossed relief or another technique that guarantees the legibility of the identifying data for at least the validity period inscribed on the Card. b. Inclusion of holograms, security codes, among others. c. The identification of the issuer and the intervening financial entity. d. The data storage means on the Card (magnetic stripe, chip, among others) must not store complete or readable data of the authentication factors. | As of 01/03/2013 and only for renewals and new TD/TC. |
| RCA039 | In a device/application associated with a CE in which a dynamic authentication mechanism is used (token, softtoken, coordinate card, among others) and that allows the execution of financial transactions considered in the scenarios with criticality level 1 of ETR prefix, the values generated to compose the “dynamic keys” must satisfy at least the following characteristics during the request, validation and entry of the requested values: a. The dynamic key must have a structure of no less than 4 random numeric digits. b. The values of the dynamic key generated in each request must have a maximum validity of 120 seconds or until its authentication, whichever occurs first. Validity by time will not be required when the entity/operator ensures that in the execution of financial transactions considered in the scenarios of ETR prefix with criticality level 1, the session of a CE uses a new and different value generated by the dynamic authentication device, both in the “login/presentation” stage and in the “confirmation” stage during the same session. c. The values of the dynamic key generated in each request must not be known before their generation and during the process of entry and validation of the data by individuals other than the customer. d. A validation of the generated value must be ensured that guarantees its authenticity by establishing an effective correspondence of the value generated in the device/application with the rest of the user's credentials that are part of the authentication process. For example, by means of a time synchronization with the CE's authentication systems, or by unique comparison of the generation seed. e. The dynamic keys are valid only once in a single individual banking transaction and a single group of interrelated transactions in commercial banking. The authentication processes of the dynamic key must occur online. | |
| RCA040 | Positive identification includes, but is not restricted to, the combined or non-combined use of the following techniques: a. Predefined questionnaires with random presentation, with automatic validation by the system. b. Presentation of identity documents issued by national authority that allow the effective comparison and validation of the bearer's characteristics. |
BANCO CENTRAL
DE LA REPÚBLICA ARGENTINA
Access Control requirements table
| Requirement code | Requirement description | Scope |
|---|---|---|
| c. Holographic signatures comparable with electronic record. d. Identification before an alternative electronic channel with two-factor authentication. | ||
| RCA041 | The entities/operators must make available to their customers the following information, establishing effective alert mechanisms within a time no greater than 24 hours after the transaction/session and according to the characteristics of each CE, without prejudice to including additional information in accordance with that generated by their transactional monitoring systems: a. Date and time of the last transaction/session confirmed in the CE. b. Notice of expiration of credentials with an advance notice no less than the operational time necessary for their change/replacement. c. Names of the session user and the holder of the accessed account. d. Contact data of the customer service for reporting irregularities/inquiries. | |
| RCA042 | Entities/operators must ensure that links/accesses from CE sessions to non-financial sites and/or third-party services that allow access to and execution of transactions considered in the scenarios of point 11.5 with prefix ETR, guarantee compliance with the same requirements established for the CE and do not share confidential credential data with the third party's sites and services. | |
| RCA043 | The identification and authentication elements based on the "something you have" factor after their generation and that remain without effective delivery to their recipient for more than 90 days must: a. Be discarded or reassigned to another client or, in the case of dynamic authentication elements (tokens, coordinate cards, among others). b. Be discarded in the case of TD/TC. | |
| RCA044 | The identification and authentication elements based on the "something you have" factor must have renewable security codes, different at each renewal of TD/TC and be applied to the transactions contemplated in the scenarios of point 11.5 under prefix ETR, as follows: a. In TD/TC based on magnetic stripe, they must have a non-visible credential verification code stored on the stripe (example: CVV1/CVC1) and a visible transaction verification code (example: CVV2/CVC2/CID) printed on the TD/TC. Optionally and only for transactions conducted in person (physical POS device), the implementation of the visible transaction security code on the TD/TC may be replaced with some authentication factor of the "something you know" type or PIN under the terms of requirement RCA031. b. In TD/TC based on the use of an integrated circuit (chip) or a combination of this with other techniques, they must have a dynamic authentication mechanism and encryption of the data stored in the integrated circuit. It may be complemented with some authentication factor of the "something you know" type or PIN under the terms of requirement RCA031. | |
| RCA045 | Entities/operators must consider, according to their risk analyses, a periodic replacement of the identification and authentication elements based on "something you have" with new elements renewed in their security codes applying, for example, the following criteria: a. In the following situations presented by the holder: 1. Report of theft, loss or deterioration. 2. Unrecognized transactions made. b. Upon the expiration registered in a TD/TC with a minimum advance notice of 20 days, immediately disabling the previous issuance or activation of the replacement, whichever occurs first. c. Upon detection of one of the situations considered in requirement RMC009. d. Upon changes in design, format or manufacturing techniques that modify the security elements of the TD/TC, a replacement plan must be carried out with execution no later than the remaining term for the original renewal. e. Upon detection of manufacturing defects or loss during distribution and/or storage, all TD/TC involved must be discarded, replaced and renewed. Likewise, entities must consider a gradual migration of TD/TC to integrated microcircuit technology, favoring market expansion, transactional security, interoperability and the evolution of financial services. | |
| RCA046 | TD/TC based on integrated circuit (CHIP) as indicated in requirement RCA044 and which also have a magnetic stripe (Dual System) may not carry out transactions using the magnetic stripe when the POS or ATM terminal has an enabled CHIP reader, except for exceptions that must have a differentiated record and form part of the analyses of point RMC009. |
BANCO CENTRAL
DE LA REPÚBLICA ARGENTINA
Access Control requirements table
| Código de requisito | Descripción de requisito | Alcance |
|---|---|---|
| RCA047 | When using TD/TC based on integrated circuit (CHIP) under the EMV standard, and according to the chosen authentication method, entities and operators must: a. For TD/TC that use the authentication method based on verification of a static data or signature recorded in the CHIP (SDA - Static Data Authentication), transactions in the scenarios of point 11.5 under prefix ETR must only be carried out in "online" mode (see glossary). Likewise, they must incorporate a second authentication factor in accordance with the provisions of requirement RCA032 when transactions involve withdrawals, transfers or payments for goods and services outside the limits of the "low value" concept (see glossary) b. For TD/TC that use authentication methods based on the dynamic generation of authentication keys (DDA/CDA – Dynamic Data Authentication/Combined Dynamic Data Authentication), transactions in the scenarios of point 11.5 under prefix ETR may be carried out in "online" or "offline" modes. On the other hand, they must incorporate a second authentication factor in accordance with the provisions of requirement RCA032 when transactions involve withdrawals, transfers or payments for goods and services outside the limits of the "low value" concept (see glossary) | |
| RCA048 | In the reader components provided or not by the entity/operator for reading the "something you have" factor (TD/TC), whether or not linked to mobile devices or personal computers, the following requirements must be met: a. The value captured by the reader must be encrypted from the reader using an algorithm no less than 3DES for components that allow transactions established with level 1 criticality in the scenarios of point 11.5. b. The reader must be uniquely associated with the following three elements: (1) processing network, mobile device or personal computer, (2) the service provided by the entity/operator and (3) the client/merchant. c. The reader must be approved by the entity/operator for the provision of the service. |
| Integrity and Logging Requirements Table | ||
|---|---|---|
| Requirement Code | Requirement Description | Scope |
| RIR001 | The authentication data of the credentials must not be stored on the device provided by the entity/operator nor kept in its activity log (Journal). | |
| RIR002 | The logging of activities in the application systems and/or devices provided by the entity/operator must guarantee for each event at least: a. Identification. b. Description. c. Full date and time. d. Source identification. e. Acting user. | |
| RIR003 | The logs collected by the application systems and/or devices provided by the entity/operator must ensure the traceability of the actions performed in all activities, identifying who (person/device/account/origin/destination), what (activity/function/transaction), where (CE, location), when (time) and how (pattern/relationship of events). | |
| RIR004 | The logs of the application systems and/or devices provided by the entity/operator must contemplate at least the following events: a. Requests and responses to transactional and maintenance actions of the applications. b. Errors and failures of the application or the device. c. Successful and failed authentication attempts. d. Credential management (creation, deletion, modification and assignment of privileges). e. Database/repository management (creation, deletion, modification and queries). f. Operational and maintenance actions (system start-up and shutdown, failures and configuration changes). | |
| RIR005 | The activity logs of each CE associated with the scenario must have, from the moment of their generation, mechanisms that allow verifying that each log is unique, follows a predetermined sequence and remains unalterable during its storage, transport and retrieval. | |
| RIR006 | The activity logs of the devices/applications provided by the entity/operator and of the transactional operations must be stored and safeguarded by means of one of the following storage regimes: a. In the case of digitized logs (Electronic Journal), they must be sent in real time or remain stored for less than 24 hours in the device provided by the entity/operator that generated them, where applicable, and must be transferred within that term to a storage and custody infrastructure. b. In the case of printed logs (Tira Journal), they must be sent immediately after each balancing and loading event of the device provided by the entity/operator. | |
| RIR007 | The historical logs of activities and transactional operations must be kept for a term no less than 6 years. The storage media of the historical archive must not be recoverable after their disposal. | |
| RIR008 | The storage media of the activity and transactional operation logs on the device provided by the entity/operator must not be recoverable after the following situations: a. 15 days after the confirmed transfer to the custody and recovery infrastructure. b. The disposal of the storage medium in the device. | |
| RIR009 | The activity logs of the devices/applications provided by the entity/operator and of the transactional operations must have protection mechanisms that ensure that they can only be accessed by those who are authorized according to the need for use/knowledge. | |
| RIR010 | The devices and/or software pieces provided by the entity/operator for the use of the CE must ensure that they satisfy a system life cycle and development based on the following conceptual stages: a. Requirements analysis. b. Acquisition/manufacture/development. c. Testing and approval. d. Implementation. e. Operation and maintenance. f. Disposal and replacement. Likewise, this cycle must provide the security elements related to, but not limited to: |
Integrity and Logging Requirements Table
| Requirement Code | Requirement Description | Scope |
|---|---|---|
| g. Functional security requirements. h. Types and characteristics of input data validation. i. Granularity of functions and logs. j. Access levels. k. Change Control. l. Update and Patches. | ||
| RIR011 | The approval processes of devices and/or software pieces provided by the entity/operator to interact with the CE must guarantee the verification of all aspects of design, functionality, interoperability and security characteristics defined in the acquisition/manufacture/development and implementation stages. | |
| RIR012 | The approval and implementation processes of CE software pieces on the client's devices must be carried out using a formal verification before their enablement. Likewise, installation methods must be used that prevent the exposure of personal, financial or client credential data. | |
| RIR013 | The following data integrity controls for transmitted data must be carried out: a. Identification of the receiver and destination account. b. Credentials and source account. c. Identification and composition of the message. | |
| RIR014 | In the transmission of credential and transaction data, every connection point between a private network and a public network must have a Firewall at each Internet connection and between any demilitarized zone and the internal network zone, including any wireless network. It applies only to the infrastructure of the entity/operator that manages the CE with TCP/IP-based networks. | |
| RIR015 | When the transport of credential and transaction data is carried out using public and/or partially private networks in any of their segments, the entity/operator must include link and session protection mechanisms in the CEs, including but not limited to: a. Use of secure protocols for data transmission (such as TLS/SSL/IPSEC/SSH) on public networks (such as 3G, 4G/LTE, GSM, GPRS, WIFI, Internet). b. Use of financial site protection methods (digital certificates based on public key infrastructure). c. strong encryption on networks that use TCP/IP-based protocols. This requirement is only applicable to TAS, POS and ATM channels and when they use public networks with TCP/IP-based protocols. | |
| RIR016 | In all cases, the devices/applications provided by the entity/operator must be able to generate a receipt of the transaction carried out that is unique and verifiable against the channel's activity records. It includes but is not limited to the alternative application of any of the following options: a. Printed paper for physical devices provided by the entity/operator. Issued at the customer's request if it does not require the customer's signature, mandatorily when it requires the customer's signature, b. Digital format for the customer's own devices, retrievable for at least 3 months after the transaction. Additionally, the identification data of the customer's credentials must be limited to the strict and minimally necessary and must not appear completely on the receipt. | |
| RIR017 | In the processes of device compatibility and/or implementation of software pieces in user-controlled environments, the entity/operator must define and inform the customer of the security requirements applicable to the user's own devices, carrying out the following tasks: a. Inform the admissibility criteria of the user's devices, as well as the hardware, software, connectivity and environment limitations for their use in the CE. b. The CE must prevent access through a device that does not satisfy the determined admissibility criteria. c. Detect and inform the user of the actions necessary to keep the service enabled from the device. | |
| RIR018 | Credentials based on TD/TC that are retained during the use of devices provided by the entity/operator must ensure compliance with the following operational actions: a. After their retention, the entity/merchant must inform the issuer before 24 hours have elapsed and in the shortest possible time according to the available means. b. The issuing entity/operator must resolve the incident within a period no greater than 48 hours. In cases where the retained material is not legitimate, it must be kept in custody with the necessary precautions to prevent its use, as evidence for subsequent investigation. |
Integrity and Logging Requirements Table
| Requirement Code | Requirement Description | Scope |
|---|---|---|
| RIR019 | The applications (software pieces) used to provide financial services on mobile devices must guarantee the unique binding between the "application", the customer's credentials and the mobile device, considering but not limited to the following combined techniques: a. Association of IMEI identifier (International Mobile Station Equipment Identity) or unique device identification code. b. Seed for encryption of data and/or credentials c. Random value that identifies the relationship of the device with the financial service. Applications for mobile devices must be hosted on sites whose security conditions are in accordance with the financial entity's policy and these must be reliably informed to the consumer of financial services. |
| Monitoring and Control Requirements Table | ||
|---|---|---|
| Requirement Code | Requirement Description | Scope |
| RMC001 | The entity/operator must establish a maximum session inactivity time on each device/application provided to the customer for the use of the CE. This time must guarantee that the session does not remain open indefinitely and include but not be limited to the following actions: a. Session expiration by established time for each channel according to documented vulnerability analysis. b. Session expiration in a time no greater in any case than 30 minutes. | |
| RMC002 | Devices provided by the entity/operator that present communication problems or total or partial failures of the security mechanisms (Access Control, Integrity and Logging) must ensure timely monitoring based on alerts and recording of the actions undertaken for their disabling/repair as appropriate. | |
| RMC003 | Monitoring must be carried out on the CE for security configuration changes and to verify the update levels of: operating systems, databases, communication links, tools that prevent and detect the presence of malicious code, network security equipment, traffic controllers and any other security tool. They must include, but not be limited to: a. Monitoring of privileges and access rights. b. Processes for copying, backup and recovery of information. c. Availability of the CE devices. d. Alarms, alerts and problems detected by event logging systems. This requirement does not include the client's own devices, nor the authentication elements based on the "something you have" factor provided by the entity/operator. | |
| RMC004 | Entities must have transactional monitoring mechanisms in their CE, operating based on the client's profile and transactional pattern characteristics, so that it warns and acts in a timely manner in at least one of the following action models: a. Preventive. Detecting and triggering communication actions with the client through other channels before confirming transactions. b. Reactive. Detecting and triggering communication actions with the client after the confirmation of suspicious transactions. c. Assumed. Detecting and assuming the return of the amounts involved in the event of the client's claims regarding the lack of knowledge of transactions carried out. | |
| RMC005 | Entities must implement alternative communication mechanisms with their clients in order to ensure varied verification channels in the presence of alarms or alerts arising from the effect of the implemented transactional monitoring. | |
| RMC006 | Based on the records collected by the entity's/operator's application systems associated with the scenario, a classification and determination of security events must be carried out, a definition of compromise limits and thresholds, normal/unexpected behavior levels, and the actions must be established according to each classification and determined limit. | |
| RMC007 | Devices provided by the entity/operator that interact with TD/TC must have alert mechanisms in case of forgetting and retention of the TD/TC, with the exception of the POS channel. | |
| RMC008 | The financial entity must provide communication channels for receiving client inquiries/complaints 24 hours a day. | |
| RMC009 | The transactional monitoring systems of TD/TC entities/operators must ensure the detection, recording, and control of situations that establish a compromise of sensitive data, including but not limited to the following: a. Common point of compromise. Point of sale, acquirer, provider, among others that compromise TD/TC transactions processed through it. b. Information leakage. Loss occurring in the technical and/or organizational infrastructure of the financial entity, operator, acquirer, distributor, and/or providers that compromises sensitive information of TD/TC (card numbers, security codes, confidential client data, among others). c. Security Codes. Demonstrated compromise of the calculation algorithms of TD/TC security codes. | |
| RMC010 | Devices/applications provided by the entity/operator must detect the simultaneous opening of more than one session for the same user, channel, and financial entity, executing one of the following actions: a. Prevent the simultaneous opening of more than one session. b. Block operations immediately after detection, informing the client of the irregularity. The ATM CE may be exempted from the actions indicated in points a and b provided that the necessary configurations to detect and record the events indicated in the requirement are included in the monitoring and control systems. |
CENTRAL BANK
OF THE ARGENTINE REPUBLIC
Table of Monitoring and Control Requirements
Code of requirement Description of requirement Scope RMC011 Transactional monitoring in CE must be based on, but not limited to, the following:
a. The classification of originators and recipients based on characteristics of their account and habitual transactions, including but not limited to the frequency of transactions by type, transaction amounts, and habitual account balances. b. Determination of thresholds, patterns, and dynamic alerts based on the transactional behavior of originators and recipients according to their classification. RMC012 For the authorization of a pre-approved credit, the entity must verifiably verify the iden- tity of the person using the financial services involved. This verification must be carried out using positive identification techniques, in accordance with the definition provided in the glos- sary and in the specific technical operating requirement (RCA040) of these regulations. Likewise, it must be previously verified through the result of the monitoring and control process, at a minimum, that the contact points indicated by the user of financial services have not been modi- fied recently. Once the identity of the person using the services has been verified, the entity must inform them – through one of the available contact points – that the credit is ap- proved and that, in the absence of objections, the amount will be credited to their account from the 2 (two) business days following. The aforementioned crediting period may be reduced in the event that the user of financial services gives their consent verifiably. The financial entity shall be exempt from implementing the foregoing, to the extent that it complies with one of the following conditions:
a. That for the authorization of a pre-approved credit, the financial entity veri- fies verifiably the identity of the person using the financial services invol- ved, through biometric solutions with proof of life. b. That the financial entity cancels the pre-approved credit, assumes the return of the amounts involved and voids any possible effects on the credit situation of the affected person using financial services, upon the police report pre- sented by this person using services in accordance with the "assumed" action model defined in requirement RMC004, provided that the report is filed within a maximum period of 90 (ninety) calendar days from the due date of the first in- stallment of the credit. In both cases, the requested credit may be immediately credited to the account of the user. The activity carried out to comply with this requirement must be traceable and auditable. RMC013 During the processes of maintenance, configuration, opening, loading, and balancing of the devi- channels contemplated in the scenario, with the exception of the POS channel, the following guidelines must be met:
the following guidelines must be met:
a. Physical and logical segregation of the following functions must be ensured:
Administration (installation, configuration and adjustment of parameters in the operating system and application). It must be limited to personnel of the operator/entity responsible for the service.
Operation (execution of operational tasks of inquiry, balancing and reporting). It must be limited to personnel of the entity or a third party contracted by the entity for the indicated processes.
Opening and closing of device and treasury. Dual control must be applied for the use and temporary possession of physical and/or logical keys. b. The implementation of the entity's internal procedures for the control of the supporting documentation of the related operational tasks must be ensured.
CENTRAL BANK OF THE ARGENTINE REPUBLIC
| Incident Management Requirements Table | ||
|---|---|---|
| Requirement code | Requirement description | Scope |
| RGI001 | Must perform, with a minimum annual periodicity and based on the risk analysis of the IT assets associated with the scenario, an analysis of the incidents that have occurred and a report that serves to establish protection measures, contents of the training and awareness program, modifications to event recording and control, and a redefinition of alerts, limits and thresholds. | |
| RGI002 | Incident identification must be based at least on early warnings, incident type/frequency/pattern statistics and IT security recommendations. | |
| RGI003 | Security incident management may be executed in a decentralized manner but must be coordinated with personnel of the financial entity. | |
| RGI004 | Not defined. | |
| RGI005 | Detected incidents must receive regular treatment with a formally defined escalation. |
Section 12. Glossary of terms
Asset: A resource of tangible or intangible value that should be protected, which includes people, information, infrastructure, finances and reputation.
Information asset: Data, information, software (programs, applications, information systems, databases), hardware.
Threat: A circumstance that could exploit one or more vulnerabilities and affect cybersecurity.
Anomaly: An unexpected event, behavior or operation.
Risk appetite: An estimate indicating how much risk the organization is willing to accept within its usual operations.
Machine learning: A branch of artificial intelligence that consists of getting a computer to draw conclusions from the statistical analysis of the data entered, through a process that improves automatically as more evidence is incorporated into the algorithm.
Enterprise architecture: Model that describes the complete set of information systems of an entity: how they are configured, how they are integrated, how they interact with the external environment, how they are operated to support the mission and how they contribute to strategic objectives.
Authentication: Process designed to establish the source of information, the validity of a transmission, message or sender, or a way to verify an individual's authorization to receive or access specific categories of information.
Out-of-band authentication: Use of physical devices in the user's possession, which have a unique identification and communicate with the entity through a channel other than the application in which the user operates. Its objective is to prove the possession and control of the device by the requester.
Multi-factor authentication (MFA): Authentication process that requires more than one factor for the requester to obtain access to resources or information. To achieve authentication, all factors presented must be correct. Multi-factor authentication can be implemented in three (3) ways:
Adaptive or risk-based authentication. A risk value is assigned to the user's authentication based on their context and it is defined from what risk level additional authentication factors are requested.
Authentication based on authorized device. When the requester logs in from a device that has not been previously authorized, multiple factors will be requested.
Permanent MFA authentication per requester. The resource to which access is desired requires the use of MFA every time a requester requires access.
The MFA two-factor method (2FA) consists of using a combination of two (2) factors from different categories.
Cyber incident or Technology and security incident. Cyber event that:
endangers the cybersecurity of an information system or the information that the system processes, stores or transmits; or
breaches security policies, security procedures or acceptable use policies, whether or not it is the product of malicious activity.
Cyber resilience / technological resilience: Capacity of an organization to continue carrying out its mission by anticipating and adapting to threats and other relevant changes in the environment, and by resisting, containing and rapidly recovering from cyber incidents.
Cybersecurity: Preservation of the confidentiality, integrity and availability of information and/or information systems through a cyber medium. In addition, other properties, such as authenticity, accountability, non-repudiation and reliability may also be involved.
One-time codes (OTP): One-time key, password or codes generated by software or by means of a device.
Malicious code (malware): Software with a malicious objective and that contains characteristics or capabilities that could cause direct or indirect harm to entities or their information systems.
Governance components: The processes, the organizational structure; the people, skills and competencies; the policies, standards and procedures, and the culture and leadership that form part of a governance framework.
Reliability: Consistency in terms of behavior and desired results.
Confidentiality: Property of information of not being made available or disclosed to unauthorized individuals, entities or processes.
Business continuity: Capacity of an organization to continue providing products and services within acceptable timeframes, and with a predefined capacity, during a disruption.
Data: Piece of information.
Customer data: customer information that allows revealing or inferring their identity, personal credentials, business relationship and/or financial position, limited, restricted and/or protected by the Personal Data Law (Law 25.326), the Financial Entities Law (Law 21.526) and specific BCRA regulations.
Accounting data: Information referring to balances, balance sheets and assets of the financial entity or of its non-individualized customers.
Transactional data: Individual or related instructions that order financial movements in accounts of one or several customers, subject to verification and approval before their completion or confirmation.
Availability: Property of information of being accessible and usable when required by an authorized entity.
Cryptographic devices: They are devices that contain one or several secret keys (symmetri- cal or asymmetric) that they use to perform a cryptographic operation for authentication (nor- mally a signature). Cryptographic devices can also be one-factor or multi-factor:
One-factor cryptographic devices. Performs the cryptographic operation when the verifier requests it.
Multi-factor cryptographic devices. Requires activation by means of a second authentication factor of the "something you know" or biometric type, to perform the cryptographic operation.
One-time code generation devices: Device that generates one-time codes. A device is considered multi-factor when it requires some prior authentication factor to access the one-time code.
Disruption: Event that causes an unplanned negative deviation in the delivery of products or services in accordance with the organization's objectives.
Event: Occurrence or change of a particular set of circumstances.
Information security event: Any observable occurrence that is relevant to information security. This may include attack attempts or failures that discover existing security vulnerabilities. Security events sometimes indicate that a cyber incident is occurring.
Explainability: Capacity to provide meaningful, context-appropriate and coherent information that allows understanding the results of the application of machine learning and artificial intelligence techniques.
Authentication Factors (AF): It is evidence that serves to prove to the requester their identity and, therefore, to pass authentication. Authentication factors are divided into three (3) categories:
Something you know. The evidence is something that only the requester can know. For example, a password or PIN.
Something you have. The evidence is something that only the requester can possess.
Something you are. The evidence is something that only the requester can be. In general, it is some biometric characteristic.
Data management: Development of activities to establish policies, procedures and best practices that allow ensuring that data are understandable, reliable, visible, accessible and interoperable.
Portfolio management: Coordinated management of the set of projects to achieve specific business objectives.
Identification: Process by which someone or something that is not known in advance becomes known.
Technological infrastructure / IT infrastructure: Subset of the infrastructure that comprises hardware, networks, software and firmware.
Integrity: Quality of being exact and complete.
Artificial intelligence (AI): Set of theories and algorithms that allow carrying out tasks that typically require capabilities proper to human intelligence.
Threat intelligence: Information about threats that has been aggre- gated, transformed, analyzed, interpreted or enriched to offer the necessary context for decision-making processes.
Management framework: Refers to a coordinated set of planning, implementation, operation, monitoring and continuous improvement processes.
Three lines model: Scheme that defines 3 levels for the assignment of roles and responsibili- ties for effective risk management and control by opposition.
Business continuity plan: Documented compilation of procedures and information for use in an incident with the objective of enabling an organization to continue delivering its critical products and services at an acceptable level.
Policy: A document that records high-level principles or an agreed course of action; direc- tion and general intent formally expressed.
Practice: Activity carried out recurrently.
Procedure: Method composed of a sequence of steps that must be followed to comple- te the task or a process.
Information owner: Within the organization, formally responsible for defining and ensuring the integrity, confidentiality and availability of certain information.
RPO (Recovery Point Objective): Maximum tolerable loss of information in the event of interrup- tion.
RTO (Recovery Time Objective): Time during which an organization can tolerate the lack of operation of its applications and the associated drop in service level, without affecting busi- ness continuity.
Memorized secret (key or password): Data used for authentication. It may be created used by a user, or created by the entity and delivered for use.
Information security: The preservation of the integrity, availability and confidentiality of information. In addition, it could include authenticity, traceability, accountability, non- repudiation and reliability.
Shadow IT: Refers to software, hardware, services and devices not authorized by the organiza- tion that operate in the IT environment.
Subcontracting: Practice under which a third party entrusts to a subcontractor part of what has been entrusted to it.
Third party: One who provides processes, services and/or activities that have been formally delega- ted by the entity in accordance with the provisions of Section 2 of the Ordered Text "Expansion of financial entities". Included within this definition is an entity belonging to a corpo- rate group (global or domestic) or an entity external to the corporate group, with which a contract has been established for the performance of processes, services and/or activities.
CENTRAL BANK OF THE ARGENTINE REPUBLIC
Risk tolerance: Acceptable level of variation with respect to the risk appetite defined in achieving the entity's objectives.
Vulnerability: Weakness of an asset or control that can be exploited by one or more threats.
Note from RegAlert. AI assistants can read this document in full, and search 70,000+ more, through the RegAlert MCP connector (https://mcp.regalert.today/mcp). Free with an account. How to connect ChatGPT, Claude or Cursor.
More like this from BCRA
BCRA published 18 documents in the last 30 days. We email you each new one the day it's published.
Source: Banco Central de la Republica Argentina — original document · Summary generated with machine assistance and checked by an AI reviewer before publication; the authoritative text is the regulator's original document. How RegAlert works
In RegAlert: added · updated