+OPS.3.1 Outsourcing for Service Providers
---+OPS.3.1.G1. Failure of a Wide Area Network (WAN)
---+OPS.3.1.G2. Insufficient Rules Regarding Information Security
---+OPS.3.1.G3. Incorrect Administration of Site, System and Data Access Rights
---+OPS.3.1.G4. Inadequate testing and approval procedures
---+OPS.3.1.G5. Insecure transport of files and storage media
---+OPS.3.1.G6. Insufficient information security management by the outsourcing service provider
---+OPS.3.1.G7. Inadequate contractual arrangements with an outsourcing customer
---+OPS.3.1.G8. Insufficient terms for the end of an outsourcing arrangement
---+OPS.3.1.G9. Inadequate contingency planning for outsourcing
---+OPS.3.1.G10. Failure of an outsourcing service provider’s systems
---+OPS.3.1.G11. Vulnerabilities in the connection to an outsourcing service provider
---+OPS.3.1.G12. Social engineering
---+OPS.3.1.G13. Lack of multi-client capability with the outsourcing service provider
---+OPS.3.1.A1 Drawing Up a Rough Concept for the Outsourcing Service (B)
---+OPS.3.1.A2 Contractual Arrangements with Outsourcing Customers (S)
---+OPS.3.1.A3 Creating a Security Concept for the Outsourcing Project (S)
---+OPS.3.1.A4 Definition of Possible Communication Partners [Central Administration, Data Protection Officer] (S)
---+OPS.3.1.A5 Provisions for Deploying the Personnel of Outsourcing Service Providers [Human Resources Department] (S)
---+OPS.3.1.A6 Procedures Regarding the Use of Third-Party Personnel [Human Resources Department] (S)
---+OPS.3.1.A7 Creation of a Client Separation Concept by an Outsourcing Service Provider (S)
---+OPS.3.1.A8 Agreements on Connecting to Outsourcing Partner Networks (S)
---+OPS.3.1.A9 Agreement on the Exchange of Data Between Outsourcing Partners (S)
---+OPS.3.1.A10 Planning and Maintaining Information Security During Ongoing Outsourcing Operations (S)
---+OPS.3.1.A11 Site, System, and Data Access Control [Central Administration] (S)
---+OPS.3.1.A12 Change Management [Organisation] (S)
---+OPS.3.1.A13 Secure Migration in Outsourcing Projects (S)
---+OPS.3.1.A14 Contingency Planning for Outsourcing [BCM Officer] (S)
---+OPS.3.1.A15 Orderly Termination of an Outsourcing Relationship [Top Management] (S)
---+OPS.3.1.A16 Security Vetting of Employees [Human Resources Department] (H)

OPS.3.1 Outsourcing for Service Providers

Introduction

Within the framework of outsourcing, service providers handle business processes and services either in part or entirely on behalf of outsourcing customers. Outsourcing can involve the use and operation of hardware and software, and services can be provided on the outsourcing customer's premises or at an external operating facility of the outsourcing service provider. Typical examples involve the operation of a data centre, an application, or a web site. Outsourcing is a generic term that is often supplemented by other terms such as "hosting", "housing", or "colocation".

Regardless of the services actually taken over, outsourcing requires a close relationship between the service provider and the customer. This means the outsourcing service provider is not insulated from the risks of an outsourcing relationship. In addition, it must implement the risk-mitigating security requirements defined by outsourcing customers (see module OPS.2.1 Outsourcing for Customers). This is because it is also in the interest of the outsourcing service provider to provide the agreed service and maintain the agreed security level. If the requirements placed on the outsourcing service provider are not met, there is a risk of high contractual penalties and possibly further legal consequences. Along with financial consequences, this can also cause lasting damage to the provider's reputation.

Objective

The module describes the requirements that outsourcing service providers must meet in order to provide the level of security demanded by outsourcing customers and avoid uncontrollable risks that might result from these business relationships. This module concentrates on requirements that address the processes of planning, implementing, and controlling information security aspects within the framework of outsourcing from the service provider’s point of view.

Scoping and Modelling

Module OPS.3.1 Outsourcing for Service Providers must be applied from the service provider's perspective to any outsourcing customer that obtains services from an outsourcing provider.

The module contains security requirements that service providers should fulfil when offering outsourcing services.

The protection of transmission channels between service providers and the outsourcing customers is not addressed within the framework of this module.

The use of outsourcing services from the customer's perspective is covered in OPS.2.1 Outsourcing for Customers.

Useful Resources

The International Organization for Standardization (ISO) provides guidelines for the management of service providers in the ISO/IEC 27001:2013 standard (annex A.15.2, “Supplier Service Delivery Management”). DIN ISO 37500:2015-08 provides further information on dealing with service providers under “Guidance on Outsourcing”.

The Information Security Forum (ISF) defines various requirements (SD1.1, SA2.2, SC1.2, SC2.2, LC1.1, BC1.1) for service providers in “The Standard of Good Practice for Information Security”.

Germany's digital association Bitkom provides information on how business processes can be outsourced to service providers in “Leitfaden Business Process Outsourcing: BPO als Chance für den Standort Deutschland” [Guide to Business Process Outsourcing: BPO as an Opportunity for Germany as a Business Location].

Bitkom has also published guidance on the legal aspects of outsourcing in the "Leitfaden Rechtliche Aspekte von Outsourcing in der Praxis" [Guide to Legal Aspects of Outsourcing in Practice].

The National Institute of Standards and Technology (NIST) lists requirements for service providers in NIST Special Publication 800-53.

1. Přehled

Název Standard
OPS.3.1.A1 Drawing Up a Rough Concept for the Outsourcing Service (B)

Outsourcing service providers MUST prepare rough concepts for the services they offer. These rough concepts MUST account for the framework conditions of the outsourcing in question, such as special requests. They MUST answer basic questions about the security level and the security requirements of outsourcing customers.

OPS.3.1.A2 Contractual Arrangements with Outsourcing Customers (S)

All the aspects of outsourcing projects SHOULD be agreed in writing with the respective outsourcing customers. All responsibilities and duties to collaborate on creating, reviewing, and changing these aspects (e.g. persons) SHOULD be specified within the framework of each agreement, or also directly in the security concepts between outsourcing service providers and their customers.

OPS.3.1.A3 Creating a Security Concept for the Outsourcing Project (S)

An outsourcing service provider SHOULD have a security concept for its services. For individual outsourcing projects, it SHOULD also establish specific security concepts based on the respective outsourcing customers' security requirements. Common security objectives SHOULD be developed between outsourcing service providers and their customers. A common classification for all sensitive information SHOULD also be established. Regular checks SHOULD be performed to ensure that the applicable security concepts are implemented.

OPS.3.1.A4 Definition of Possible Communication Partners [Central Administration, Data Protection Officer] (S)

The internal and external communication partners who may transmit and receive specific information on a given outsourcing project SHOULD be defined between the outsourcing service provider and the outsourcing customer. It SHOULD be checked at regular intervals whether the communication partners are still working in their respective roles. The corresponding authorisations SHOULD be adapted in the event of changes. Criteria that determine which communication partners may receive which information SHOULD be specified between the outsourcing partners at hand.

OPS.3.1.A5 Provisions for Deploying the Personnel of Outsourcing Service Providers [Human Resources Department] (S)

The employees of an outsourcing service provider SHOULD be instructed regarding their tasks and informed of outsourcing customers' existing information security regulations. Where required, the outsourcing service provider’s employees SHOULD be vetted in accordance with the customer's requirements (e.g. by means of a certificate of good conduct). The employees of the outsourcing service provider SHOULD be obliged in writing to comply with the relevant laws, regulations, confidentiality agreements, and internal provisions. Deputising arrangements SHOULD be implemented in all areas.

OPS.3.1.A6 Procedures Regarding the Use of Third-Party Personnel [Human Resources Department] (S)

If an outsourcing service provider deploys external personnel, its outsourcing customers SHOULD be informed. External employees with responsibilities related to outsourcing SHOULD also be required in writing to comply with relevant laws, regulations, and internal rules. They SHOULD be briefed on their tasks, and in particular on security specifications. Third-party personnel deployed on short notice (or only once) SHOULD be treated as visitors. However, customers' security specifications SHOULD also be taken into account for third-party personnel.

OPS.3.1.A7 Creation of a Client Separation Concept by an Outsourcing Service Provider (S)

A suitable client separation concept SHOULD ensure that the application and data contexts of different outsourcing customers are separated appropriately. Client separation concepts SHOULD be drawn up by outsourcing service providers and made available to their customers. Client separation concepts SHOULD provide sufficient security for the protection needs of outsourcing customers. The necessary client separation mechanisms SHOULD be implemented sufficiently by the outsourcing service provider.

OPS.3.1.A8 Agreements on Connecting to Outsourcing Partner Networks (S)

Before a proprietary network is connected to the network of an outsourcing service provider, all the security-relevant aspects at hand SHOULD be specified in a written agreement. It SHOULD be defined who from one data network may access which areas and services of the other data network. Contact partners SHOULD be appointed on both sides for organisational and technical questions regarding the network connection. All security gaps identified SHOULD be eliminated and the required level of security SHOULD be verifiably achieved before the network connection is activated. In the event of security issues on one or both sides, it SHOULD be specified who must be informed and what escalation steps are to be initiated.

OPS.3.1.A9 Agreement on the Exchange of Data Between Outsourcing Partners (S)

The required security safeguards SHOULD be agreed for the regular exchange of data among fixed communication partners of the outsourcing partners in question. Data formats and a secure form of data exchange SHOULD be defined. Contact persons SHOULD be appointed for organisational and technical questions. Appropriate contact persons SHOULD also be named for security-relevant events that occur when exchanging data with third parties. Availability and response times when exchanging data with third parties SHOULD be agreed. The types of exchanged data that can be used for specific purposes SHOULD also be defined.

OPS.3.1.A10 Planning and Maintaining Information Security During Ongoing Outsourcing Operations (S)

The security concepts of outsourcing partners SHOULD be regularly checked to ensure that they are still up to date and consistent with each other. The status of the security safeguards agreed SHOULD be checked at regular intervals. Outsourcing partners SHOULD cooperate appropriately. They SHOULD also coordinate regularly on changes and improvements.

In addition, outsourcing partners SHOULD perform regular joint drills and tests. Information on security risks and how to handle them SHOULD be exchanged between outsourcing partners at regular intervals. A process SHOULD be a defined to secure the flow of information in case of security incidents that affect the contractual partners in question.

OPS.3.1.A11 Site, System, and Data Access Control [Central Administration] (S)

Site, system, and data access authorisations SHOULD be regulated for the employees of both outsourcing service providers and outsourcing customers. It SHOULD also be specified which authorisations are to be granted to auditors and other inspectors. Rights SHOULD always only be granted when they are necessary to perform a task. There SHOULD be a controlled procedure for granting, managing, and withdrawing authorisations.

OPS.3.1.A12 Change Management [Organisation] (S)

There SHOULD be policies for making changes to IT components, software, and configuration data. When making changes, the relevant security aspects SHOULD also be considered. All changes MUST be planned, tested, approved, and documented. How and to what extent the changes are documented SHOULD be agreed with outsourcing customers. The documentation SHOULD be made available to outsourcing customers. Fallback solutions SHOULD be developed before changes are carried out. In the event of major security-relevant changes, the information security management department of the outsourcing organisation in question SHOULD already be involved in advance.

OPS.3.1.A13 Secure Migration in Outsourcing Projects (S)

For the migration phase of a given outsourcing project, a security management team consisting of qualified employees of the outsourcing customer and the outsourcing service provider SHOULD be established. A security concept SHOULD be drawn up for the migration phase. Upon completion of the migration, the security concept SHOULD be updated. It SHOULD be ensured that all exceptions are reversed at the end of the migration phase. If there are changes during the migration phase, it SHOULD be checked whether the contractual basis and existing documents need to be adjusted accordingly.

OPS.3.1.A14 Contingency Planning for Outsourcing [BCM Officer] (S)

There SHOULD be a contingency planning concept for outsourcing that comprises the components of the outsourcing customer and the outsourcing service provider in question, as well as the associated interfaces. The contingency planning concept for outsourcing SHOULD specify the responsibilities, contact persons, and processes between the outsourcing customer and the outsourcing service provider. Regular joint emergency drills SHOULD be performed.

OPS.3.1.A15 Orderly Termination of an Outsourcing Relationship [Top Management] (S)

If a contractual relationship with an outsourcing customer is terminated, the business activities of the customer and the outsourcing provider SHOULD NOT be affected. The outsourcing contract with the outsourcing customer SHOULD specify all aspects regarding the termination of the service relationship in question, including for both a planned and an unplanned end of the contractual relationship. The outsourcing service provider SHOULD return all the information and data of the outsourcing customer. The outsourcing service provider SHOULD then securely delete all data belonging to the customer. All authorisations configured within the framework of the outsourcing project in question SHOULD be reviewed and deleted if required.

OPS.3.1.A16 Security Vetting of Employees [Human Resources Department] (H)

The trustworthiness of an outsourcing service provider's new employees and external personnel SHOULD be checked with the help of appropriate certificates. To this end, criteria SHOULD be contractually stipulated with outsourcing customers.

1.1 Odkazy

1.2 Identifikované požadavky

1.3 Související regulace

2. Identifikované požadavky

Požadavky
Zdroj Požadavek

3. Související regulace

Regulace
Zdroj Regulace

Propojené úkoly