+RTS ICT Risk Management T. II Ch. I Sec. 7 Art. 17 , 2
|
1. Overview
RTS ICT Risk Management T. II Ch. I Sec. 7 Art. 17 , 2
2. After having made significant changes to their ICT systems, central counterparties and central securities depositories shall submit their ICT systems to stringent testing by simulating stressed conditions. Central counterparties shall involve, as appropriate, in the design and conduct of the testing referred to in the first subparagraph:
- (a) clearing members and clients;
- (b) interoperable central counterparties;
- (c) other interested parties,
Central securities depositories shall, as appropriate, involve in the design and conduct of the testing referred to in the first subparagraph:
- (a) users;
- (b) critical utilities and critical service providers;
- (c) other central securities depositories;
- (d) other market infrastructures;
- (e) any other institutions with which central securities depositories have identified interdependencies in their ICT
business continuity policy.
1.1 References
1.2 Identified Requirements
1.3 Related Standards
2. Identified Requirements
Requirements
| Source |
Requirement |
3. Related Standards
Standards
| Source |
Requirement |
|
NOREA
|
Change Procedures
Ensure that all changes to software, hardware, firmware components, and systems, along with security parameters, are appropriately placed and scoped. Document and communicate change details, including the purpose and scope of the change, the implementation timeline, and expected outcomes. Define clear roles and responsibilities to ensure that changes are defined, planned, transitioned, tested, and finalized in a controlled manner. Additionally, establish effective quality assurance procedures. Implement mechanisms to maintain independence between the functions that approve changes and those responsible for requesting and implementing them.
|
|
NOREA
|
Security Requirements
Identify the potential impact of a change on existing security measures and assess whether additional security measures are required for its implementation. Verify that security requirements have been met for all implemented changes. Establish fallback procedures and assign responsibilities for aborting changes or recovering from changes not successfully implemented.
|
|
NOREA
|
Emergency Change Management
Define procedures for documenting, reevaluating, assessing, and approving the implementation of emergency changes, including workarounds and patches.
|
|
NOREA
|
OTAP Implementation
Ensure segregation of production environments from development, testing, and other non-production environments, encompassing all components of an environment. This also includes requirements to conduct the development and testing in production environments. Ensure that the instances in which testing is performed in production environment are clearly identified, justified, for limited periods of time approved by the relevant function.
|
|