Security considerations
When using the External Secrets Operator for Red Hat OpenShift, there are some security concerns you should consider:
-
The
external-secretsoperand fetches the secrets from the configured external providers and stores it in a Kubernetes nativeSecretsresource. This results in a secret zero problem. It is recommended to secure the secret objects using additional encryption. For more information, see Data encryption options. -
When configuring
SecretStoreandClusterSecretStoreresources, consider using short-term credential-based authorization. This approach enhances security by limiting the window of opportunity for unauthorized access, even if credentials are compromised. -
To enhance the security of the External Secrets Operator for Red Hat OpenShift, it is crucial to implement role-based access controls (RBACs). These RBACs should define and limit access to the custom resources provided by the External Secrets Operator.