Four-Eyes Deletion Control for Critical IBM Cloud Services

IBM Cloud is an enterprise-grade platform where mission‑critical services are deployed and operated. A customer recently shared the following scenario: during periods of staff reduction or personnel transitions, there is a risk that a frustrated or malicious administrator could intentionally delete production‑critical services such as Key Protect, ROKS, or Security Manager.

Currently, when deleting a service instance, the platform only requires the user to re‑enter the service name as confirmation.

The proposed enhancement is to introduce an audited four‑eyes approval requirement for the deletion of designated critical cloud services in production environments. For each service, customers should be able to configure whether deletion is allowed under:

• Two‑eyes principle (standard deletion with single approval), or
• Four‑eyes principle (deletion requires a second, independent approver through an auditable workflow).

This feature would provide an additional security layer for enterprise customers, helping to prevent both accidental and intentional deletion of high‑value, business‑critical cloud services.