Secure Platform
Mirantis Kubernetes Engine provides default configurations that offer greater protection for applications running on top of Mirantis Container Runtime and across both Swarm and Kubernetes orchestration technologies. The platform establishes strong secure defaults, while still leaving the controls with the admin to change configurations and policies as needed.
Out-of-the-box security defaults include:
System-level mutual TLS authentication and cryptographic node identity ensure that communications stay inside the cluster, and foreign nodes stay outside, preventing data leakage and attacks.
Application-level isolation with authentication/ authorization lets you share resources without sacrificing security because you must explicitly open network communications to an application for any application or person to see or access it.
Container security solutions provide FIPS 140-2 validated cryptographic modules that ensure that Mirantis Container Runtime meets the standards required by the US Federal government and other regulated industries by delivering on the fundamental confidentiality, integrity and availability objectives of information security. Besides container runtime security, the Mirantis Cloud Native Platform product suite features DISA STIG validation for Mirantis Kubernetes Engine, making it easier for customers to pass compliance audits and ensure secure operations.