+OPS.2.1 Outsourcing for Customers
---+OPS.2.1.G1. Insufficient Rules Regarding Information Security
---+OPS.2.1.G2. Incorrect Administration of Site, System and Data Access Rights
---+OPS.2.1.G3. Inadequate testing and approval procedures
---+OPS.2.1.G4. Inadequate contractual arrangements with outsourcing service providers
---+OPS.2.1.G5. Insufficient terms for the end of an outsourcing project
---+OPS.2.1.G6. Dependency on an Outsourcing Service Provider
---+OPS.2.1.G7. Disruption of the Office Atmosphere due to an Outsourcing Project
---+OPS.2.1.G8. Inadequate Information Security in the Early Stages of Outsourcing
---+OPS.2.1.G9. Failure of an Outsourcing Service Provider’s Systems
---+OPS.2.1.G10. Vulnerabilities in the Connection to an Outsourcing Service Provider
---+OPS.2.1.G11. Lack of Multi-Client Capability with the Outsourcing Service Provider
---+OPS.2.1.A1 Specification of Security Requirements for Outsourcing Projects (B)
---+OPS.2.1.A2 Timely Involvement of Employee Representatives [Central Administration] (S)
---+OPS.2.1.A3 Selection of a Suitable Outsourcing Service Provider (S)
---+OPS.2.1.A4 Contractual Arrangements with the Outsourcing Service Provider (S)
---+OPS.2.1.A5 Establishing an Outsourcing Strategy (S)
---+OPS.2.1.A6 Drawing up a Security Concept for the Outsourcing Project [Process Owner] (S)
---+OPS.2.1.A7 Definition of Possible Communication Partners [Central Administration] (S)
---+OPS.2.1.A8 Provisions for Deploying the Personnel of the Outsourcing Service Provider [Human Resources Department] (S)
---+OPS.2.1.A9 Agreements on Connecting to Outsourcing Partner Networks (S)
---+OPS.2.1.A10 Agreement on the Exchange of Data Between Outsourcing Partners (S)
---+OPS.2.1.A11 Planning and Maintaining Information Security During Ongoing Outsourcing Operations (S)
---+OPS.2.1.A12 Change Management [Process Owner] (S)
---+OPS.2.1.A13 Secure Migration in Outsourcing Projects (S)
---+OPS.2.1.A14 Contingency Planning for Outsourcing [BCM Officer] (S)
---+OPS.2.1.A15 Organised Termination of an Outsourcing Relationship [Procurement Department] (S)
---+OPS.2.1.A16 Security Vetting of Employees (H)
|
OPS.2.1 Outsourcing for Customers
IntroductionWithin the framework of outsourcing, organisations (outsourcing customers) outsource business processes and services entirely or partially to external service providers (outsourcing service providers). Outsourcing can involve the use and operation of hardware and software. A service can be provided on the 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 what is outsourced, every outsourcing arrangement binds the customer to the external service provider and the quantity and quality of its services. For the customer in particular, this relationship is associated not only with opportunities, but also with considerable risks. These include a high degree of dependency and the loss of in-house knowledge, as well as of ways to control and guide operations. Information security aspects must therefore be taken into consideration appropriately at every stage of an outsourcing arrangement. ObjectiveThis module seeks to ensure that all the security objectives of a given outsourcing customer are still met after its business processes or services have been handed over to an outsourcing service provider. The agreed security level should be consistently maintained or improved regardless of outsourcing. Outsourcing must not result in any uncontrollable risks for the outsourcing organisation with regard to information security. The focus of this module consists of requirements that outsourcing customers should consider and meet during every phase of an outsourcing project. Scoping and ModellingModule OPS.2.1 Outsourcing for Customers must be applied separately from the user perspective to each outsourcing service provider that provides services to one or more of a given customer's target objects. This module includes threats and security requirements from the outsourcing customers’ point of view and is limited to the requirements regarding the protection of information on the part of the outsourcing organisation. Transmission paths to outsourcing service providers are not covered here. The use of cloud services is dealt with in module OPS.2.2 Cloud Usage. Module OPS.2.1 Outsourcing for Customers module is not applicable to such cases. Module OPS.2.1 Outsourcing for Customers also does not apply to service providers (such as porter services or cleaning staff) that perform tasks on behalf of a customer without assuming responsibility for a target object. Since these service providers nevertheless have access to target objects, they must be integrated into the customer's security concept in line with IT-Grundschutz. This integration is to be carried out at the requirement level—that is, via the requirements for third-party personnel, gatekeepers, security services, and cleaning staff as found in modules ORP.2 Personnel and INF.1 Generic Building, for example. Useful ResourcesThe International Organization for Standardization (ISO) provides guidelines for the management of service providers in the ISO/IEC 27001:2013 standard (section 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 (SC1) 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. Übersicht
| Bezeichnung |
Standard |
|
OPS.2.1.A1 Specification of Security Requirements for Outsourcing Projects (B)
|
All the security requirements for an outsourcing project MUST be defined on the basis of an outsourcing strategy. Both outsourcing parties MUST contractually commit to comply with IT-Grundschutz or a comparable level of protection. All interfaces between the outsourcing service provider and the outsourcing customer MUST be identified and corresponding security requirements defined in this regard. The security requirements MUST specify the authorisations (e.g. site, system, and data access rights) that the two parties are to grant to one another.
|
|
OPS.2.1.A2 Timely Involvement of Employee Representatives [Central Administration] (S)
|
Employee Representatives SHOULD be informed of an outsourcing project in good time. Employee Representatives SHOULD be involved from the tender phase onwards. Depending on the outsourcing project in question, the statutory rights of co-determination SHOULD be taken into consideration.
|
|
OPS.2.1.A3 Selection of a Suitable Outsourcing Service Provider (S)
|
A requirements profile containing the security requirements for a given outsourcing project SHOULD be created for selecting an outsourcing service provider. Assessment criteria for the outsourcing service provider and its staff SHOULD also exist. These SHOULD be based on the requirements profile.
|
|
OPS.2.1.A4 Contractual Arrangements with the Outsourcing Service Provider (S)
|
All aspects of an outsourcing project SHOULD be agreed in writing with the outsourcing service provider in question. In addition, all roles and duties of cooperation for the creation, review, and modification of a security concept SHOULD be regulated with the outsourcing service provider (e.g. if personnel changes occur). The rights and obligations of the contractual parties SHOULD be agreed in writing. For the purpose of checking compliance with the requirements at hand on a regular basis, the outsourcing service provider SHOULD enable the outsourcing customer to conduct audits.
|
|
OPS.2.1.A5 Establishing an Outsourcing Strategy (S)
|
A strategy for outsourcing SHOULD be defined. This SHOULD take into account the economic, technical, organisational, and legal framework conditions, as well as the relevant aspects of information security. The business processes, tasks, or applications generally associated with outsourcing SHOULD be clarified. An outsourcing customer SHOULD retain sufficient skills, competencies, and resources to be able to determine and control the information security requirements for each outsourcing project on its own. An outsourcing strategy SHOULD describe the goals, opportunities, and risks of the corresponding outsourcing project.
|
|
OPS.2.1.A6 Drawing up a Security Concept for the Outsourcing Project [Process Owner] (S)
|
An outsourcing customer SHOULD draw up an information security concept based on the associated security requirements for each of its outsourcing projects. Every outsourcing service provider SHOULD also provide an individual security concept for the respective outsourcing project. The two security concepts SHOULD be coordinated. The outsourcing service provider's security concept and its implementation SHOULD be merged into an overall security concept. The outsourcing customer or independent third parties SHOULD regularly check the effectiveness of the security concept.
|
|
OPS.2.1.A7 Definition of Possible Communication Partners [Central Administration] (S)
|
The internal and external communication partners who may transmit and receive specific information about a given outsourcing project SHOULD be defined. There SHOULD be a process that can be used to check the functions of the communication partners on both sides. The admissible communication partners and their respective authorisations MUST always be documented and kept up to date.
|
|
OPS.2.1.A8 Provisions for Deploying the Personnel of the Outsourcing Service Provider [Human Resources Department] (S)
|
The employees of an outsourcing service provider SHOULD be obliged in writing to comply with relevant laws, regulations, and the outsourcing customer's rules. The employees of the outsourcing service provider SHOULD be briefed on their tasks and informed of existing information security regulations in a controlled manner. Deputising rules SHOULD be in place for the employees of the outsourcing service provider. There SHOULD be a controlled process that defines how the outsourcing service provider terminates its contractual relationships with its employees. Third-party personnel of the outsourcing service provider who are used on a short-term or one-off basis SHOULD be treated as visitors.
|
|
OPS.2.1.A9 Agreements on Connecting to Outsourcing Partner Networks (S)
|
Before the network of an outsourcing customer is connected to the network of its outsourcing service provider, all security-relevant aspects SHOULD be agreed in writing. The agreement SHOULD specifically define the areas and services to which the outsourcing service provider will be granted access in the network of the outsourcing customer. The affected areas SHOULD be suitably separated from each other. Compliance with the network connection agreements SHOULD be checked and documented. Contact persons SHOULD be appointed on both sides for organisational and technical questions about the network connection. The required security level SHOULD be ensured and verified with the outsourcing service provider before the network connection to the outsourcing service provider is activated. If there are security issues on one or both sides, it SHOULD be specified who must be informed and what escalation steps are to be initiated.
|
|
OPS.2.1.A10 Agreement on the Exchange of Data Between Outsourcing Partners (S)
|
The security safeguards required for regular exchanges of data with fixed communication partners SHOULD be agreed. Data formats and approaches for the secure exchange of data SHOULD also be defined. There SHOULD be contact persons for organisational and technical problems. Contact persons SHOULD also be named for any security-relevant events that occur when exchanging data with third parties. Availability and response times SHOULD be agreed for data exchanges with third parties. It SHOULD be defined which exchanged data may be used for what purposes.
|
|
OPS.2.1.A11 Planning and Maintaining Information Security During Ongoing Outsourcing Operations (S)
|
An operational concept SHOULD be drawn up which also takes the security aspects of a given outsourcing project into account. The security concepts of the outsourcing partners SHOULD be regularly checked to ensure that they are up to date and consistent with each other. The status of the security safeguards agreed SHOULD be checked at regular intervals. There SHOULD be regular communication between the outsourcing partners. Proposals for changes and improvements SHOULD be discussed and agreed regularly. The outsourcing partners SHOULD perform regular joint drills and tests to maintain the established level of security. Information on security risks and how to handle them SHOULD be exchanged between the 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.2.1.A12 Change Management [Process Owner] (S)
|
Outsourcing customers SHOULD be given sufficient notice of major changes. Outsourcing customers SHOULD regularly request documentation of all significant changes regarding planning, testing, approval, and documentation. Before any changes are made, fallback solutions SHOULD be developed in cooperation with the outsourcing service provider.
|
|
OPS.2.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. For the migration phase, a preliminary security concept SHOULD be drawn up that also considers the test and introduction phase. It SHOULD be ensured that production data is not used as test data in an unprotected manner during the migration phase. All changes SHOULD be documented. 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. In the event of changes during the migration phase, the extent to which the contractual basis has to be adapted SHOULD be checked.
|
|
OPS.2.1.A14 Contingency Planning for Outsourcing [BCM Officer] (S)
|
A contingency planning concept for outsourcing SHOULD exist that covers the components of the outsourcing customer and the outsourcing service provider in question, as well as the associated interfaces and communication channels. The contingency planning concept for outsourcing SHOULD specify the responsibilities, contact persons, and processes between the outsourcing customer and the outsourcing service provider. The outsourcing customer SHOULD monitor whether the outsourcing service provider has implemented the business continuity safeguards defined. Outsourcing customers and service providers SHOULD conduct joint emergency drills for this purpose.
|
|
OPS.2.1.A15 Organised Termination of an Outsourcing Relationship [Procurement Department] (S)
|
Contracts with outsourcing service providers SHOULD specify all aspects regarding the termination of the service relationship concerned, including for both planned and unplanned termination. The business of an outsourcing customer SHOULD NOT be affected if its service relationship with its outsourcing service provider is terminated. All information and data SHOULD be returned to the outsourcing customer upon termination. The outsourcing service provider SHOULD securely delete all related data once this information and data has been returned.
|
|
OPS.2.1.A16 Security Vetting of Employees (H)
|
There SHOULD be contractual agreements with outsourcing service providers that state that the trustworthiness of the personnel deployed will be checked appropriately. To this end, providers and customers SHOULD work together to define corresponding criteria.
|
1.1 Referenzen
1.2 Identifizierte Anforderungen
1.3 Zugehörige Regulierungen
2. Identifizierte Anforderungen
Anforderungen
| Quelle |
Anforderung |
3. Zugehörige Regulierungen
Regulierungen
| Quelle |
Regulierung |
Verknüpfte Vorgänge
|