NSM ICT Security Principles (Norway)

Requirement

2.1.1: Include security in the organisation’s procurement process

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

Include security in the organisation’s procurement process. Determine ICT security specifications when procuring any type of ICT product or service, see principle 2.2 – Establish a secure ICT architecture. Include life cycle security from procurement to disposal.

Fulfill this requirement by completing the tasks below ->

This requirement is part of the framework:

NSM ICT Security Principles (Norway)

Other requirements of the framework

2.1.1: Include security in the organisation’s procurement process

Best practices

How to implement:

2.1.1: Include security in the organisation’s procurement process

This policy on

2.1.1: Include security in the organisation’s procurement process

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.

Include security in the organisation’s procurement process. Determine ICT security specifications when procuring any type of ICT product or service, see principle 2.2 – Establish a secure ICT architecture. Include life cycle security from procurement to disposal.

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.1: Include security in the organisation’s procurement process

Task name

Priority

Task completes

Complete these tasks to increase your compliance in this policy.

Critical

No other tasks found.

Complete these tasks in Cyberday ISMS ->

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.1: Include security in the organisation’s procurement process

of the framework

NSM ICT Security Principles (Norway)

Task name

Priority

Task completes

Complete these tasks to increase your compliance in this policy.

Critical

General rules for the procurement of data systems

Critical

High

Normal

Low

System management

Data system procurement

General rules for the procurement of data systems

This task helps you comply with the following requirements

Članak 30.1.e: Sigurnost u nabavi, razvoju i održavanju mrežnih i informacijskih sustava NIS2 Croatia

4.2: Tietojärjestelmien hankinnat TiHL tietoturvavaatimukset

9.3 §: Tietojärjestelmien hankinta ja kehittäminen Kyberturvallisuuslaki

5.3.1: Information Security in new systems TISAX

13 §: Tietoaineistojen ja tietojärjestelmien tietoturvallisuus TiHL

Security rules for the development and acquisition of data systems

Critical

High

Normal

Low

System management

Data system procurement

Security rules for the development and acquisition of data systems

This task helps you comply with the following requirements

Članak 30.1.e: Sigurnost u nabavi, razvoju i održavanju mrežnih i informacijskih sustava NIS2 Croatia

4.2: Tietojärjestelmien hankinnat TiHL tietoturvavaatimukset

9.3 §: Tietojärjestelmien hankinta ja kehittäminen Kyberturvallisuuslaki

5.3.1: Information Security in new systems TISAX

13 §: Tietoaineistojen ja tietojärjestelmien tietoturvallisuus TiHL

Requiring a system description from suppliers of important information systems to be acquired

Critical

High

Normal

Low

System management

Data system procurement

Requiring a system description from suppliers of important information systems to be acquired

This task helps you comply with the following requirements

Članak 30.1.e: Sigurnost u nabavi, razvoju i održavanju mrežnih i informacijskih sustava NIS2 Croatia

30 § 3.5°: L'acquisition, du développement et de la maintenance des réseaux et des systèmes d'information NIS2 Belgium

2.1.10: Review the service provider’s security when outsourcing NSM ICT-SP

2.1.1: Include security in the organisation’s procurement process NSM ICT-SP

14.5.6): Tinklų ir informacinių sistemų saugumą NIS2 Lithuania

Complete these tasks in Cyberday ISMS ->

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.

Start free trial