Content library
Cyberday content library
Equipment maintenance and safety

How to fill the requirement

Cyberday content library

Equipment maintenance and safety

Task name
Priority
Status
Theme
Policy
Other requirements
No items found.

Laitteistojen suojaus luvattomia laitteita vastaan (TL II)

Critical
High
Normal
Low

Laitteistot suojataan luvattomien laitteiden (näppäilynauhoittimet, langattomat lähettimet ml. mobiililaitteet ja vastaavat) liittämistä vastaan.

Baseline configuration for systems

Critical
High
Normal
Low

The organization has maintained a basic configuration requirement for IT systems and industrial control systems that takes into account security principles, such as the concept of least functionality.

Ensuring hardware integrity

Critical
High
Normal
Low

The organization must ensure the integrity of its hardware components. This can be done:

  • With hard to copy labels
  • With verifiable serial numbers provided by the developer
  • By requiring the use of anti-tampering technologies
  • Hardware shipments include hardware and firmware upgrades


Identifying the hardware that is connecting to the datacenter

Critical
High
Normal
Low

The organization must use equipment identification as a means of establishing a connection.

Where appropriate, the organization should use location-aware technologies to validate the integrity of authentication based on known device locations.

Documentation of other protected assets

Critical
High
Normal
Low

The organization shall list all relevant protected assets to determine ownership and to ensure that security measures cover all necessary items.

A large portion of the protected assets (including data sets, data systems, personnel / units, and partners) are treated through other tasks. In addition, the organization must list other important assets, which may be, depending on the nature of its operations, e.g. hardware (servers, network equipment, workstations, printers) or infrastructure (real estate, power generation, air conditioning). In addition the organization should make sure that relevant external devices are documented.

Safe placement of equipment

Critical
High
Normal
Low

For example, data processing equipment, as well as other important equipment, should be placed in the premises safely and with consideration. Placement should restrict unauthorized access to devices.

Ensuring the quality of equipment maintenance

Critical
High
Normal
Low

Equipment should be serviced at intervals recommended by the supplier and in accordance with the supplier's specifications.

Basic service testing, fault tolerance evaluation and verification

Critical
High
Normal
Low

The operation of basic services (such as electricity, telecommunications, water supply, sewerage, heating, ventilation and air conditioning) will be monitored to ensure that their capacity covers business growth.

Setting up and resourcing backup equipment

Critical
High
Normal
Low

Organisation must setup and maintain redundant equipment to their ICT environment which can adequately ensure business needs. The equipment should be setup to have the needed resources, capabilities and functions to run the needed operations.

Handling the loss, misuse, damage and theft of assets

Critical
High
Normal
Low

The organization should define policies, processes or technical measures to handle the loss, misuse, damaging and theft of organizational assets. These could include the following:

  • Reporting process
  • Guidelines and manuals
  • Asset and inventory tracking
  • Insurance
  • Regular audits
  • Access control
  • Device hardening
  • Training and awareness programs
  • Mobile device management
  • Data encryption and protection
  • Physical security

Secure usage of maintenance tools and portable devices for organization's systems

Critical
High
Normal
Low

The organization establishes and enforces strict controls over the use of maintenance tools and portable storage devices in the organization's OT/ICS environments. These include:

  • Implementing approval and monitoring processes for maintenance tools such as diagnostic test equipment, packet sniffers, and laptops
  • Ensure that all maintenance equipment and portable devices are inspected upon entry into the facility and protected by anti-malware solutions before being used on critical systems
  • Equipment containing critical system information should be secured and their unauthorized removal prevented

Regular updating and maintenance of hardware

Critical
High
Normal
Low

Organization ensures that all organizational hardware is regularly reviewed for security capabilities and for the need of acquiring patches, updates and or upgrades. Ensure secure handling of hardware during maintenance by restricting access to authorized personnel and implementing controls that prevent tampering or unauthorized access.

In addition plans are defined and implemented for hardware end-of-life, including maintenance support and obsolescence management, ensuring that the outdated hardware does not introduce security risks.

Process for reviewing and approving hardware before deployment

Critical
High
Normal
Low

The organization has a process to review and approve hardware before installation or use. The process includes at least:

  • Verify authenticity: Confirm the authenticity of the hardware, ensuring it comes from trusted and reputable vendors.
  • Assess conformance: Ensure the hardware meets the organization's security standards and technical requirements for use in the specific environment.
  • Check for firmware integrity: Ensure that the hardware’s firmware is genuine, up-to-date, and free from unauthorized modifications.

This process should include special-purpose hardware, such as diagnostic or maintenance tools ensuring they meet security and operational requirements.

Use of surge protectors and uninterruptible power supplies (UPS)

Critical
High
Normal
Low

Surge protectors prevent current level rises and falls from damaging the equipment. Uninterruptible power supplies (UPS), on the other hand, guarantee a limited amount of battery power, which allows you to work even during short power outages. Critical equipment is held in connection to a UPS.

Alarm systems for equipment environment

Critical
High
Normal
Low

Alarm systems monitor the level of key environmental conditions (e.g. temperature and humidity) that can adversely affect the operation of data processing equipment. There should also be a functioning fire alarm system in the environment.

Cabling security

Critical
High
Normal
Low

Power and communication cables that either move data themselves or support data transmission services are protected from damage, eavesdropping and interference.

The safety of cabling should take into account e.g. the following points:

  • communication lines should, as far as possible, be underground or otherwise adequately protected
  • electrical cables should be insulated from telecommunication cables to avoid interference
  • use of armored cables, electromagnetic shielding or technical raking in very critical places

Lightning protection

Critical
High
Normal
Low

All buildings and all incoming power lines and external communication lines are equipped with lightning protection.

Electromagnetic data breach management

Critical
High
Normal
Low

Electronic devices such as cables, monitors, copiers, tablets and smartphones leak electromagnetic radiation, from which it is possible to find out the original transmitted data with the right hardware and, for example, steal the entered username and password.

Openings in the premises' structures (windows, doors, air conditioning) are protected to prevent radiation from escaping. In addition, equipment handling confidential data is located so as to minimize the risk of leakage due to electromagnetic leakage.

Equipment maintenance log

Critical
High
Normal
Low

Maintenance performed on the equipment is recorded in a log, which contains information e.g.:

  • of suspected and happened defects
  • of preventive and remedial actions
  • of checking the equipment after maintenance

Physical switch security

Critical
High
Normal
Low

Identify physical access to switches. It is important to make sure that switches are properly secured and unauthorized parties can't access them.

Universal cyber compliance language model: Comply with confidence and least effort

In Cyberday, all frameworks’ requirements are mapped into universal tasks, so you achieve multi-framework compliance effortlessly.

Security frameworks tend to share the common core. All frameworks cover basic topics like risk management, backup, malware, personnel awareness or access management in their respective sections.
Cyberday’s universal cyber security language technology creates you a single security plan and ensures you implement the common parts of frameworks just once. You focus on implementing your plan, we automate the compliance part - for current and upcoming frameworks.
Start your free trial
1.1 (MIL2): Manage IT and OT Asset Inventory
C2M2: MIL1
1.1 (MIL3): Manage IT and OT Asset Inventory
C2M2: MIL1
1.1.1: Availability of information security policies
TISAX
1.1.1: Identify the organisation’s strategy and priorities
NSM ICT-SP
1.1.2: Identify the organisation’s structures and processes for security management
NSM ICT-SP
1.1.3: Identify the organisation’s processes for ICT risk management
NSM ICT-SP
1.1.4: Identify the organisation’s tolerances for ICT risk
NSM ICT-SP
1.1.5: Identify the organisation’s deliverables, information systems and supporting ICT functions
NSM ICT-SP
1.1.6: Identify information processing and data flow
NSM ICT-SP
1.2 (MIL2): Manage Information Asset Inventory
C2M2: MIL1
1.2 (MIL3): Manage Information Asset Inventory
C2M2: MIL1
1.2.1: Establish a process to identify devices and software in use at the organisation
NSM ICT-SP
1.2.1: Scope of Information Security management
TISAX
1.2.2: Establish organisational guidelines for approved devices and software
NSM ICT-SP
1.2.2: Information Security Responsibilities
TISAX
1.2.3: Identify devices in use at the organisation
NSM ICT-SP
1.2.3: Information Security requirements in projects
TISAX
1.2.4: Definition of responsibilities with service providers
TISAX
1.2.4: Identify the software in use at the organisation
NSM ICT-SP
1.2: Manage Information Asset Inventory
C2M2: MIL1
1.3 (MIL2): Manage IT and OT Asset Configuration
C2M2: MIL1
1.3 (MIL3): Manage IT and OT Asset Configuration
C2M2: MIL1
1.3.1: Identification of information assets
TISAX
1.3.1: Identify the users of the information systems
NSM ICT-SP
1.3.2: Classification of information assets
TISAX
1.3.2: Identify and define the different user categories
NSM ICT-SP
1.3.3: Identify roles and responsibilities linked especially to ICT security
NSM ICT-SP
1.3.3: Use of approved external IT services
TISAX
1.3.4: Use of approved software
TISAX
1.3: Manage IT and OT Asset Configuration
C2M2: MIL1
1.4 (MIL2): Manage Changes to IT and OT Assets
C2M2: MIL1
1.4 (MIL3): Manage Changes to IT and OT Assets
C2M2: MIL1
1.4.1: Management of Information Security Risks
TISAX
1.4: Manage Changes to IT and OT Assets
C2M2: MIL1
1.5 (MIL1): Management Activities for the ASSET domain
C2M2: MIL1
1.5 (MIL2): Management Activities for the ASSET domain
C2M2: MIL1
1.5 (MIL3): Management Activities for the ASSET domain
C2M2: MIL1
1.5.1: Assessment of policies and requirements
TISAX
1.5.2: External review of ISMS
TISAX
1.5: Management Activities for the ASSET domain
C2M2: MIL1
1.6.1: Reporting of security events
TISAX
1.6.2: Management of reported events
TISAX
1.6.3: Crisis preparedness
TISAX
10 §: Johdon vastuu
KyberTL
10. Processing of personal data relating to criminal convictions and offences
GDPR
10.1 (MIL2): Establish Cybersecurity Program Strategy
C2M2: MIL1
10.1 (MIL3): Establish Cybersecurity Program Strategy
C2M2: MIL1
10.1.1: Policy on the use of cryptographic controls
ISO27 Full
10.1.2: Key management
ISO27 Full
10.1.2: Key management
ISO 27017
10.1: Continuous improvement
ISO27k1 Full
10.1: Cryptographic controls
ISO27 Full
10.1: Cryptographic controls
ISO 27017
10.1: Establish Cybersecurity Program Strategy
C2M2: MIL1
10.2 (MIL2): Establish and Maintain Cybersecurity Program
C2M2: MIL1
10.2 (MIL3): Establish and Maintain Cybersecurity Program
C2M2: MIL1
10.2: Establish and Maintain Cybersecurity Program
C2M2: MIL1
10.2: Non-conformity and corrective action
ISO27k1 Full
10.3 (MIL1): Management Activities for the PROGRAM domain
C2M2: MIL1
10.3 (MIL2): Management Activities for the PROGRAM domain
C2M2: MIL1
10.3 (MIL3): Management Activities for the PROGRAM domain
C2M2: MIL1
10.3: Management Activities for the PROGRAM domain
C2M2: MIL1
10: Cryptography
ISO27 Full
10: Cryptography
ISO 27017
10: Cybersecurity Program Management (PROGRAM)
C2M2: MIL1
10: Prosessi väärinkäytöksiin reagoimiseksi
Sec overview
11 §: Poikkeamailmoitukset viranomaiselle
KyberTL
11. Processing which does not require identification
GDPR
11.1.1: Physical security perimeter
ISO27 Full
11.1.2: Physical entry controls
ISO27 Full
11.1.3: Securing offices, rooms and facilities
ISO27 Full
11.1.4: Protecting against external and environmental threats
ISO27 Full
11.1.5: Working in secure areas
ISO27 Full
11.1.6: Delivery and loading areas
ISO27 Full
11.1: Secure areas
ISO27 Full
11.2.1: Equipment siting and protection
ISO27 Full
11.2.2: Supporting utilities
ISO27 Full
11.2.3: Cabling security
ISO27 Full
11.2.4: Equipment maintenance
ISO27 Full
11.2.5: Removal of assets
ISO27 Full
11.2.6: Security of equipment and assets off-premises
ISO27 Full
11.2.7: Secure disposal or re-use of equipment
ISO27 Full
11.2.7: Secure disposal or re-use of equipment
ISO 27017
11.2.8: Unattended user equipment
ISO27 Full
11.2.9: Clear desk and clear screen policy
ISO27 Full
11.2: Equipment
ISO27 Full
11.2: Equipment
ISO 27017
11: Digiturvan mittarien määrittäminen
Sec overview
11: Physical and environmental security
ISO27 Full
11: Physical and environmental security
ISO 27017
12 §: Luotettavuutta edellyttävien tehtävien tunnistaminen ja luotettavuudesta varmistuminen
TiHL
12 §: Poikkeamaa koskeva väliraportti
KyberTL
12. Transparent information, communication and modalities for the exercise of the rights of the data subject
GDPR
12.1.1: Documented operating procedures
ISO27 Full
12.1.2: Change management
ISO27 Full
12.1.3: Capacity management
ISO27 Full
12.1.4: Separation of development, testing and operational environments
ISO27 Full
12.1: Operational procedures and responsibilities
ISO27 Full
12.2.1: Controls against malware
ISO27 Full
12.2: Protection from malware
ISO27 Full