Article 37: ICT systems acquisition, development, and maintenance

Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.

The financial entities referred to in Article 16(1) of Regulation (EU) 2022/2554 shall design and implement, where appropriate, a procedure governing the acquisition, development, and maintenance of ICT systems following a risk-based approach. That procedure shall:

(a) ensure that, before any acquisition or development of ICT systems takes place, the functional and non-functional requirements, including information security requirements, are clearly specified and approved by the business function concerned;

(b) ensure the testing and approval of ICT systems prior to their first use and before introducing changes to the production environment;

(c) identify measures to mitigate the risk of unintentional alteration or intentional manipulation of the ICT systems during development and implementation in the production environment.

This requirement is part of the framework:  
DORA simplified RMF

Other requirements of the framework

34729
Article 37: ICT systems acquisition, development, and maintenance
Best practices
How to implement:
Article 37: ICT systems acquisition, development, and maintenance
This policy on
Article 37: ICT systems acquisition, development, and maintenance
provides a set concrete tasks you can complete to secure this topic. Follow these best practices to ensure compliance and strengthen your overall security posture.

The financial entities referred to in Article 16(1) of Regulation (EU) 2022/2554 shall design and implement, where appropriate, a procedure governing the acquisition, development, and maintenance of ICT systems following a risk-based approach. That procedure shall:

(a) ensure that, before any acquisition or development of ICT systems takes place, the functional and non-functional requirements, including information security requirements, are clearly specified and approved by the business function concerned;

(b) ensure the testing and approval of ICT systems prior to their first use and before introducing changes to the production environment;

(c) identify measures to mitigate the risk of unintentional alteration or intentional manipulation of the ICT systems during development and implementation in the production environment.

Read below what concrete actions you can take to improve this ->
Frameworks that include requirements for this topic:
No items found.

How to improve security around this topic

In Cyberday, requirements and controls are mapped to universal tasks. A set of tasks in the same topic create a Policy, such as this one.

Here's a list of tasks that help you improve your information and cyber security related to
Article 37: ICT systems acquisition, development, and maintenance
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
No other tasks found.

How to comply with this requirement

In Cyberday, requirements and controls are mapped to universal tasks. Each requirement is fulfilled with one or multiple tasks.

Here's a list of tasks that help you comply with the requirement
Article 37: ICT systems acquisition, development, and maintenance
of the framework  
DORA simplified RMF
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
Approval process before deploying new software
Critical
High
Normal
Low
3
requirements
System management
Data system management

Approval process before deploying new software

This task helps you comply with the following requirements

Testing of new systems before deployment
Critical
High
Normal
Low
1
requirements
System management
Data system procurement

Testing of new systems before deployment

This task helps you comply with the following requirements

Security rules for the development and acquisition of data systems
Critical
High
Normal
Low

The ISMS component hierachy

When building an ISMS, it's important to understand the different levels of information hierarchy. Here's how Cyberday is structured.

Framework

Sets the overall compliance standard or regulation your organization needs to follow.

Requirements

Break down the framework into specific obligations that must be met.

Tasks

Concrete actions and activities your team carries out to satisfy each requirement.

Policies

Documented rules and practices that are created and maintained as a result of completing tasks.

Never duplicate effort. Do it once - improve compliance across frameworks.

Reach multi-framework compliance in the simplest possible way
Security frameworks tend to share the same core requirements - like risk management, backup, malware, personnel awareness or access management.
Cyberday maps all frameworks’ requirements into shared tasks - one single plan that improves all frameworks’ compliance.
Do it once - we automatically apply it to all current and future frameworks.