|
+INF.13.A12 Secure Configuration of TBM Systems (S) |
INF.13.A12 Secure Configuration of TBM Systems (S)All systems in TBM and systems operated by TBM SHOULD be configured securely. At minimum, these configurations SHOULD be tested before a system is put into operation. Configuration changes during productive operations SHOULD be tested on a test instance before activation or only carried out according to the principle of dual control. The configuration of systems SHOULD be backed up to enable quick re-installation of an error-free version (rollback). Rollback tests SHOULD be set up on a test system or performed during maintenance windows. The configurations SHOULD be stored centrally. Automated distribution of software updates and configurations SHOULD be set up for similar systems, including devices at the automation and field level (see section 4.1, TBM-Specific Terminology Used). Configuration changes SHOULD be made known to all the parties involved in operational and service processes (fault clearance, on-call service, maintenance, etc). In particular, these include:
In the event of a malfunction, it SHOULD be ensured that a maintenance technician can operate or parameterise the system affected (for example). Furthermore, whether systems are configured according to the corresponding specifications SHOULD be checked both regularly and whenever required. The results SHOULD be documented in a transparent manner. Deviations from the specifications SHOULD be corrected. 1. Übersicht
1.1 Referenzen1.2 Identifizierte Anforderungen1.3 Zugehörige Regulierungen2. Identifizierte Anforderungen
3. Zugehörige Regulierungen
Verknüpfte Vorgänge
|