+APP.4.4.A2 Planning Automation with CI/CD (B)

APP.4.4.A2 Planning Automation with CI/CD (B)

Automating the operation of applications in Kubernetes using CI/CD MUST ONLY take place after appropriate planning. The planning MUST cover the entire lifecycle from commissioning to decommissioning, including development, testing, operation, monitoring, and updates. A roles and rights concept and the securing of Kubernetes Secrets MUST be part of the planning.

1. Vue d’ensemble

1.1 Références

1.2 Exigences identifiées

1.3 Réglementations associées

2. Exigences identifiées

Exigences

3. Réglementations associées

Réglementations

Tickets liés

Liens
blocks G 0.14 Interception of Information / Espionage
blocks G 0.19 Disclosure of Sensitive Information
blocks G 0.20 Information or Products from an Unreliable Source
blocks G 0.21 Manipulation with Hardware or Software
blocks G 0.23 Unauthorised Access to IT Systems
blocks G 0.25 Failure of Devices or Systems
blocks G 0.27 Lack of Resources
blocks G 0.28 Software Vulnerabilities or Errors
blocks G 0.30 Unauthorised Use or Administration of Devices and Systems
blocks G 0.37 Repudiation of Actions
blocks G 0.39 Malware
blocks G 0.45 Data Loss
blocks G 0.46 Loss of Integrity of Sensitive Information