8
No.
Area and measures
Description
1
Keep operating
systems and
applications updated
All software, including operating systems, applications and firmware
on clients, mobile devices, servers, network equipment, etc. must
be updated when new versions or security updates are released
from the supplier. The update must follow a fixed process that helps
ensure that potential compatibility issues or inadequacies are
uncovered before the update is transferred to the production
environment. Deadlines are set as to how fast security updates
should be commissioned after their release.
2
Segment networks
and limit traffic
between segments
The organization’s internal networks should be physically or logically
divided into network segments, allowing a unit (clients, mobile
devices, servers or network equipment) to be placed in a segment in
accordance with its use and sensitivity.
The network traffic between individual network segments must be
limited to only that which is required and, if possible, be protected
and monitored.
3
Protect clients with
antivirus
programmes and
firewalls
All clients must be protected by an antivirus solutions and a locally
installed firewall.
4
Control user
accounts and rights
Creation, use and closure of user accounts must take place based on
a senior management approved process. The granting of rights,
including privileged rights, must only take place based on workrelated requirements. These rights must be continuously reviewed,
updated and approved in relation to potential changes in roles and
responsibility.
Privileged rights to clients, applications and systems must be
granted on a “need to have” basis.
5
Use secure
passwords and multifactor authentication
6
Conduct backup of
data and
configurations and
test recovery
Backup of data from business critical IT systems must be conducted.
Backup must always be conducted in accordance with organization
policies that consider the consequences to an organization if data in
the production environment is lost. Configurations and systems,
which are necessary to recover following a major security incident,
must also be included in the backup. Regular testing must be
undertaken to ensure that the backup contents are complete and
that data and configurations can be loaded from backup. A copy
must be kept offline.
7
Establish logging of
anomalies and
security incidents
Logging of key systems must be enabled, including successful and
failed login attempts. Logging of configuration changes and access
to sensitive data or systems must also be logged. Logs should be
kept separately and with limited access and be regularly reviewed.
Logs must be kept for an adequate period of time.
8
Protect remote
access to systems
Remote access to organization systems must be protected with
multi-factor authentication. The integrity of the communication must
be protected by encryption, for example by use of HTTPS or a VPN
service.
9
Encrypt data on
clients and mobile
devices as well as
communication over
other networks
Data on clients and in particular portable clients used outside the
organization must be protected by full disk encryption. Similarly,
data on mobile devices should be protected with encryption and
possibly administered at an MDM (Mobil Device Management)
platform, which also allows remote deletion. All communication with
organization systems over other networks outside organizational
control must be encrypted.
10
Compile a list of
approved
applications
(whitelisting)
Installation and closure of applications on organization clients must
be limited to the pre-approved applications authorized for use in the
organization.
Access to any account must be protected by use of secure
passwords and, if possible, be supplemented with multi-factor
authentication.
Access to accounts with privileged rights must be protected with
multi-factor authentication, including accounts that are used in
connection with remote access to organization systems.
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents