Requirement

SITUATION-1: Perform Logging

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

MIL1 requirements
a. Logging is occurring for assets that are important to the delivery of the function, at least in an ad hoc manner

MIL2 requirements
b. Logging is occurring for assets within the function that may be leveraged to achieve a threat objective, wherever feasible
c. Logging requirements are established and maintained for IT and OT assets that are important to the delivery of the function and assets within the function that may be leveraged to achieve a threat objective
d. Logging requirements are established and maintained for network and host monitoring infrastructure (for example, web gateways, endpoint detection and response software, intrusion detection and prevention systems)
e. Log data are being aggregated within the function

MIL3 requirements
f. More rigorous logging is performed for higher priority assets

This requirement is part of the framework:  
C2M2: MIL1

Other requirements of the framework

20056
SITUATION-1: Perform Logging
Best practices
How to implement:
SITUATION-1: Perform Logging
This policy on
SITUATION-1: Perform Logging
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. Logging is occurring for assets that are important to the delivery of the function, at least in an ad hoc manner

MIL2 requirements
b. Logging is occurring for assets within the function that may be leveraged to achieve a threat objective, wherever feasible
c. Logging requirements are established and maintained for IT and OT assets that are important to the delivery of the function and assets within the function that may be leveraged to achieve a threat objective
d. Logging requirements are established and maintained for network and host monitoring infrastructure (for example, web gateways, endpoint detection and response software, intrusion detection and prevention systems)
e. Log data are being aggregated within the function

MIL3 requirements
f. More rigorous logging is performed for higher priority assets

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
SITUATION-1: Perform Logging
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
SITUATION-1: Perform Logging
of the framework  
C2M2: MIL1
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical

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.