Rule · SMV · 26 Mar 2019
Entities must implement an information security management system, with a Board-approved policy, controls covering access, human resources, physical security, asset management, operations, systems acquisition, backups and incident management, and report on it to the Board or Risk Committee at least every 6 months. Significant changes require a prior risk report to the Board, Risk Committee or specialized body, and significant cloud subcontracting requires enhanced due diligence on access and audit rights and data location. Entities must report cyberattacks to Pe-CERT, directly or through sectoral CSIRTs, and file the RO_r1 Operational Risk Loss Event Report.
PERÚ Ministry of Economy and Finance
SMV
Superintendency of the Market in Securities
DECADE OF EQUAL OPPORTUNITIES FOR WOMEN AND MEN – YEAR OF THE FIGHT AGAINST CORRUPTION AND IMPUNITY
Lima, 26 March 2019
File No. 2018039905 and Joint Reports No. 1356-2018-SMV/06/12/13 and No. 281-2019-SMV/06/12/13 of 23 November 2018 and 20 March 2019, respectively, both issued by the Legal Advisory Office, the Deputy Superintendency of Risks and the Deputy Superintendency of Research and Development; as well as the Draft Amendment to the Operational Risk Management Regulation (hereinafter, the DRAFT);
That, in accordance with the provisions of subsection a) of Article 1 of the Consolidated Text of the Organic Law of the Superintendency of the Securities Market – SMV (hereinafter, the Organic Law of the SMV), approved by Decree Law No. 26126 and its amendments, the SMV is empowered to issue legal rules regulating matters of the securities market;
That, in accordance with subsection b) of Article 5 of the aforementioned rule, the Board of Directors of the SMV has the power to approve the regulations of the securities market, as well as those to which natural and legal persons subject to its supervision must adhere;
That, Article 16-B of the Securities Market Law - LMV, approved by Legislative Decree No. 861, establishes that legal persons authorized by the SMV must establish a Risk Management System in accordance with the rules established by the SMV;
That, on 20 December 2015, the Comprehensive Risk Management Regulation, approved by SMV Resolution No. 037-2015-SMV/01, was published in the Official Gazette El Peruano, which establishes minimum criteria for the Entities to which the SMV grants operating authorization to adequately develop their comprehensive risk management;
That, on 15 September 2016, the Operational Risk Management Regulation was approved by SMV Resolution No. 027-2016-SMV/01, with the purpose of establishing provisions that regulate with greater specificity and independently various aspects associated with operational risk, as part of the management of the inherent risks to which said Entities are exposed;
That, as part of the process of implementing risk-based supervision in the SMV, certain modifications are necessary to provide guidelines for the recording of operational risk loss events, set requirements for the identification and assessment of the impact of significant changes in the Entity, as well as provide guidelines to adequately monitor outsourced services and incorporate the obligation to report operational risk indicators; with the purpose of guaranteeing the correct development of operations by the Entities supervised by the SMV and contributing to improving off-site and on-site supervision processes;
That, the evolution of the financial industry, particularly the incorporation of information technologies in the way of generating, processing and managing its information assets; involve new risks that affect the intrinsic processes of the institution's business as well as enable changes in the development of its operations. Therefore, it is essential to regulate minimum cybersecurity management standards applicable to the Entities to which the SMV grants operating authorization, and to provide guidelines for cloud data processing, so that they are developed adequately;
That, it should be noted that, in relation to the outsourcing of data processing abroad, the supervised entity, for the adequate risk management of this activity may, among other aspects, take into account criteria such as the political stability and security of the jurisdictions where the outsourced data processing service provider will operate, without prejudice to its obligation to ensure that the risks it identifies remain within acceptable limits and proportional to the data processing activity that the Entity will outsource outside the country;
That, the DRAFT was disseminated for public consultation through the SMV's Securities Market Portal for a period of thirty (30) business days, as provided by SMV Resolution No. 032-2018-SMV/01, published on 30 November 2018 in the Official Gazette El Peruano; and,
In accordance with the provisions of subsection a) of Article 1 and subsection b) of Article 5 of the Organic Law of the SMV; the second paragraph of Article 8 of the Securities Market Law, Legislative Decree No. 861 and its amendments; numeral 2 of Article 9 of the Regulation of Organization and Functions of the SMV, approved by Supreme Decree No. 216-2011-EF; as well as what was agreed by the Board of Directors of the SMV in its session of 22 March 2019;
Article 1.- Amend Articles 2 and 3 of TITLE I GENERAL PROVISIONS of the Operational Risk Management Regulation, approved by SMV Resolution No. 027-2016-SMV/01, in accordance with the following text:
For the application and/or implementation of the provisions of this Regulation, the following definitions shall be considered:
a) Asset: Any element that has value for an individual, an entity or a government.
b) Virtual asset: Representation of an asset in Cyberspace.
c) Loss event database (BDEP): The database of operational risk loss events referred to in Article 8 of this Regulation.
d) Significant Change: Any change in the operating, computer or business environment that has a significant influence on the risk profile of an Entity.
e) Pe-CERT: Coordinator of Emergency Responses in Teleinformatic Networks of the Public Administration of Peru.
f) CSIRT (Computer Security Incident Response Team): Team responsible for the development of preventive measures and response to computer incidents.
g) Cyberthreat or cyber threat: The appearance of a potential or actual situation that could become a cyberattack.
h) Cyberattack or cyber attack: Organized or
premeditated criminal action by one or more agents who use the services or applications of cyberspace or are the target of the same or where cyberspace is the source or tool for the commission of a crime.
i) Cyberspace: Complex environment resulting from the interaction of people, software and services on the Internet through technological devices connected to said network, which does not exist in any physical form.
j) Cybersecurity: Condition of being protected against physical, social, financial, emotional, occupational, psychological, educational or other consequences resulting from failure, damage, error, accidents, damages or any other event in Cyberspace that may be considered undesirable.
k) Confidentiality: Information must be kept in reserve, and may be accessible only to those users who are duly authorized, trained and supervised.
l) Availability: Information must be accessible to authorized users when required.
m) Operational Risk loss event: The event that leads to one or several losses, whose origin corresponds to operational risk. In this Regulation, the terms “operational risk loss event” and “loss event” shall be used interchangeably with the same meaning.
n) Key Risk Indicators: Metric that provides information about the Entity's level of exposure to a specific operational risk at a given moment.
o) Business interruption: Event that generates the total or significant partial interruption of one or more business lines or their support processes for thirty (30) continuous minutes or more.
p) Loss: It is a negative impact on the Entity's results or equity.
q) Information security incident: Event associated with a possible failure in the security policy, a failure in controls, or a previously unknown situation relevant to security, which has a significant probability of compromising business operations and threatening information security.
r) Information: Any form of electronic, optical, magnetic or other similar media record, susceptible to being processed, distributed and stored.
s) Integrity: Information must be complete, accurate and truthful.
t) Insourcing: Management modality through which an Entity again develops a process that was previously outsourced.
u) Community Cloud: Cloud infrastructure available for the exclusive use of a specific community of entities, including the case of several entities of the same group.
v) Hybrid Cloud: Cloud infrastructure composed of two or more distinct cloud infrastructures.
w) Private Cloud: Cloud infrastructure available for the exclusive use of a single entity.
x) Public Cloud: Cloud infrastructure available for open use by the general public.
y) Maximum tolerable period of interruption: It is the period, determined by the Entity, after which the viability of the Entity would be seriously affected, if a particular product or service is not resumed.
z) Main supplier: It is one that, if its operations were interrupted, would significantly affect the continuity of the Entity's business. In addition to those with which there is a significant outsourcing, public service providers such as: telecommunications, energy, among others, must be considered.
aa) Regulation: The Operational Risk Management Regulation.
bb) GIR Regulation: The Comprehensive Risk Management Regulation, approved by SMV Resolution No. 037-2015-SMV/01.
cc) Cloud services: Services provided using cloud computing, that is, a model that allows ubiquitous, convenient and on-demand network access to a shared set of configurable computing resources (for example, networks, servers, storage, applications and services) that can be quickly provisioned and deployed, requiring minimal management effort or interaction with the service provider.
dd) SIEM (Security Information and Event Management): Information system that provides real-time analysis of security alerts generated by applications, security devices and network elements. They are usually log centralization systems.
ee) Outsourcing: Management modality through which an Entity contracts a third party to develop a process that could be carried out by the contracting Entity.
ff) Chain outsourcing: It is that outsourcing where the supplier, in turn, subcontracts parts of the service to other suppliers.
gg) Significant outsourcing: It is that outsourcing that, in the event of failure or suspension of the service, can put the Entity at risk, by significantly affecting its income, solvency or business continuity.
hh) Recovery time objective: It is the time established by the Entity to resume a process, in the event of an operational interruption event. It is less than the maximum tolerable period of interruption.
Likewise, the definitions contained in the GIR Regulation shall apply.
Hereinafter, the aforementioned terms may be used in singular or plural form, without implying a change in their meaning. Unless otherwise mentioned, reference to specific articles must be understood as made to the corresponding ones of this Regulation.
This Regulation establishes the minimum general guidelines, criteria and parameters that the Entity must observe in the design, development and application of its operational risk management, in accordance with the nature and proportionality of the business, which must consider the size of the entity, the volume of transactions and the complexity of the operations it carries out.
As part of adequate operational risk management, Entities must implement an information security management system and business continuity management.”
Article 2.- Amend TITLE III INFORMATION SECURITY MANAGEMENT and articles 9, 10 and 11 of the Operational Risk Management Regulation, approved by SMV Resolution No. 027-2016-SMV/01, in accordance with the following text:
The Entity must implement an information security management system that allows guaranteeing the integrity, confidentiality and availability of information, as well as effectively managing its risks, including cybersecurity risks, through the adequate combination of policies, procedures, controls, organizational structure and specialized computer tools.
To this end, it must at least carry out the following activities:
a) Definition of an information security policy that includes cybersecurity aspects, and that is approved by the Board of Directors or equivalent body.
b) Definition and implementation of an information security management methodology, which includes cybersecurity aspects, in accordance with the provisions of article 7 of the Regulation, and that is consistent with the Entity's comprehensive risk management.
c) Maintenance of adequate records that allow verifying compliance with the rules, standards, policies, procedures and others defined by the Entity, as well as maintaining sufficient audit evidence.
The Entity must have an organizational structure that allows it to implement and maintain the information security management system, for which it must:
a) Establish, maintain and disseminate information security and cybersecurity policies and procedures.
b) Clearly assign and distribute roles and responsibilities.
c) Identify, evaluate and treat information security and cybersecurity risks, in accordance with the provisions of literal b of article 9 of this Regulation.
d) Determine all the controls that are necessary to implement the chosen option(s) for information security and cybersecurity risk treatment.
e) Develop awareness and training activities in information security and cybersecurity, to keep them updated on new cyber threats, both within the entity and with respect to users and third parties that it considers relevant.
f) Continuously evaluate events associated with a possible failure in the security policy, in the controls or a previously unknown situation relevant to security and recommend appropriate actions. g) Develop communication plans to determine responsibilities in decision-making, as well as the policies and procedures to disclose potential vulnerabilities;
h) Direct and promote that personnel contribute to the effectiveness of the information security management system; and,
i) Report to the Board of Directors or equivalent body or to the Risk Committee, according to its organization, on the performance of the information security management system with the frequency determined by the Entity, which may not be greater than 6 months.
Entities must implement, in accordance with their size, volume of transactions and complexity of their operations, the following controls as part of information security and cybersecurity management:
1. Access control:
a) Formal procedures for the granting, administration of rights and profiles, as well as the revocation of users.
b) Periodic reviews of the rights granted to users.
c) Users must have an identification for personal use, in such a way that possible responsibilities can be traced and identified.
d) Special controls on system utilities and audit tools.
e) Monitoring of access and use of systems to detect unauthorized activities.
f) Special controls on remote users and mobile computing.
2. Human resources security:
a) Definition of roles and responsibilities established regarding information security and cybersecurity.
b) Background verification (criminal, judicial, credit, etc.), in accordance with the classification of information to which they will have access.
c) Awareness and training on new and emerging risks.
d) Disciplinary processes in case of non-compliance with information security policies.
e) Procedures defined in case of termination of personnel, which include aspects such as the revocation of access rights and the return of assets.
3. Physical and environmental security:
a) Controls to prevent unauthorized physical access, damage or interference to the Entity's premises and information.
b) Controls to prevent loss, damage or theft of assets, including the protection of equipment against physical and environmental threats.
a) Carry out and maintain an inventory of assets and assign responsibilities regarding the protection of these assets. Those virtual assets relating to the entity's presence in cyberspace must be considered in this inventory.
b) Classify the assets, based on the type of information they contain or process and the value they hold for the business, indicating the existing risk level for the Entity, as well as the appropriate control measures that must be associated with the classifications.
a) Documented procedures for system operation.
b) Control over changes in the operating environment, which includes changes to information systems, processing facilities, and procedures.
c) Separation of functions to reduce the risk of error or fraud.
d) Separation of development, testing, and production environments.
e) Controls to protect data in transit and at rest.
f) Implement tools or services that allow for event correlation that can alert about security incidents, such as a SIEM.
g) Monitoring of the service provided by third parties.
h) Configure servers, including the underlying operating systems, in accordance with a base security configuration guide.
i) Run anti-malicious software controls (such as spyware or malware) on the server.
j) Processing capacity management.
k) Preventive and detection controls over the use of software of dubious origin, viruses, and other similar items.
l) Security over networks, storage media, and system documentation.
m) Security over information exchange, including email.
n) Security over electronic channels.
o) Maintenance of audit logs and monitoring of system use.
p) Depending on the structure, service channels, transaction volume, and number of clients, monitor different sources of information such as websites, blogs, and social networks, for the purpose of identifying possible cyberattacks against the Entity.
For security management in the acquisition, development, and maintenance of computer systems, the following criteria, among others, must be taken into account:
a) Include in the requirements analysis for new systems or improvements to current systems, controls over information input, processing, and output information.
b) Apply encryption techniques to critical information that must be protected. c) Define controls over the implementation of applications before going into production.
d) Control access to source code program libraries.
e) Maintain a strict and formal change control, which will be duly supported by computer systems in the case of complex environments or those with a high number of changes.
f) Ensure scripting of web interfaces to prevent XSS attacks.
g) Implement session management for web applications with access to sensitive and/or business-relevant information.
h) Control the handling of data inputs to prevent SQL injection attacks.
i) Perform source code reviews for services provided in cyberspace.
j) Control existing technical vulnerabilities in the Entity's systems.
a) Regular and validated backup procedures with the frequency determined by the Entity. These procedures must include the necessary measures to ensure that essential information can be recovered in the event of media failure or after a disaster. These measures will be consistent with the Entity's business continuity strategy.
b) Keep backup information and restoration procedures in a location that avoids exposing them to possible events that could compromise the operation of the main processing center.
To ensure that security incidents and vulnerabilities are controlled in a timely manner, the Entity must consider the following aspects:
a) Formal procedures for reporting information security incidents and vulnerabilities associated with information systems.
b) Established procedures to give an adequate response to reported security incidents and vulnerabilities.
c) Establish the procedures to report, when considered pertinent, to the national CSIRT (Pe-CERT or whoever acts on its behalf regarding private entities), directly or through sectoral CSIRTs, if applicable, the cyberattacks that require its management.
The Entity shall ensure that legal, contractual, or regulatory requirements are complied with and, where applicable, incorporated into the internal logic of computer applications.
10. Information privacy: The Entity must adopt measures that reasonably ensure the privacy of the information it receives from its clients and service users, in accordance with the regulations in force on the matter”.
Article 3°.- Amend article 16 and incorporate it into TITLE V OTHER PROVISIONS of the Operational Risk Management Regulations, approved by Resolution SMV N° 027-2016-SMV/01, according to the following text:
The following are considered significant changes in an illustrative, but not limited, manner:
a) Provision of new services and products, significant modifications and/or cessation in the provision thereof.
b) Changes to the technological infrastructure that supports the main products and/or services.
c) New service channels and/or significant modifications thereof.
d) Mergers, acquisitions and/or any corporate reorganization.
e) Change of main office.
f) Significant subcontracting, insourcing of significant activities and/or modifications thereto, or other relevant change in processes.
This list may be expanded by Resolution of the Superintendent of the Securities Market.
The Entity shall carry out an assessment of all risks associated with significant changes, taking as a minimum reference the risk types indicated in the Comprehensive Risk Management Regulations.
Prior to making decisions on significant changes, a report containing the results of said assessment shall be submitted to the Board of Directors, Risk Committee or specialized body. The report shall contain as a minimum the information on the change (description, objectives, associated processes, etc.), the identified risks (differentiated by risk types), as well as the treatment measures implemented or to be implemented, and this must be available to the Superintendency.
Article 4°.- Amend Articles 17 and 18 of TITLE V OTHER PROVISIONS of the Operational Risk Management Regulations, approved by Resolution SMV N° 027-2016-SMV/01, in accordance with the following text:
Entities assume full responsibility for all subcontracted services and activities, as well as for the management decisions arising from them, and may be sanctioned for non-compliance with their regulatory obligations.
To this end, entities shall:
1. Establish formal policies and procedures to determine the level of risk represented by each subcontracting.
2. Based on the results obtained in point 1, control mechanisms shall be implemented that should apply from the beginning to the completion of a subcontracting (selection of the provider, design of the contract, monitoring of the service, continuity plans and exit strategies).
3. Maintain an updated record of information on all subcontracting, considering as a minimum the following: Name of the provider, description of the service(s), type of subcontracting (significant and non-significant), start date, end date, description of the modifications made to the contract.
These provisions are also applicable to intra-group subcontracting, that is, the provision of services by a separate legal entity belonging to the same economic group.
Likewise, any significant subcontracting shall be treated as a significant change.
In the case of significant cloud subcontracting, in addition to the considerations mentioned in the preceding paragraphs, and prior to making decisions on outsourcing, an enhanced due diligence of the provider and the service shall be carried out, at least considering the following aspects:
1. Access and audit rights. Entities that subcontract shall take into account the limitations to the effective exercise of access and audit rights. However, the entity may rely on external certifications and internal or external audit reports provided by the cloud service provider, provided that:
a. The outsourcing entity ensures that the scope of the certification or audit report includes the systems (that is, the processes, applications, infrastructures, data centers, etc.) and the controls it considers key associated with the service provided.
b. The outsourcing entity evaluates in depth the content of the certifications or audit reports on a continuous basis and, in particular, ensures that the key controls continue to be included in future versions of an audit report and verifies that the certification or audit report is not outdated.
c. The certifications are issued and the audits are carried out in accordance with generally accepted standards and include a test of the operational effectiveness of the established key controls.
2. Data and systems security. The entities must take into account the aspects related to data and systems security, carrying out at a minimum the following actions:
a. Identify and classify the activities, processes and related data and systems based on their sensitivity and the protection measures required.
b. Carry out a risk-based selection of the activities, processes and related data and systems that are being considered for outsourcing to a cloud computing solutions provider.
c. Define and decide the appropriate level of protection of information confidentiality, the continuity of the outsourced activities, as well as the integrity and traceability of the data and systems in the context of the planned cloud service outsourcing (public, private, hybrid or community). d. Consider adopting specific measures when necessary to protect data in transit, data in memory and data at rest, such as the use of encryption technologies combined with an adequate key management architecture.
3. Location of data and data processing. In the case of data processing abroad, they must act with special prudence, given the possible risks related to data protection, considering the following:
a. The entity that decides to outsource will evaluate the location of the data and data processing with a risk-based approach.
b. The outsourcing entity must ensure that the identified risks remain within acceptable limits and proportional to the importance of the outsourced activity.
4. Chain outsourcing. The entity must take into account the risks associated with "chain" outsourcing when the provider of the outsourced service subcontracts parts of the service to other providers. The entity shall accept chain outsourcing only if the subcontractor also fully complies with the existing obligations between the entity (which outsources) and the service provider (which is outsourced).
5. Clearly defined continuity plans and exit strategies. The entity shall propose and implement measures to maintain business continuity in the event that the provision of services by the provider fails or deteriorates to an unacceptable degree. Likewise, it shall ensure that it can exit cloud service outsourcing agreements, if necessary, without causing excessive disruptions to the services provided, nor negatively affecting its compliance with the regulatory regime, nor compromising the continuity and quality of the services provided to its clients.
The Entities must submit periodic reports to the SMV on Operational Risk, Information Security and Business Continuity management, with the aim of being able to carry out permanent monitoring of activities and having an organized scheme that allows for sufficient, relevant and timely information for decision-making.
The series of indicators are detailed in Annex III and are comprised of the following reports:
| Management System | Report | Description | Frequency |
|---|---|---|---|
| Operational Risk | RO_r1 | Operational Risk Loss Events. | Quarterly |
| RO_r2 | Significant Changes | Monthly | |
| Information Security | SI_r1 | Identified vulnerabilities. | Quarterly |
| SI_r2 | Investment in Cybersecurity. | Annual | |
| Business Continuity | CN_r1 | Interruption Events. | Quarterly |
| CN_r2 | Activation of Continuity Plans. | Quarterly | |
| CN_r3 | Main Suppliers. | Semiannual | |
| CN_r4 | Continuity Plans and Tests. | Semiannual |
All indicator reports must be submitted to the SMV within thirty (30) calendar days after the close of the period subject to reporting. In the event that no "Significant Changes" have occurred during the month to be reported, the submission of the RO_r2 report shall not be required.
By Circular, the SMV shall communicate the reporting channel, as well as the formats together with their respective methodological notes.
Article 5.- Incorporate article 19 into TITLE V OTHER PROVISIONS of the Operational Risk Management Regulation, approved by SMV Resolution No. 027-2016-SMV/01, in accordance with the following text:
The Entities must retain the information referred to in this Regulation for a period of no less than ten (10) years".
Article 6.- Modify the content of ANNEX I TYPES OF OPERATIONAL RISK LOSS EVENTS of the Operational Risk Management Regulation, approved by SMV Resolution No. 027-2016-SMV/01, in accordance with the following text:
| Event type (Level 1) | Definition | Event type (Level 2) | Examples |
|---|---|---|---|
| Internal fraud | Losses derived from any type of action aimed at defrauding, misappropriating assets or breaching regulations, laws or internal policies in which employees of the Entity are involved, and which has the purpose of obtaining an illicit benefit. | Unauthorized activities | Undisclosed transactions (intentionally), unauthorized transactions (with pecuniary losses), erroneous valuation of positions (intentional). |
| Theft and fraud | Theft, embezzlement, forgery, bribery, account appropriation, smuggling, tax evasion (intentional). | ||
| External fraud | Losses derived from any type of action aimed at defrauding, misappropriating an asset improperly or breaching legislation, by a third party, in order to obtain an illicit benefit. | Theft and fraud | Theft, forgery. |
| Systems security | Damage from computer attacks, theft of information. | ||
| Labor relations and workplace safety | Losses derived from actions incompatible with legislation or labor agreements, regarding health or safety at work, the payment of claims for personal damages, or cases related to diversity or discrimination. | Labor relations | Matters related to remuneration, social benefits, termination of contracts. |
| Health and safety at work | Cases related to health and safety at work standards; compensation to workers. | ||
| Diversity and discrimination | All types of discrimination. |
| Practices related to clients, products, services and Business | Losses derived from involuntary or negligent breach of an obligation to clients or generated by deficiency in the product or service. | Suitability, disclosure of information and trust | Abuses of trust / breach of guidelines, suitability aspects / disclosure of information (client knowledge, etc.), breach of privacy of client information, breach of privacy, aggressive sales, abuse of confidential information the privacy of client information, breach of privacy, aggressive sales, abuse of confidential information. |
|---|---|---|---|
| Improper business or market practices | Restrictive practices of competition, improper commercial / market practices, market manipulation, use of insider information, money laundering and financing of terrorism. | ||
| Defective products | Product defects (unauthorized, etc.), error of the models. | ||
| Selection, sponsorship and risks | Absence of investigation of clients in accordance with the guidelines, excess of risk limits against clients. | ||
| Advisory activities | Litigation over results of advisory activities. | ||
| Damage to physical assets | Losses derived from damage or harm to material assets as a consequence of natural disasters or other events. | Disasters and other events | Losses from natural disasters, human losses from external causes (terrorism, vandalism). |
| Business interruption due to failures in information technology | Losses derived from interruptions in business and from failures in the systems. | Systems | Losses from failures in hardware, software or telecommunications equipment; failure in electrical power. |
| Deficiency in the execution, delivery and management of processes | Losses derived from errors in the processing of operations or in the management of processes, as well as from relations with counterparties, such as suppliers, clients, among others. | Reception, execution and maintenance of operations | Errors of data entry, maintenance or download, breach of deadlines or responsibilities, erroneous execution of models / systems, accounting errors. Errors in the securities compensation process and |
| cash settlement (e.g. in Delivery vs. Payment). | |||
| Monitoring and presentation of reports | Breach of the obligation to report, inaccuracy of external reports (with generation of losses). | ||
| Acceptance of clients and documentation | Nonexistence of authorizations /rejections of clients, nonexistent / incomplete legal documents. | ||
| Management of client accounts | Unauthorized access to accounts, incorrect records of clients (with generation of losses), loss or damage of client assets due to negligence. | ||
| Commercial counterparties | Failures of counterparties other than clients, other litigation with counterparties other than clients. | ||
| Distributors and suppliers | Subcontracting, litigation with suppliers. |
Article 7.- Incorporate the following annexes: ANNEX II GUIDELINES FOR THE REGISTRATION OF LOSS EVENTS DUE TO OPERATIONAL RISK and ANNEX III KEY RISK INDICATORS to the Operational Risk Management Regulation, approved by Resolution SMV N° 027-2016-SMV/01, in accordance with the following text:
The gross loss amount associated with an event, which will be registered in the BDEP, must include the following aspects, as applicable:
a. Direct impact on the financial statements, including expenses, decrease in the value of assets, among others.
b. Repair or replacement expenses to restore the situation existing before the occurrence of the event, including the payment of deductibles associated with the contracted insurance.
c. Provisions recognized in the financial statements associated with loss events due to operational risk.
The following aspects must not be considered in the determination of the gross loss amount:
a. Recoveries after the occurrence of the loss event.
b. Expenses from general maintenance contracts for equipment or premises.
c. Expenses associated with improvements made after the loss event.
d. Insurance premiums.
Loss events associated with damage to fixed assets that render them unusable must be recorded in the BDEP in accordance with the following provisions:
a. If the damaged asset is replaced, the acquisition cost of the new asset must be recorded as a loss.
b. If the damaged asset is not replaced, the estimated market price of said asset must be recorded as a loss or, if this is not known, the historical acquisition cost must be recorded. On the other hand, if the asset is replaced at a later date, the loss amount recorded in the BDEP must be modified by the acquisition cost of the new asset.
In cases where an event simultaneously produces losses and gains for the Entity, with a negative net balance, said balance must be considered for the calculation of the loss amount and its recording in the BDEP.
Loss events associated with claims submitted by users must be incorporated into the BDEP, including those cases of operations not recognized by users because they are presumably fraudulent operations, and those in which the Entity decides to assume the loss without conducting a full investigation.
Any recovery associated with the event must be recorded in the BDEP separately from the gross loss amount. A recovery will be considered as such whenever it occurs independently and subsequent to the occurrence of the original loss event.
Below is a non-limiting list of recoveries:
a. Payments received from an insurance company after the execution of contracted policies.
b. Payments received as a favorable result of a judicial or arbitration process.
c. Payments made by a third party providing services to the Entity, with the aim of mitigating the negative impact of the occurrence of a loss event for which it is responsible that affected both parties.
d. Payments received from clients or employees as a result of the recovery process.
The provisions referred to in literal c of numeral 1 must be recorded in the BDEP, including, among others, those related to judicial disputes, arbitration processes and administrative proceedings.
The amount assigned in the BDEP to this provision must be updated as many times as the provision is modified. At the moment the final loss amount associated with the event is known with certainty, the amount of the recorded provision must be replaced by the final amount. The Entity must establish specific procedures for the proper execution of the aforementioned tasks.
The provisions recorded in the BDEP must be clearly identified, so that they can be distinguished from other impacts associated with the event, for which the Entities must develop and implement appropriate internal procedures.
In the case of an event with multiple losses, the Entities may record the minimum information required for each loss, and must establish a way to group said information by the event that originated them, that is, the initial event without which none of the related losses would have occurred.
Below is a non-limiting list of multiple losses:
a. Repeated errors caused by a failure in a business process or service.
b. Refunds to various clients arising from a common claim or caused by a single event (for example, the loss of documents during a move or due to a fire).
c. Losses due to fraud carried out through the same action and by the same person or criminal group.
d. An interruption of technology services that affects multiple lines of business.
e. An individual or group of officials who receive erroneous instructions that generates multiple losses.
Multiple errors caused by the same person over a given period must be treated as independent events, and therefore must not be grouped in the BDEP. For example, losses on the trading desk due to operational errors by a representative at different times.
The Entity must establish procedures that guarantee the recording in the BDEP of those events with multiple losses that, as a whole, exceed the minimum loss recording amount established by the Entity, even though the gross amount of each individual loss caused by the same event is less than the minimum recording amount.
Events that lead to opportunity costs or unrealized gains may be recorded in the BDEP as long as they are objectively measurable and verifiable against operations of a similar nature under normal business conditions, for example, commissions not charged on redemptions of fund units due to errors associated with an operational risk.
There are various events whose recording in the BDEP is not mandatory. Below is a non-limiting list of this type of events:
a. Those that did not lead to losses, but that, under other circumstances, could have been actual losses, known as “near losses”. For example, when money is transferred to a wrong account, but, after its identification, its reversal occurs on the same day of the transfer, avoiding the negative impact for the Entity.
b. Events that led to gains, except that there has simultaneously been an event that generates losses and gains, with a negative net result, which must be recorded in the BDEP, as indicated in paragraph 4 of numeral 1 of this annex.
c. Events that represent only temporary accounting losses due to failures in the recording of the Entity's financial information, and that, once corrected, do not signify actual financial losses, unless, as a result of said failures, administrative sanctions or other related ones are produced, which must be recorded in the BDEP.
d. Expenses of an internal nature or transfer costs, which have been generated regardless of the occurrence of the event, although expenses associated with overtime are included when compared with usual schedules, provided that these represent effective losses associated with operational risk loss events.
The Entities will evaluate the possible advantages associated with having the information indicated in the preceding letters. If the Entity decides to record it, the events will be clearly identified in the database, so that said events can be precisely distinguished from those required by the regulations, for which they must develop and implement appropriate internal procedures".
| Reporting year | Quar-ter | Event type (Level 1) | Event type (Level 2) | Number of events per quarter | Maximum loss per quarter | Total gross amount (a) | Total recovered amount (b) | Total net amount (a)-(b) | % of Total (a-b)/(c) |
|---|---|---|---|---|---|---|---|---|---|
| 2019 | 3 | Internal fraud | Unauthorized activities | S/ | % | ||||
| Theft and fraud | |||||||||
| External fraud | Theft and fraud | S/ | % | ||||||
| Systems security | |||||||||
| Employment practices and workplace safety | Labor relations | S/ | % | ||||||
| Health and safety at work | |||||||||
| Diversity and discrimination | |||||||||
| Clients, products and business practices | Suitability, information disclosure and trust | S/ | % | ||||||
| Improper business or market practices | |||||||||
| Defective products | |||||||||
| Selection, sponsorship and risks | |||||||||
| Advisory activities | |||||||||
| Damage to physical assets | Disasters and other events | S/ | % | ||||||
| Business disruption due to information technology failures | Systems | S/ | % | ||||||
| Deficiency in execution, delivery and process management | Receipt, execution and maintenance of operations | S/ | % | ||||||
| Monitoring and reporting | |||||||||
| Client acceptance and documentation | |||||||||
| Client account management | |||||||||
| Commercial counterparties | |||||||||
| Distributors and suppliers | |||||||||
| Quarter total | 0 | S/ | S/ | S/ | (c) | 0% |
Methodological notes: 1) For the purposes of this report, consider the definition for each type of event in accordance with the provisions of Annexes I and II of the Operational Risk Management Regulation. 2) In the "Reporting year" column, enter the year with four digits. Likewise, in the "Quarter" column, enter 1, 2, 3 or 4 as applicable. 3) Information related to loss events recorded in the database shall be entered. Depending on the type of event (level 1 and 2), the number of recorded events, the amount of the maximum recorded loss (the largest recorded event), the total gross loss amount (referring to the total number of events), the total amount recovered with existing coverages, the total net loss amount, and finally the ratio of the net amount to the total accumulated net loss must be filled in.
| Reporting year | Quarter | Month | Significant change (a) | Description of the change (b) | Business Line | Related product | Related support process | Risk report number | Total changes in the quarter (c) | % of Total (c)/(d) |
|---|---|---|---|---|---|---|---|---|---|---|
| 2019 | 1 | January | % | |||||||
| February | ||||||||||
| March | ||||||||||
| 2 | April | % | ||||||||
| May | ||||||||||
| June | ||||||||||
| Annual total of Significant Changes (d) | 0 | 0% |
Methodological notes: 1) In the "Reporting year" column, enter the year with four digits. In the "Quarter" column, enter 1, 2, 3 or 4 as applicable. Likewise, in the "Month" column, enter the name of the month referred to. 2) The report must be prepared taking into consideration the following: (a): Take as reference the list of significant changes indicated in Article 19 of the Operational Risk Management Regulation. (b): Indicate a brief description of the significant change. 3) In all cases, the business line where the significant change was made must be selected, as well as the product and/or support process affected by the significant change. 4) It shall be reported only if there is any significant change during the referred period, through the channel and in the manner determined by the SMV.
| Vulnerabilities | ||||
|---|---|---|---|---|
| Reporting year | Reporting quarter | Month | Number of high and critical vulnerabilities identified (a) | Number of high and critical vulnerabilities corrected (b) |
| 2019 | 1 | 1 | ||
| 2 | ||||
| 3 | ||||
| Quarter total | 0 | 0 |
Methodological notes: 1) The report must be prepared taking into consideration the following: (a): Indicate the total number of high and critical vulnerabilities identified during the measurement period (month)
(b): Indicate the total number of high and critical vulnerabilities corrected during the measurement period (month)
2) In the "Reporting year" column, enter the year with four digits. Likewise, in the "Quarter" and "Month" columns, enter 1, 2, 3 or 4 as applicable.
3) Vulnerability shall be understood as any deficiency and/or weakness of an operating system, application or technological equipment, which can be exploited by unauthorized users for non-genuine purposes (usually to cause harm). A vulnerability shall be considered high or critical when it has a CVSS (Common Vulnerability Scoring System) score greater than or equal to 7.
| Total | ||||
|---|---|---|---|---|
| (Figures in Thousands of soles) | 2018 | 2019 | 2020 | 2021 |
| IT Investment (a) | ||||
| a/c | % | % | % | % |
| a/d | % | % | % | % |
| Cybersecurity Investment (b) | ||||
| b/c | % | % | % | % |
| b/d | % | % | % | % |
| Perimeter security | ||||
| Network security | ||||
| Protection of network access devices | ||||
| Application security | ||||
| Systems Development | ||||
| Internal Training | ||||
| Consultancies | ||||
| Others | ||||
| Total Investment (a+b) | ||||
| (a+b)/c | % | % | % | % |
| (a+b)/d | % | % | % | % |
| Gross Profit (c) | ||||
| Operating Expenses (d) |
1) The report must be prepared taking into consideration the following:
(a): Indicate the amount of investment in Information Technology (IT) for the indicated period.
(b): Indicate the amount of investment in Cybersecurity (considering the sum of the fields detailed for each domain) for the indicated period.
(c): Indicate the Gross Profit (individual) for the indicated period.
(d): Indicate the Operating Expenses (individual) for the indicated period.
Interruptions of business
Interruptions due to failures in computer systems Interruptions due to failures in main suppliers Year of report Tri- mester of report Month Number of interrup- tions (a) Time (min) total of interruption (b) Number of interrup- tions (c) Time (min) total of interrup- tion (d) Proportion of interruptions due to failures in the systems (c )/(a) Proportion of the time of interruption due to failures in the systems (d)/(b) Number of interrup- tions (e) Time (min) total of interrup- tion (f) Proportion of interruptions due to failures in main suppliers (e)/(a) Proportion of time of interruption due to failures in suppliers main (f)/(b) Total of the company 1 2 3
1) The report must be prepared taking into consideration the following:
(a): Indicate the total number of interruptions occurring during the measurement period (month), in the corresponding line of business
(b): Indicate the total interruption time during the measurement period (month), in the corresponding line of business
(c): Indicate the number of interruptions due to system failures during the measurement period (month), in the corresponding line of business
(d): Indicate the interruption time due to system failures during the measurement period (month), in the corresponding line of business
(e): Indicate the total number of interruptions due to supplier failures during the measurement period (month), in the corresponding line of business
(f): Indicate the interruption time due to supplier failures during the measurement period (month), in the corresponding line of business
2) In those cases in which an interruption does not exceed thirty (30) minutes due to the activation of business continuity plans, said interruption shall not be considered for the purposes of this report.
3) If an event affects more than one line of business, said event must be reported in each of the affected lines of business.
4) Since there are interruption events that may affect more than one line of business, as indicated in the previous paragraph, the report for the "Total of the company" line will not always be the sum of the number of interruptions and times recorded in each of the lines of business.
5) Interruption events that significantly affect the operational continuity of any service channel, such as branches, ATMs, correspondent tellers or others, must be reported in the line(s) of business affected by said event. It should be noted that the unavailability of 50% or more service points of said channel nationwide or in a given region shall be considered a significant interruption of a service channel.
6) In the "Report Year" column, enter the year with four digits. Likewise, in the "Report Quarter" column, enter 1, 2, 3 or 4, as applicable.
Number of times a continuity plan was activated of the business Percentage of TORs that were not met Year of report Quarter of the report Month Crisis management plan (a) Emergency plan (b) Business continuity plan(s) ( c) IT service recovery plan TI (d) Upon activating the business continuity plan(s) (e ) Upon activating the IT service recovery plan TI (f) 1 2 3
1) TOR: Target recovery time
2) IT: Information technology
3) The report must be prepared taking into consideration the following:
(a): Indicate the number of times the Crisis Management Plan was activated during the measurement period (month).
(b): Indicate the number of times any of the company's emergency plans was (were) activated during the measurement period (month).
(c): Indicate the number of times any of the company's business continuity plans was (were) activated during the measurement period (month).
(d): Indicate the number of times the IT services recovery Plan was activated during the measurement period (month).
(e): (No. of TORs not met / Total No. of TORs that should have been met upon activating the business continuity plans activated during the measurement period)*100%.
(f): (No. of TORs not met / Total No. of TORs that should have been met upon activating the IT services recovery plan during the measurement period)*100%.
4) In the “Reporting year” column, enter the year with four digits. Likewise, in the “Reporting quarter” column, enter 1, 2, 3 or 4, as applicable.
| Reporting year | Reporting semester | Total No. of main suppliers (a) | No. of main suppliers with BCP or for which the company has an alternative supplier (b) | Ratio (b)/(a) |
|---|---|---|---|---|
1) BCP: Business continuity plan
2) For the purposes of this report, consider the definition of main supplier described in article 2 of the Operational Risk Management Regulation.
3) The report must be prepared taking into consideration the following:
(a): Indicate the total number of main suppliers.
(b): Indicate the number of main suppliers that have a business continuity plan and/or an alternative supplier. If the main supplier has a business continuity plan and, in addition, an alternative supplier is available, it must be counted and reported as a single supplier.
4) In the “Reporting year” column, enter the year with four digits. Likewise, in the “Reporting semester” column, enter 1 or 2, as applicable.
| Crisis management plan | Emergency plan | Business continuity plan(s) | IT services recovery plan | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Reporting year | Reporting semester | Number of plans (a) | Number of plans tested (b) | Number of plans (c) | Number of plans tested (d) | Number of plans (e) | Number of plans tested (f) | Number of plans (g) | Number of plans tested (h) |
1) IT: Information technology
2) The report must be prepared taking into consideration the following:
(a), (c), (e) and (g): Indicate the number of crisis management plans (a), emergency plans (c), business continuity plans (e) and IT services recovery plans (g), respectively.
(b), (d), (f) and (h): Indicate the number of crisis management plans (b), emergency plans (d), business continuity plans (f) and IT services recovery plans (h) that had been tested in the reporting semester.
3) In the “Reporting year” column, enter the year with four digits. Likewise, in the “Reporting semester” column, 1 or 2 must be entered, as applicable
| Business continuity plans | IT services recovery plan | ||||
|---|---|---|---|---|---|
| Reporting year | Reporting semester | Total number of tests performed (a) | Percentage of TORs not met (b) | Total number of tests performed (c ) | Percentage of TORs not met (d) |
1) IT: Information technology
2) The report must be prepared taking into consideration the following:
(a): Indicate the total number of tests performed on business continuity plans.
(b): (No. of TORs not achieved / Total No. of TORs that should have been achieved when testing business continuity plans)*100%
(c): Indicate the total number of tests performed on its IT service recovery plan
(d): (No. of TORs not achieved / Total No. of TORs that should have been achieved when testing the IT service recovery plan)*100%
3) For purposes of this report, the term "continuity test" shall be understood as any type of exercise, test, simulation, among others, carried out in order to verify the operation of business continuity plans.
4) If any test is carried out in which compliance with the TOR is not verified, said test shall not be considered for purposes of the report.
5) In the "Reporting year" column, enter the year with four digits. Likewise, in the "Reporting semester" column, 1 or 2 must be entered, as applicable.
"THIRD.- With respect to the indicator reports established in article 18 of the Regulation, the first submission shall correspond:
1. For entities that are part of a financial conglomerate, to the second quarter of 2020 (in the case of reports RO_r1, RO_r2, SI_r1, CN_r1 and CN_r2), to the first half of 2020 (in the case of reports CN_r3 and CN_r4) and to the 2020 fiscal year (in the case of report SI_r2)
2. For entities that are not part of a financial conglomerate, to the first quarter of 2021 (in the case of reports RO_r1, RO_r2, SI_r1, CN_r1 and CN_r2), to the first half of 2021 (in the case of reports CN_r3 and CN_r4) and to the 2021 fiscal year (in the case of report SI_r2)".
1. For entities that are part of a financial conglomerate: no later than 31 January 2021.
2. For entities that are not part of a financial conglomerate: no later than 31 December 2021.
The other modifications incorporated by this resolution must be implemented in accordance with the following deadlines:
1. For entities that are part of a financial conglomerate: no later than 31 January 2020.
2. For entities that are not part of a financial conglomerate: no later than 31 December 2020.
As long as they do not adapt to the provisions of this article and provided that the indicated deadlines are not exceeded, the entities must continue applying the rules that were in force before the entry into force of this resolution.
Article 10.- These provisions and those of the Operational Risk Management Regulation are not applicable to Risk Rating Companies or Price Providing Companies. The operational risk management obligations applicable to Risk Rating Companies and Price Providing Companies shall be established in their respective regulations.
Article 12.- Publish this resolution in the Official Gazette El Peruano and on the Securities Market Portal of the Superintendency of the Securities Market (www.smv.gob.pe).
Register, communicate and publish.
Signed by: PESCHIERA REBAGLIATI José
Reason:
Date: 26/03/2019 06:31:03 p.m.
José Manuel Peschiera Rebagliati
Superintendent of the Securities Market
Signed by: VARGAS PIÑA Julio Cesar FAU:
Reason:
Signed by: RIVERO ZEVALLOS Carlos Fabian FAU 201:
Reason:
Signed by: RABANAL SOBRINO Alejandro Julio FAU 201 Reason:
Signed by: GIL VASQUEZ Liliana FAU 20131016396 hard Reason:
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.
RegAlert holds no document that amends or replaces this one. This is not a check that it is in force: confirm with the regulator.
“Article 16-B of the Securities Market Law - LMV, approved by Legislative Decree No. 861, establishes that legal persons authorized by the SMV must establish a Risk Management System”
“in accordance with the provisions of subsection a) of Article 1 of the Consolidated Text of the Organic Law of the Superintendency of the Securities Market – SMV (hereinafter, the Organic Law of the SMV), approved by Decree Law No. 26126”
“numeral 2 of Article 9 of the Regulation of Organization and Functions of the SMV, approved by Supreme Decree No. 216-2011-EF”
More like this from SMV
SMV published 22 documents in the last 30 days. We email you each new one the day it's published.
Source: Superintendencia del Mercado de Valores (Peru) — 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