PR.IP-2: A System Development Life Cycle to manage systems is implemented.

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

The system and application development life cycle shall include security considerations.
Guidance
- System and application development life cycle should include the acquisition process of the
organization's business critical systems and its components.
- Vulnerability awareness and prevention training for (web application) developers, and advanced
social engineering awareness training for high-profile roles should be considered.
- When hosting internet facing applications the implementation of a web application firewall (WAF)
should be considered.

The development process for critical systems and system components shall cover the full
design cycle and shall provide a description of the functional properties of security controls,
and design and implementation information for security-relevant system interfaces.
Guidance
The development cycle includes:
- All development phases: specification , design, development, implementation.
- Configuration management for planned and unplanned changes and change control during the
development.
- Flaw tracking & resolution.
- Security testing.

Best practices
How to implement:
PR.IP-2: A System Development Life Cycle to manage systems is implemented.

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

The system and application development life cycle shall include security considerations.
Guidance
- System and application development life cycle should include the acquisition process of the
organization's business critical systems and its components.
- Vulnerability awareness and prevention training for (web application) developers, and advanced
social engineering awareness training for high-profile roles should be considered.
- When hosting internet facing applications the implementation of a web application firewall (WAF)
should be considered.

The development process for critical systems and system components shall cover the full
design cycle and shall provide a description of the functional properties of security controls,
and design and implementation information for security-relevant system interfaces.
Guidance
The development cycle includes:
- All development phases: specification , design, development, implementation.
- Configuration management for planned and unplanned changes and change control during the
development.
- Flaw tracking & resolution.
- Security testing.

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
PR.IP-2: A System Development Life Cycle to manage systems is implemented.
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
PR.IP-2: A System Development Life Cycle to manage systems is implemented.
of the framework  
CyberFundamentals (Belgium)
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical

The ISMS component hierachy

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.