WebSphere® Liberty operator supports different mechanisms for securing your environment.
Securing initial credentials
No default credentials need to be changed. However, you must create your own credentials when you set up nodes and collectives. More information on securing WebSphere Liberty and WebSphere Liberty applications is available at Securing Liberty and its applications.
Setting limits with the ResourceQuota resource
Setting limits to the resources that can be used by a Kubernetes namespace can prevent such
security issues as Denial-of-Service (DOS) attacks. For more information about setting limits with
ResourceQuota resource, see Kubernetes Hardening Guidance (published by the National
Security Agency and the Cybersecurity and Infrastructure Security Agency) or Resource quotas in the Red Hat® OpenShift® documentation.
Advanced security hardening information
For advanced security hardening information, see Security considerations in the IBM Cloud Pak for Watson AIOps documentation.