Requirement

ASSET-2: Manage Information Asset Inventory

Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.

MIL1 requirements
a. Information assets that are important to the delivery of the function (for example, SCADA set points and customer information) are inventoried, at least in an ad hoc manner

MIL2 requirements
b. The information asset inventory includes information assets within the function that may be leveraged to achieve a threat objective
c. Inventoried information assets are categorized based on defined criteria that includes importance to the delivery of the function
d. Categorization criteria include consideration of the degree to which an asset within the function may be leveraged to achieve a threat objective
e. The information asset inventory includes attributes that support cybersecurity activities (for example, asset category, backup locations and frequencies, storage locations, asset owner, cybersecurity requirements)

MIL3 requirements
f. The information asset inventory is complete (the inventory includes all assets within the function)
g. The information asset inventory is current, that is, it is updated periodically and according to defined triggers, such as system changes
h. Information assets are sanitized or destroyed at end of life using techniques appropriate to their cybersecurity requirements

This requirement is part of the framework:  
C2M2: MIL1
Best practices
How to implement:
ASSET-2: Manage Information Asset Inventory
This policy on
ASSET-2: Manage Information Asset Inventory
provides a set concrete tasks you can complete to secure this topic. Follow these best practices to ensure compliance and strengthen your overall security posture.

MIL1 requirements
a. Information assets that are important to the delivery of the function (for example, SCADA set points and customer information) are inventoried, at least in an ad hoc manner

MIL2 requirements
b. The information asset inventory includes information assets within the function that may be leveraged to achieve a threat objective
c. Inventoried information assets are categorized based on defined criteria that includes importance to the delivery of the function
d. Categorization criteria include consideration of the degree to which an asset within the function may be leveraged to achieve a threat objective
e. The information asset inventory includes attributes that support cybersecurity activities (for example, asset category, backup locations and frequencies, storage locations, asset owner, cybersecurity requirements)

MIL3 requirements
f. The information asset inventory is complete (the inventory includes all assets within the function)
g. The information asset inventory is current, that is, it is updated periodically and according to defined triggers, such as system changes
h. Information assets are sanitized or destroyed at end of life using techniques appropriate to their cybersecurity requirements

Read below what concrete actions you can take to improve this ->
Frameworks that include requirements for this topic:
No items found.

How to improve security around this topic

In Cyberday, requirements and controls are mapped to universal tasks. A set of tasks in the same topic create a Policy, such as this one.

Here's a list of tasks that help you improve your information and cyber security related to
ASSET-2: Manage Information Asset Inventory
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
No other tasks found.

How to comply with this requirement

In Cyberday, requirements and controls are mapped to universal tasks. Each requirement is fulfilled with one or multiple tasks.

Here's a list of tasks that help you comply with the requirement
ASSET-2: Manage Information Asset Inventory
of the framework  
C2M2: MIL1
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
Data system listing and owner assignment
Critical
High
Normal
Low
80
requirements
System management
Data system management

Data system listing and owner assignment

This task helps you comply with the following requirements

Documentation of data sets for data stores
Critical
High
Normal
Low

The ISMS component hierachy

When building an ISMS, it's important to understand the different levels of information hierarchy. Here's how Cyberday is structured.

Framework

Sets the overall compliance standard or regulation your organization needs to follow.

Requirements

Break down the framework into specific obligations that must be met.

Tasks

Concrete actions and activities your team carries out to satisfy each requirement.

Policies

Documented rules and practices that are created and maintained as a result of completing tasks.

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.