+SOV-4-05 Ingress Data Control
---+SOV-4-05-C
---+SOV-4-05-AC1
---+SOV-4-05-AC2
---+SOV-4-05-SI
|
1. Overview
SOV-4-05 Ingress Data Control
SOV-4-05 Ingress Data Control
| Summary |
Standard |
|
SOV-4-05-C
|
All software updates and operational data affecting the cloud service MUST be received, authorized and validated in a secured network area managed and controlled by the cloud service provider. The cloud service provider MUST verify and check updates for known vulnerabilities. Updates MUST include documentation satisfying the needs of the cloud service provider. The update process MUST be based on a controlled change management processes.
|
|
SOV-4-05-AC1
|
The cloud service provider MUST implement the secure network area (e. g. DMZ) on dedicated physical devices.
|
|
SOV-4-05-AC2
|
The cloud service provider MUST provide technical documentation how the criterion SOV-4-05-C is implemented to the responsible cybersecurity authority if requested, in accordance with applicable law and established supervisory, cooperation agreements or audit mechanisms. The responsible authority is the one in the country where the data center is located. Such information may be provided through appropriate confidentiality protections and secure disclosure procedures.
|
|
SOV-4-05-SI
|
A vulnerability is regarded as known, when it is listed in the European Union Vulnerability Database (EUVD) or in the Common Vulnerabilities and Exposures (CVE) Program from the National Institute of Standards and Technology (NIST).
|
1.1 References
1.2 Identified Requirements
1.2 Related Regulation
2. Identified Requirements
Requirements
| Source |
Requirement |
3. Related Regulations
Regulations
| Source |
Regulation |
|