+17. pants 2.
|
17. pants 2.
Pēc būtisku izmaiņu ieviešanas savās IKT sistēmas centrālie darījumu partneri un centrālie vērtspapīru depozitāriji pakļauj savas IKT sistēmas stingrai testēšanai, kurā simulē stresa apstākļus. Centrālie darījumu partneri pirmajā daļā minētajā testēšanas plānošanā un veikšanā pēc vajadzības iesaista:
a)
tīrvērtes dalībniekus un klientus;
b)
sadarbspējīgus centrālos darījumu partnerus;
c)
citas ieinteresētās personas.
Centrālie vērtspapīru depozitāriji pirmajā daļā minētajā testēšanas plānošanā un veikšanā pēc vajadzības iesaista:
b)
kritiski svarīgus sabiedrisko pakalpojumu sniedzējus un kritiski svarīgus pakalpojumu sniedzējus;
c)
citus centrālos vērtspapīru depozitārijus;
d)
citas tirgus infrastruktūras;
e)
jebkuras citas iestādes, ar kurām centrālajiem vērtspapīru depozitārijiem ir identificēta savstarpējā atkarība to IKT darbības nepārtrauktības politikā.
1. Pārskats
1.1 Atsauces
1.2 Identificētās prasības
1.3 Saistītie standarti
2. Identificētās prasības
3. Saistītie standarti
Standarti
| Avots |
Prasība |
|
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.
|
|