2.3.10: Reduce the risk posed by IoT devices

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

Reduce the risk posed by IoT devices. a) Create a plan for deploying such devices to include security aspects with risk assessments, incl. an assessment of the cloud the devices connect to. b) Only purchase devices with built-in security functions, e.g. which i) provide security updates (2.3.1), ii) are able to change all standard passwords (2.3.7), iii) can be forced to only use networks the organisation has control over. c) Monitor traffic from the devices (see principle 3.2 – Establish security monitoring), d) isolate the devices in separate network zones (see principles 2.2 – Establish a secure ICT architecture and 2.5 – Control data flow) and e) consider their location with regard to unauthorised physical access to the devices.

Best practices
How to implement:
2.3.10: Reduce the risk posed by IoT devices
This policy on
2.3.10: Reduce the risk posed by IoT devices
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.

Reduce the risk posed by IoT devices. a) Create a plan for deploying such devices to include security aspects with risk assessments, incl. an assessment of the cloud the devices connect to. b) Only purchase devices with built-in security functions, e.g. which i) provide security updates (2.3.1), ii) are able to change all standard passwords (2.3.7), iii) can be forced to only use networks the organisation has control over. c) Monitor traffic from the devices (see principle 3.2 – Establish security monitoring), d) isolate the devices in separate network zones (see principles 2.2 – Establish a secure ICT architecture and 2.5 – Control data flow) and e) consider their location with regard to unauthorised physical access to the devices.

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.3.10: Reduce the risk posed by IoT devices
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.3.10: Reduce the risk posed by IoT devices
of the framework  
NSM ICT Security Principles (Norway)
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
Secure deployment of IoT devices
Critical
High
Normal
Low
1
requirements
Technical cyber security
Network security

Secure deployment of IoT devices

This task helps you comply with the following requirements

General rules for the acquisition of IoT devices
Critical
High
Normal
Low
1
requirements
System management
Data system procurement

General rules for the acquisition of IoT devices

This task helps you comply with the following requirements

Network usage log and process for detecting inappropriate network traffic
Critical
High
Normal
Low
28
requirements
Technical cyber security
Network security

Network usage log and process for detecting inappropriate network traffic

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.