2.1.10: Review the service provider’s security when outsourcing

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

Review the service provider’s security when outsourcing. As a minimum, one should review if the provider: a) has a management system in place for information security along with any certifications in accordance with international standards, e.g. ISO/IEC 27001. b) provides details of the security architecture used to deliver the service.c) has development plans for future security functions for the service in response to technological advances and changes with threats over time. d) maintains a list of who is granted access to the organisation’s information, where and how it will be processed and stored, and the extent of mechanisms to segregate it from other customers. e) has security functions that meet the organisation’s needs. f) carries out security monitoring in order to detect security incidents that could impact the organisation. g) has procedures in place for managing incidents and for non-conformance and security reporting. h) has established incident management plans which works with the organisation’s own plans. i) has procedures for approving subcontractors and their use of subcontractors. j) has specified which activities should be performed when terminating the contract, including returning/moving/deleting the organisation’s information.

This requirement is part of the framework:  
NSM ICT Security Principles (Norway)
Best practices
How to implement:
2.1.10: Review the service provider’s security when outsourcing
This policy on
2.1.10: Review the service provider’s security when outsourcing
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.

Review the service provider’s security when outsourcing. As a minimum, one should review if the provider: a) has a management system in place for information security along with any certifications in accordance with international standards, e.g. ISO/IEC 27001. b) provides details of the security architecture used to deliver the service.c) has development plans for future security functions for the service in response to technological advances and changes with threats over time. d) maintains a list of who is granted access to the organisation’s information, where and how it will be processed and stored, and the extent of mechanisms to segregate it from other customers. e) has security functions that meet the organisation’s needs. f) carries out security monitoring in order to detect security incidents that could impact the organisation. g) has procedures in place for managing incidents and for non-conformance and security reporting. h) has established incident management plans which works with the organisation’s own plans. i) has procedures for approving subcontractors and their use of subcontractors. j) has specified which activities should be performed when terminating the contract, including returning/moving/deleting the organisation’s information.

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
2.1.10: Review the service provider’s security when outsourcing
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
2.1.10: Review the service provider’s security when outsourcing
of the framework  
NSM ICT Security Principles (Norway)
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
Personnel guidelines for reporting security incidents
Critical
High
Normal
Low
Incident management resourcing and monitoring
Critical
High
Normal
Low
Documenting partners who are related to offered digital services supply chain
Critical
High
Normal
Low
Requiring a system description from suppliers of important information systems to be acquired
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.