2.3.6: Ensure that maintenance of all configurations, installations and operations are done securely

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

Ensure that maintenance of all configurations, installations and operations are done securely.
a) Perform management operations in trusted channels. Consider i) installing trusted TLS certificates, ideally issued internally, in as many administrator interfaces as possible, see 2.7.1. and 2.7.2. And ii) avoid exposing administrator interfaces to the internet and to the servers/clients using the service. b) Use trusted and dedicated clients for management operations. c) Reduce interactive log-ins directly on servers and clients to a minimum when performing management operations. Interactive log-in increases the risk (attacks such as “pass the hash”) and goes against the goal of automating and standardising configuration, and also against the goal of automated verification of the configuration.

This requirement is part of the framework:  
NSM ICT Security Principles (Norway)
Best practices
How to implement:
2.3.6: Ensure that maintenance of all configurations, installations and operations are done securely
This policy on
2.3.6: Ensure that maintenance of all configurations, installations and operations are done securely
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.

Ensure that maintenance of all configurations, installations and operations are done securely.
a) Perform management operations in trusted channels. Consider i) installing trusted TLS certificates, ideally issued internally, in as many administrator interfaces as possible, see 2.7.1. and 2.7.2. And ii) avoid exposing administrator interfaces to the internet and to the servers/clients using the service. b) Use trusted and dedicated clients for management operations. c) Reduce interactive log-ins directly on servers and clients to a minimum when performing management operations. Interactive log-in increases the risk (attacks such as “pass the hash”) and goes against the goal of automating and standardising configuration, and also against the goal of automated verification of the configuration.

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.6: Ensure that maintenance of all configurations, installations and operations are done securely
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.6: Ensure that maintenance of all configurations, installations and operations are done securely
of the framework  
NSM ICT Security Principles (Norway)
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
Ensure that maintenance of configurations, installations and operations are done securely
Critical
High
Normal
Low
1
requirements
Technical cyber security
Network security

Ensure that maintenance of configurations, installations and operations are done securely

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.