NSM ICT Security Principles (Norway)

Requirement

1.2.4: Identify the software in use at the organisation

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

Identify the software in use at the organisation in accordance with the process described in 1.2.1. a) Identify firmware, operating system and applications (name, version number, manufacturer, installation date, whether it is still supported) installed on servers, clients and network equipment etc. b) Create a plan for how to approve software for use at the organisation (see 1.2.2). The process described above can be simplified by being consistent in allowlisting all applications (especially clients) (alternatively the use of app stores). Systematic use of application allowlists (or app stores) can make it easier to maintain an inventory of software in use. This is particularly relevant for end user clients.

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

1.2.4: Identify the software in use at the organisation

Best practices

How to implement:

1.2.4: Identify the software in use at the organisation

This policy on

1.2.4: Identify the software in use at the organisation

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.

Identify the software in use at the organisation in accordance with the process described in 1.2.1. a) Identify firmware, operating system and applications (name, version number, manufacturer, installation date, whether it is still supported) installed on servers, clients and network equipment etc. b) Create a plan for how to approve software for use at the organisation (see 1.2.2). The process described above can be simplified by being consistent in allowlisting all applications (especially clients) (alternatively the use of app stores). Systematic use of application allowlists (or app stores) can make it easier to maintain an inventory of software in use. This is particularly relevant for end user clients.

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

1.2.4: Identify the software in use at the organisation

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

1.2.4: Identify the software in use at the organisation

of the framework

NSM ICT Security Principles (Norway)

Task name

Priority

Task completes

Complete these tasks to increase your compliance in this policy.

Critical

Authorized users and rules for installing software and libraries

Critical

High

Normal

Low

Development and cloud

Technical vulnerability management

Authorized users and rules for installing software and libraries

This task helps you comply with the following requirements

12.6.2: Restrictions on software installation ISO 27001

SUM-02: Keeping licensed software up to date Cyber Essentials

DE.CM-5: Unauthorized mobile code detection NIST

TEK-17: Muutoshallintamenettelyt Julkri

8.19: Installation of software on operational systems ISO 27001

Whitelisting

Critical

High

Normal

Low

Technical cyber security

Malware protection

Whitelisting

This task helps you comply with the following requirements

MWP-05: Whitelisting Cyber Essentials

MWP: Application allow listing Cyber Essentials

1.2.2: Establish organisational guidelines for approved devices and software NSM ICT-SP

1.2.4: Identify the software in use at the organisation NSM ICT-SP

2.3.2: Configure clients so that only software known to the organisation is able to execute NSM ICT-SP

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