IND.2.1 General ICS Components

Passwords set by default or by the manufacturer MUST be changed (see ORP.4 Identity and Access Management). These changes MUST be documented. Passwords MUST be stored securely.

It MUST be ensured that only authorised employees are allowed to access the configuration and maintenance interfaces of ICS components. The configuration of an ICS component MUST ONLY be changed after the approval or authentication of the person in charge.

Secure protocols MUST be implemented for configuring and maintaining ICS components. Information MUST be protected during transmission.

All services, features, and interfaces of ICS components that are not being used MUST be disabled or uninstalled.

ICS components MUST be separated from office IT. If ICS components depend on other components in the network in question, this SHOULD be documented sufficiently. ICS components SHOULD communicate as little as possible with other ICS components.

Backups MUST be created prior to each system change in an ICS component.

ICS components SHOULD be protected against malware by suitable mechanisms (see OPS.1.1.4 Protection Against Malware). If an anti-virus protection program is used in this regard, the program and the virus signatures approved by the manufacturer SHOULD always be up to date.

If the resources on the ICS component are not sufficient or real-time requests could be endangered by the use of anti-virus protection programs, alternative safeguards (such as the isolation of the ICS component or the production network) SHOULD be implemented.

The latest approved security updates SHOULD always be installed when maintaining an ICS component. Updates for the respective operating system SHOULD only be installed following approval by the manufacturer of a given ICS component. Alternatively, updates SHOULD be checked in a test environment before they are used in a productive ICS component. Maintenance SHOULD be performed on short notice for critical security updates.

Before they are commissioned, ICS components SHOULD correspond to the latest internally approved firmware, software, and patch status.

New ICS components SHOULD be integrated into existing operating, monitoring, and information security management processes.

Externally accessible interfaces SHOULD be protected against misuse.

Measurement or control data SHOULD be protected against unauthorised access or changes during transmission. Whether this is necessary or feasible SHOULD be checked in situations involving applications with real-time requirements. If measurement or control data is transmitted using public networks, it SHOULD be protected appropriately.

There SHOULD be alternative and independent communication options that an organisation can use to maintain its ability to function in the event of malfunctions.

Regular security tests SHOULD be carried out to check whether the technical security safeguards in place are still implemented efficiently. The security tests SHOULD NOT be carried out while the system is running. Such tests SHOULD be scheduled for maintenance periods. The results SHOULD be documented. Identified risks SHOULD be evaluated and addressed.

Firmware updates or new control programs SHOULD ONLY be installed after their integrity has been checked. They SHOULD only come from trusted sources.