Rule · BCRA · 23 Jan 1998 · A 2659
Financial institutions must ensure their Information Systems area depends on a level guaranteeing independence from user areas, separates development, maintenance, operations, support and database administration, and maintains a 1-year Systems Plan and 3-year strategic plan. Entities with over 10 branches must form a Systems Committee. External auditor special reports are due 31.3.98 and 30.6.98. Passwords need 4 characters, 5-password non-repetition, 3 failed attempts, 30-minute inactivity and 30-day expiry; audit reports kept 3 years. Backups: 2 copies, accounting data duplicated 10 years; contingency plan tested annually. New products must be recorded in application systems within 90 calendar days.
CENTRAL BANK OF THE ARGENTINE REPUBLIC
COMMUNICATION "A" 2659
23/01/98
TO THE FINANCIAL INSTITUTIONS:
Ref.: Circular RUNOR 1 - 260. CONAU 1 - 243. Minimum operating requirements of the information systems area of financial institutions
We address you for the purpose of informing you that this Institution adopted the following resolution:
1. Approve, with effect from 1.7.98, the "Minimum operating requirements of the information systems (IS) area" set forth in the annex to this communication.
2. Establish that, in relation to the provisions of the preceding point, the external auditors must issue a special report as of 31.3.98 and 30.6.98 on the degree of progress in compliance with the provisions referred to in said point.
We greet you very attentively.
CENTRAL BANK OF THE ARGENTINE REPUBLIC
Alfredo A. Besio
Manager of Standards for
Financial Institutions
Ruben A. Escobar
Manager of External
Systems Audit
| B.C.R.A. | MINIMUM OPERATING REQUIREMENTS OF THE INFORMATION SYSTEMS (IS) AREA (INFORMATION TECHNOLOGY) | Annex to Com. "A" 2659 |
|---|
The procedures that must be carried out for the development of the task and control of the information systems areas, which involve the Board of Directors, Board of Administration or equivalent authority, General Management, Information Systems (IS) Management and personnel of the entity, must be designed to provide a reasonable degree of security in relation to the achievement of the objectives and the resources applied in the following aspects:
Effectiveness: The information and related processes must be relevant and pertinent for the development of the activity. They must be presented in a correct, coherent, complete manner and in a way that can be used in a timely manner.
Efficiency: The information process must be carried out through an optimal use of resources.
Confidentiality: Critical or sensitive information must be protected in order to prevent its unauthorized use.
Integrity: It refers to the accuracy that the information must have, as well as its validity in accordance with the guidelines set by the entity and external regulations.
Availability: The resources and information must be available in time and form, when required.
Compliance: It refers to compliance with internal rules and all laws and regulations to which financial institutions are subject.
Reliability: The systems must provide correct information to be used in the entity's operations, in the presentation of financial reports to internal users and in their delivery to the Central Bank of the Argentine Republic and other regulatory bodies.
All these aspects must be applied to each of the resources involved in information technology processes, such as: data, application systems, technology, facilities and people.
The points detailed below list a series of minimum requirements that financial institutions and fund clearing houses must comply with, which will be subject to supervision by the Superintendency of Financial and Exchange Institutions.
(The denomination "entity" includes both financial institutions and fund clearing houses).
1.1. Within the organizational structure, the Information Systems area must functionally depend on a level that allows guaranteeing its independence from the user areas.
1.2. The area must present a clear delimitation of tasks between systems development and maintenance, operations, technical support and supervision, in a manner that guarantees an adequate segregation of functions and does not prevent control by opposition of interests. Likewise, it must maintain a separation of functions between systems development and maintenance and database administration.
In entities with up to 10 branches, the technical support function may functionally depend on the operations sector.
1.3. There must be a formal Systems Plan that allows continuous and direct supervision of the tasks carried out by the different sectors and that contains a schedule of the area's activities, assignment of priorities, resources, sectors involved and all the tasks to be carried out during a period of 1 year.
Likewise, there must be a strategic systems plan, which contains the main projects and the schedules for their implementation, for a period of at least 3 years.
1.4. The managerial control of the area must be formal, keeping in file - for 2 years - the written documents in which the sectors inform their supervisors of the different activities carried out, in order to allow adequate control of compliance with the policies, objectives and plans defined by management.
1.5. In entities with more than 10 branches, there must be a Systems Committee for the institutional treatment of policies, objectives and planning of the Information Systems area in which the highest directive and/or managerial levels of the areas designated by the entity must participate, formalizing the content of the meetings through minutes, which must be kept filed for a period of at least 2 years.
2.1. There must be general policies, a clear definition of the missions and functions of all jobs (responsibility, dependency, functions supervised, etc.), standards and written procedures that are the basis for planning, control and managerial evaluation of the area.
2.2. There must be manuals with methodology standards for the design, development and maintenance of application systems. Its application shall govern all new systems and modifications whose development occurs after the date of this communication.
2.3. There must be documentation of: application systems; the operation of computer processes; data and file recovery processes; data backup and safekeeping processes; physical and logical security; telecommunications network administration; procedures for putting programs into production; handling of user requirements; user manuals; fund transfer procedures, etc.
2.4. There must be detailed documentation on computer equipment, including diagrams and physical layout of facilities, inventory of "hardware" and base "software", network topology diagrams, types of links and location of nodes.
This information includes both the main data processing center and secondary ones, departmental networks, branches, fund transfers and the alternative contingency center.
3.1. There must be adequate planning and written and updated documentation of the activities normally carried out in the information processing center, which must include at least the detail of the processes to be performed, the controls carried out, the mechanisms for recording events and problems, the procedures for cancellations and reprocessing in each of the activities, relations with other areas and the mechanisms for distributing information.
3.2. There must be control procedures to ensure the correct implementation of changes when applicable, such as: changes of programs in production libraries, files, data dictionary definitions, program run orders, etc.
3.3. In cases where there are different processing centers, there must be a person responsible for the centralized control of the operations and processes carried out in them.
4.1. There must be formally established contracts with external providers of "software", processing and/or services, which contemplate aspects such as the procedure by which the entity, in the event of any situation that the provider might suffer causing it to cease operating or providing its services in the market, can obtain the data, source programs, manuals and technical documentation, in order to ensure continuity in processing.
In addition, the contracts must clearly establish that the Superintendency of Financial and Exchange Entities shall have unrestricted access to the data and all related technical documentation (file design, type of organization, etc.).
4.2. The entity must have technically trained human resources to exercise efficient control over the tasks carried out by the external provider, whether through agents under an employment relationship or who are not linked to the external providers.
Computerized information systems must have built into their programming validations and minimum controls to ensure the integrity and validity of the information they process (referring to: dates, account numbers, customer numbers, interest rates, terms, amounts, etc.)
6.1. Within the entity's structure there must be a function for the administration and control of data access security that guarantees its independence from the Information Systems area.
In entities with up to 10 branches, this function may be performed by the highest-ranking officer of the systems area.
6.2. There must be a formal information security policy, detailing at least the following aspects: level of confidentiality of data, procedure for granting user passwords for system access, standards set for user access and authentication, courses of action to follow in the event of initiating disciplinary proceedings against employees or their separation or that of third parties from the entity.
6.3. Regarding user access and authentication, the following values must be set, at minimum: 4 characters in length for "passwords", non-repetition of the last 5 passwords, etc. Likewise, the following requirements must be established as maximum limits: deactivate the terminal after 3 failed access attempts, disconnect the terminal after 30 minutes of inactivity, automatic password expiration interval of 30 days, etc.
6.4. The security system must keep password or "password" files encrypted, generate audit reports on attempted violations, the use of sensitive utilities and the activities of users with administration attributes and special accesses, which must be kept on file for 3 years, using non-reusable storage media (paper, CD, optical disk or other technologies of that characteristic).
The logical security administrator is the primary person responsible for the daily and formal control and monitoring of these files and reports.
6.5. Access to sensitive utilities that allow modifying data in the production environment must be restricted, documenting when this occurs.
6.6. The security scheme must include an appropriate separation of the development and maintenance environments of systems and operations (production), not allowing the entry of analysts and programmers into the production environment, nor of operators into the development environment or tools.
6.7. The implementation in production of the programs must be carried out by personnel who have no relationship with the systems development and maintenance area, through a procedure that guarantees the correspondence between the "source" and "executable" programs.
7.1. There must be data backup procedures ("backups"), containing a detailed plan with the quantity, frequency, appropriate storage locations both internal and external, detailed inventories, responsible person and form of administration of the magnetic media. These procedures must provide, at a minimum, for the generation of 2 backup copies, keeping the storage of one of them in a building located at a reasonable distance from the processing center.
7.2. The retention periods for data and program backups (daily, weekly, monthly, "software" that administers them, etc.) must ensure their recovery in the event of any processing inconvenience that arises.
Likewise, the backups of accounting information (personal identification data, balances at the beginning of the month, movements, etc.) must be kept available, in duplicate and in conditions to be processed, for 10 years.
7.3. Formal and duly documented tests of recovery and integrity of data backups ("backups") must be carried out.
7.4. There must be a contingency/emergency plan, tested comprehensively at least annually, that clearly and precisely establishes the courses of action to be followed, the times, responsibilities, files, telecommunications and all those resources necessary to achieve continuity of processing, in the event of a situation that affects the normal development of production tasks.
7.5. Alternative equipment (own or through formal agreements with third parties) must be available for processing and telecommunications, in order to overcome possible failures or interruptions of activities in their usual equipment. It must be located in a building located at a reasonable distance from the processing center.
7.6. The facilities must have appropriate physical and environmental security, with adequate access controls. Access to the processing area must be allowed only to authorized personnel and there must be no unnecessary combustible material in it. Automatic smoke/heat detection controls and fire extinguishing elements must be installed.
The listings and documentation of data, programs and systems must be safeguarded with adequate security measures, as well as there must be a procedure to determine their destruction or disposal, once their retention period has been fulfilled.
8.1. Protection mechanisms must be established for data transmitted over the telecommunications network, through adequate encryption techniques by "hardware" and/or "software".
8.2. Within the telecommunications networks, there must be a duly administered "software", in order to provide adequate security for access to the networks, changes to their operating system and monitoring of the activity carried out in them.
9.1. Active and passive operations must be recorded, administered and processed in the corresponding application systems, and no operation may be recorded/administered manually, in spreadsheets or with other utility "software".
In the case of new services or products, the entity will have a maximum period of 90 calendar days, from the first operation, to record/administer these operations in the corresponding application systems. In these cases, they must have the formal authorization of the entity's systems committee and its communication to the internal audit area.
9.2. For each application system, the technical documentation must be kept updated containing, at a minimum: objectives, scopes, system diagram, record of modifications, programming language, ownership of the source programs, known problems or limitations, description of the "hardware" and "software" used, their interrelation with the telecommunications networks, description of the screens that allow direct modification of production data (change of parameters, formulas, rates, data, etc.).
9.3. In the files of the applications corresponding to passive operations, the personal identification data (surname and name, CUIT/CUIL/CDI, in the latter case, when applicable, document number, etc.) of all the holders of each of the accounts must appear individually.
9.4. All application systems must issue daily a listing ordered by branch and account, with the "value-date" movements processed, which must be kept on file for 3 years, for the purposes of their subsequent review by those responsible for control. When there are no movements of this type, a legend indicating this situation must appear in the listing.
9.5. They must have a management information system to be used by the highest authorities in decision-making, which obtains and integrates in a fully automated manner the data residing in the files or databases of their applications.
9.6. The accounting system must have the necessary controls to prevent the entry of unbalanced daily entries, to deregister accounts that have or have had balances during the fiscal year, to register accounts with a balance without the corresponding counterpart, to modify balances of accounts without movements and other registrations of this nature.
9.7. The maximum period for entering "value-date" entries in the accounting system is 5 days for personnel who must enter accounting movements normally. Once said period has elapsed and within the following month (approximately 40 calendar days for entities that do not have foreign branches and 60 calendar days for those that do), transactions may only be entered with authorization from the entity's highest accounting authority, expressed with their signature and seal on the corresponding vouchers and the use of their personal access key ("password"), or failing that, with authorization from an officer designated by the general manager, in accordance with the rules approved by the board of directors or equivalent authority of the entity. In these cases, the internal and external auditors must be notified.
9.8. The maximum period for entering "value-date" movements in the application systems is 5 days.
9.9. Entities must have automated systems for generating information for the Banco Central de la República Argentina, avoiding the re-entry or non-automated exchange of data between different environments.
In cases where manual entry of information is required, because it does not reside in their files, this must be done through specific programs, in an appropriate security environment, in independent files, with no possibility of modifying information already generated in an automated manner.
The Superintendencia de Entidades Financieras y Cambiarias shall especially verify that the information corresponding to the classification of the consumer portfolio must be generated in an automated manner and there must be no possibility of modifying it to improve it, without prejudice to the future application of that restriction to other information.
9.10. There must be a file with a "unique customer key" in such a way as to correctly establish all of each customer's passive and active transactions at the entity.
9.11. A centralized control procedure must be established to periodically verify the effectiveness, by the branches, of the closing of accounts of the signatories of checking accounts disqualified by the Banco Central de la República Argentina.
9.12. The information to the Banco Central de la República Argentina on rejected checks and their signatories must be generated automatically by the same application system that administers the checking accounts or by a subsystem that automatically takes the data generated by this system. In cases where the check has not been signed by all of its holders, those who did not sign must be eliminated in a subsequent process.
10.1. The systems used for funds transfers must comply with the minimum internal control requirements established in the preceding points, with regard to the physical and logical security and operation of the equipment.
10.2. There must be no users with simultaneous attributes of entry, verification and/or sending of messages, in order to ensure adequate control through the separation of interests. Individual persons responsible for each of the aforementioned attributes must be designated.
10.3. The listings reflecting daily activity must be controlled and kept on file for 10 years, for their subsequent review by those responsible for control and by virtue of legal accounting rules.
11.1. The automated teller machines ("ATM's") that make up a network administered by an entity and/or by third parties must operate in a real-time processing and direct connection ("on-line") scheme with the computer that administers the network and the database it operates.
11.2. In the event of interruption of the link between an automated teller machine and the computer that administers it, the ATM must be taken out of service for all types of monetary transactions until the process is normalized.
11.3. The opening of automated teller machines must be performed by two persons, leaving a written record in minutes of their participation and the result of the reconciliation, balancing of banknotes, conformity of deposits, retained cards, totals, differences if any, etc.
11.4. In transactions carried out through automated teller machines that involve movements of funds, the corresponding voucher must be issued or, at a minimum, the user must be given the option to print it or not.
11.5. Automated teller machines must, in all cases, print, in real time, a listing or audit tape, in which all of their activity is reflected (inquiries, transactions, "software" and sensor messages, etc.) with details of date, time and identification of the automated teller machine.
11.6. A file must be generated on magnetic media, with all the transactions and messages of the system, for use by those responsible for control and audit. This file must meet all security and integrity conditions in order to guarantee its reliability and remain available for 5 years.
11.7. Measures must be established to appropriately set the "customer identification key" ("PIN") and maintain its confidentiality, and it must be encrypted in all places where it is stored or transmitted and its access restricted with appropriate and justified levels of security.
Likewise, the programs, files and magnetic media containing formulas, algorithms and data used to calculate the "PIN" must be subject to the same security conditions.
11.8. The card embossing and "PIN" generation procedure must provide for an adequate separation of functions so as not to concentrate both activities in the same sector or officer.
11.9. The processes for generating and printing the "PIN" must ensure that they do not appear printed in visible form and/or associated with the customer number, nor can they be viewed on screen, in order to guarantee their confidentiality.
11.10. The "PIN" and the cards must not be delivered together, but must form part of separate procedures.
11.11. Systems that require a "PIN" to be used must restrict customer access after, at most, three failed attempts.
11.12. The entity must provide the customer with a transaction number for each transaction processed.
11.13. Telephone banking systems that carry out fund transfer operations cannot operate on the basis that the customer has to communicate their "PIN" to a human interlocutor.
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