Include backups of software to ensure recovery

Organization must be able to monitor that devices, data systems and networks are maintained in accordance with the defined configurations (including security features) both during the implementation phase and throughout their entire life cycle.

For this, the organization has defined standard templates for secure configurations of devices, data systems and networks. When specifying standard templates, the following are taken into account:

• publicly available guidelines (e.g. templates from suppliers and independent security organizations)
• the level of protection required for different assets
• fulfilling related information security requirements
• feasibility and applicability of the configurations to the organization's operations

Standard templates should be checked regularly and updated when significant new threats or vulnerabilities need to be responded to or new software or hardware versions are released.

The following points should be taken into account when defining standard templates:

• the number of root-level rights is minimized
• unnecessary access rights are disabled
• unnecessary functions and services are deactivated
• access to powerful utilities and important settings is strictly controlled
• the clocks are synchronized
• the supplier's default passwords are changed immediately and the security-related settings are checked
• timeout functions are used if necessary (e.g. automatic logout)
• license requirements are met

Backup master images of operating systems and installation software to ensure recovery capabilities from a software perspective.

The organization must have clear policies for developing virtualization security. The policy should be reviewed and updated at least annually.

The virtualization policy should consider at least:

• Virtual Machine Lifecycle Management
• Limiting the storage of virtual machine icons and snapshots
< li>Backup and fault tolerance
• Labeling virtual machines by risk level
• Change management process for creating, storing, and using virtual machine icons
• Using firewalls to separate virtual machine groups