Requirement

THIRD-PARTIES-2: Manage Third-Party Risk

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

MIL1 requirements
a. The selection of suppliers and other third parties includes consideration of their cybersecurity qualifications, at least in an ad hoc manner
b. The selection of products and services includes consideration of their cybersecurity capabilities, at least in an ad hoc manner

MIL2 requirements
c. A defined method is followed to identify cybersecurity requirements and implement associated controls that protect against the risks arising from suppliers and other third parties
d. A defined method is followed to evaluate and select suppliers and other third parties
e. More rigorous cybersecurity controls are implemented for higher priority suppliers and other third parties
f. Cybersecurity requirements (for example, vulnerability notification, incident-related SLA requirements) are formalized in agreements with suppliers and other third parties
g. Suppliers and other third parties periodically attest to their ability to meet cybersecurity requirements

MIL3 requirements
h. Cybersecurity requirements for suppliers and other third parties include secure software and secure product development requirements where appropriate
i. Selection criteria for products include consideration of end-of-life and end-of-support timelines
j. Selection criteria include consideration of safeguards against counterfeit or compromised software, hardware, and services
k. Selection criteria for higher priority assets include evaluation of bills of material for key asset elements, such as hardware and software
l. Selection criteria for higher priority assets include evaluation of any associated third-party hosting environments and source data
m. Acceptance testing of procured assets includes consideration of cybersecurity requirements

This requirement is part of the framework:  
C2M2: MIL1

Other requirements of the framework

20098
THIRD-PARTIES-2: Manage Third-Party Risk
Best practices
How to implement:
THIRD-PARTIES-2: Manage Third-Party Risk
This policy on
THIRD-PARTIES-2: Manage Third-Party Risk
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. The selection of suppliers and other third parties includes consideration of their cybersecurity qualifications, at least in an ad hoc manner
b. The selection of products and services includes consideration of their cybersecurity capabilities, at least in an ad hoc manner

MIL2 requirements
c. A defined method is followed to identify cybersecurity requirements and implement associated controls that protect against the risks arising from suppliers and other third parties
d. A defined method is followed to evaluate and select suppliers and other third parties
e. More rigorous cybersecurity controls are implemented for higher priority suppliers and other third parties
f. Cybersecurity requirements (for example, vulnerability notification, incident-related SLA requirements) are formalized in agreements with suppliers and other third parties
g. Suppliers and other third parties periodically attest to their ability to meet cybersecurity requirements

MIL3 requirements
h. Cybersecurity requirements for suppliers and other third parties include secure software and secure product development requirements where appropriate
i. Selection criteria for products include consideration of end-of-life and end-of-support timelines
j. Selection criteria include consideration of safeguards against counterfeit or compromised software, hardware, and services
k. Selection criteria for higher priority assets include evaluation of bills of material for key asset elements, such as hardware and software
l. Selection criteria for higher priority assets include evaluation of any associated third-party hosting environments and source data
m. Acceptance testing of procured assets includes consideration of 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
THIRD-PARTIES-2: Manage Third-Party Risk
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
THIRD-PARTIES-2: Manage Third-Party Risk
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.