2.3.4: Establish and maintain standard security configurations

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

Establish and maintain standard security configurations, ideally one template for each type of device across the organisation. This applies to operating systems (client and server), firewalls, network equipment, applications and hardware. a) All management of security configurations should be centralised and standardised for each type of device. b) The configuration should be reviewed and updated regularly to eliminate the latest vulnerabilities and attack vectors. c) Changes to the configuration should follow the organisation’s process for change management and be overseen by authorised staff. d) Security configurations must only be changed by authorised operating staff and not be able to be changed by end users on their clients.

Best practices
How to implement:
2.3.4: Establish and maintain standard security configurations
This policy on
2.3.4: Establish and maintain standard security configurations
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.

Establish and maintain standard security configurations, ideally one template for each type of device across the organisation. This applies to operating systems (client and server), firewalls, network equipment, applications and hardware. a) All management of security configurations should be centralised and standardised for each type of device. b) The configuration should be reviewed and updated regularly to eliminate the latest vulnerabilities and attack vectors. c) Changes to the configuration should follow the organisation’s process for change management and be overseen by authorised staff. d) Security configurations must only be changed by authorised operating staff and not be able to be changed by end users on their 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
2.3.4: Establish and maintain standard security configurations
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.4: Establish and maintain standard security configurations
of the framework  
NSM ICT Security Principles (Norway)
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
Defining standard templates for secure configurations
Critical
High
Normal
Low

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.