Requirement

THREAT-2: Respond to Threats and Share Threat Information

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

MIL1 requirements
a. Internal and external information sources to support threat management activities are identified, at least in an ad hoc manner
b. Information about cybersecurity threats is gathered and interpreted for the function, at least in an ad hoc manner
c. Threat objectives for the function are identified, at least in an ad hoc manner
d. Threats that are relevant to the delivery of the function are addressed, at least in an ad hoc manner

MIL2 requirements
e. A threat profile for the function is established that includes threat objectives and additional threat characteristics (for example, threat actor types, motives, capabilities, and targets)
f. Threat information sources that collectively address all components of the threat profile are prioritized and monitored
g. Identified threats are analyzed and prioritized and are addressed accordingly
h. Threat information is exchanged with stakeholders (for example, executives, operations staff, government, connected organizations, vendors, sector organizations, regulators, Information Sharing and Analysis Centers [ISACs])

MIL3 requirements
i. The threat profile for the function is updated periodically and according to defined triggers, such as system changes and external events
j. Threat monitoring and response activities leverage and trigger predefined states of operation (SITUATION-3g)
k. Secure, near-real-time methods are used for receiving and sharing threat information to enable rapid analysis and action

This requirement is part of the framework:  
C2M2: MIL1
Best practices
How to implement:
THREAT-2: Respond to Threats and Share Threat Information
This policy on
THREAT-2: Respond to Threats and Share Threat Information
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. Internal and external information sources to support threat management activities are identified, at least in an ad hoc manner
b. Information about cybersecurity threats is gathered and interpreted for the function, at least in an ad hoc manner
c. Threat objectives for the function are identified, at least in an ad hoc manner
d. Threats that are relevant to the delivery of the function are addressed, at least in an ad hoc manner

MIL2 requirements
e. A threat profile for the function is established that includes threat objectives and additional threat characteristics (for example, threat actor types, motives, capabilities, and targets)
f. Threat information sources that collectively address all components of the threat profile are prioritized and monitored
g. Identified threats are analyzed and prioritized and are addressed accordingly
h. Threat information is exchanged with stakeholders (for example, executives, operations staff, government, connected organizations, vendors, sector organizations, regulators, Information Sharing and Analysis Centers [ISACs])

MIL3 requirements
i. The threat profile for the function is updated periodically and according to defined triggers, such as system changes and external events
j. Threat monitoring and response activities leverage and trigger predefined states of operation (SITUATION-3g)
k. Secure, near-real-time methods are used for receiving and sharing threat information to enable rapid analysis and action

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
THREAT-2: Respond to Threats and Share Threat Information
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
THREAT-2: Respond to Threats and Share Threat Information
of the framework  
C2M2: MIL1
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
Regular analysis and utilization of information related to information security threats
Critical
High
Normal
Low
16
requirements
Development and cloud
Technical vulnerability management

Regular analysis and utilization of information related to information security threats

This task helps you comply with the following requirements

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.