2.1.5: Use a secure software development method

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

Use a secure software development method in order to reduce vulnerabilities in the software. This includes: a) Adequate planning, including the organisation’s needs, legal conditions, ICT security considerations and the need to train personnel. b) Analysis of user needs, including ICT security requirements. c) Design of the software according to requirements. d) Development of the software, including secure coding and testing (see 2.1.6 and 2.1.7). e) Deployment of the software. f) Secure management of the software, including i) planning for performing and distributing security updates, and ii) planning support for newer and more recent security functionality.

Best practices
How to implement:
2.1.5: Use a secure software development method
This policy on
2.1.5: Use a secure software development method
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.

Use a secure software development method in order to reduce vulnerabilities in the software. This includes: a) Adequate planning, including the organisation’s needs, legal conditions, ICT security considerations and the need to train personnel. b) Analysis of user needs, including ICT security requirements. c) Design of the software according to requirements. d) Development of the software, including secure coding and testing (see 2.1.6 and 2.1.7). e) Deployment of the software. f) Secure management of the software, including i) planning for performing and distributing security updates, and ii) planning support for newer and more recent security functionality.

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
2.1.5: Use a secure software development method
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
2.1.5: Use a secure software development method
of the framework  
NSM ICT Security Principles (Norway)
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
Designing Secure Software Development Life Cycle(SSDLC) process
Critical
High
Normal
Low
Automated secure code deployment and release
Critical
High
Normal
Low
3
requirements
Development and cloud
Secure development

Automated secure code deployment and release

This task helps you comply with the following requirements

Built in and default cyber security in system development (Security by design)
Critical
High
Normal
Low
5
requirements
Development and cloud
Secure development

Built in and default cyber security in system development (Security by design)

This task helps you comply with the following requirements

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.