Content library
C2M2: MIL1
ASSET-1: Manage IT and OT Asset Inventory

Requirement description

MIL1 requirements
a. IT and OT assets that are important to the delivery of the function are inventoried, at least in an ad hoc manner

MIL2 requirements
b. The IT and OT asset inventory includes assets within the function that may be leveraged to achieve a threat objective
c. Inventoried IT and OT assets are prioritized based on defined criteria that include importance to the delivery of the function
d. Prioritization criteria include consideration of the degree to which an asset within the function may be leveraged to achieve a threat objective
e. The IT and OT inventory includes attributes that support cybersecurity activities (for example, location, asset priority, asset owner, operating system, and firmware versions)

MIL3 requirements
f. The IT and OT asset inventory is complete (the inventory includes all assets within the function)
g. The IT and OT asset inventory is current, that is, it is updated periodically and according to defined triggers, such as system changes
h. Data is destroyed or securely removed from IT and OT assets prior to redeployment and at end of life

How to fill the requirement

C2M2: MIL1

ASSET-1: Manage IT and OT Asset Inventory

Task name
Priority
Status
Theme
Policy
Other requirements
Data system listing and owner assignment
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
System management
Data system management
55
requirements

Examples of other requirements this task affects

Članak 30.1.i (Imovina): Upravljanja programskom i sklopovskom imovinom
NIS2 Croatia
4.1: Tietojärjestelmien tietoturvallisuus
TiHL tietoturvavaatimukset
2.5: Riskienhallinta
TiHL tietoturvavaatimukset
9.5 §: Suojattavan omaisuuden hallinta
Kyberturvallisuuslaki
1.3.1: Identification of information assets
TISAX
See all related requirements and other information from tasks own page.
Go to >
Data system listing and owner assignment
1. Task description

Organisation must maintain a listing of used data systems and their owners. Owner is responsible for completing the related documentation and possible other security actions directly related to the data system.

Data system documentation must include at least:

  • System purpose and linked responsibilities
  • System's data location (covered in a separate task)
  • System's maintenance and development responsibilities and linked partners (covered in a separate task)
  • When necessary system's access roles and authentication methods (covered in a separate task)
  • When necessary systems interfaces to other systems (covered in a separate task)
Data store listing and owner assignment
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Privacy
Processing principles and accountability
44
requirements

Examples of other requirements this task affects

Članak 30.1.i (Imovina): Upravljanja programskom i sklopovskom imovinom
NIS2 Croatia
9.5 §: Suojattavan omaisuuden hallinta
Kyberturvallisuuslaki
9.3.1: Data processing activities management
TISAX
1.3.1: Identification of information assets
TISAX
9.5.1: Management of data transfer
TISAX
See all related requirements and other information from tasks own page.
Go to >
Data store listing and owner assignment
1. Task description

Organisation must maintain a listing of controlled data stores and their owners. Owner is responsible for completing the documentation and other possible security actions directly related to the data store.

Data store documentation must include at least:

  • Connected responsibilities
  • Data processing purposes (covered in a separate task)
  • Data sets included in the data store (covered in a separate task)
  • Data disclosures (covered in a separate task)
  • When necessary, data stores connections to action processes
Documentation of data sets for data stores
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Management of data sets
Management of data sets
48
requirements

Examples of other requirements this task affects

Članak 30.1.i (Imovina): Upravljanja programskom i sklopovskom imovinom
NIS2 Croatia
2.4: Luokittelu ja turvallisuusluokittelu
TiHL tietoturvavaatimukset
3.1: Tietoaineistojen tietoturvallisuus
TiHL tietoturvavaatimukset
2.5: Riskienhallinta
TiHL tietoturvavaatimukset
9.5 §: Suojattavan omaisuuden hallinta
Kyberturvallisuuslaki
See all related requirements and other information from tasks own page.
Go to >
Documentation of data sets for data stores
1. Task description

The organization shall maintain a list of data sets contained in the data stores it manages.

The documentation shall include at least the following information:

  • Data systems and other means used to process the data sets
  • Key categories of data in the data set (and whether it contains personal data)
  • Data retention period (discussed in more detail in a separate task)
  • Information on archiving / disposal of data (discussed in more detail in a separate task)
Documentation of other protected assets
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Physical security
Equipment maintenance and safety
31
requirements

Examples of other requirements this task affects

Članak 30.1.i (Imovina): Upravljanja programskom i sklopovskom imovinom
NIS2 Croatia
9.5 §: Suojattavan omaisuuden hallinta
Kyberturvallisuuslaki
9.12 §: Fyysinen turvallisuus
Kyberturvallisuuslaki
5.2.7: Network management
TISAX
3.1.3: Management of supporting assets
TISAX
See all related requirements and other information from tasks own page.
Go to >
Documentation of other protected assets
1. Task description

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.

Applying original security measures to copies and translations
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Physical security
Non-electronic data and copies
3
requirements

Examples of other requirements this task affects

FYY-09: Tietojen kopioiminen
Julkri
ASSET-1: Manage IT and OT Asset Inventory
C2M2
F-08.2: TURVALLISUUSLUOKITELTUJEN TIETOJEN KOPIOIMINEN
Katakri 2020
See all related requirements and other information from tasks own page.
Go to >
Applying original security measures to copies and translations
1. Task description

Printers and copiers are interpreted as information systems and must therefore meet the requirements for both technical, physical and administrative information security. The technical requirements can be met, for example, with a separate device solution.

The requirement can be met by taking the measures mentioned below:

  • Copies are treated like original data.
  • The copy can only be handed over to a person who has processing rights to the information and a need for the information content.
  • A copy/printout may only be taken by with a device that meets the safety level requirements.



Identifying critical functions and related assets
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Risk management and leadership
Continuity management
16
requirements

Examples of other requirements this task affects

26: Kriittisten toimintojen tunnistaminen
Digiturvan kokonaiskuvapalvelu
72: Organisaation kriittisten palveluiden tunnistaminen
Digiturvan kokonaiskuvapalvelu
73: Kriittisten palveluiden riippuvuudet palvelutoimittajista
Digiturvan kokonaiskuvapalvelu
ASSET-1: Manage IT and OT Asset Inventory
C2M2
6.2a: Jatkuvuuden hallinta
Tietoturvasuunnitelma
See all related requirements and other information from tasks own page.
Go to >
Identifying critical functions and related assets
1. Task description

The organization has a clear process, according to which it identifies the most critical functions in terms of its operations (e.g. services offered to customers), which are subject to the highest continuity requirements.

Items in the IT environment that are necessary for these activities (such as information systems, data reserves, operating processes, partners, units, hardware) are classified as critical.

Critical functions are considered with the highest priority, e.g. in continuity planning, and stricter safety requirements can be applied to them than to other objects in the environment.

Tasks included in the policy

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

Never duplicate effort. Do it once - improve compliance across frameworks.

Reach multi-framework compliance in the simplest possible way
Security frameworks tend to share the same core requirements - like risk management, backup, malware, personnel awareness or access management.
Cyberday maps all frameworks’ requirements into shared tasks - one single plan that improves all frameworks’ compliance.
Do it once - we automatically apply it to all current and future frameworks.
Get to know Cyberday
Start your free trial
Cyberday is your all-in-one solution for building a secure and compliant organization. Whether you're setting up a cyber security plan, evaluating policies, implementing tasks, or generating automated reports, Cyberday simplifies the entire process.
With AI-driven insights and a user-friendly interface, it's easier than ever to stay ahead of compliance requirements and focus on continuous improvement.
Clear framework compliance plans
Activate relevant frameworks and turn them into actionable policies tailored to your needs.
Credible reports to proof your compliance
Use guided tasks to ensure secure implementations and create professional reports with just a few clicks.
AI-powered improvement suggestions
Focus on the most impactful improvements in your compliance with help from Cyberday AI.