non-proprietary security policy document may be freely reproduced and distributed in its entirety without modification. Rancher Kubernetes Cryptographic Library FIPS 140-2 Non-Proprietary Security Policy CA 94042 rancher.com Corsec Security, Inc. 13921 Park Center Rd., Ste. 460 Herndon, VA 20171 corsec.com +1 703.276.6050 FIPS 140-2 Security Policy Rancher Kubernetes Cryptographic Specification Name Date [140] FIPS 140-2, Security Requirements for Cryptographic Modules 12/3/2002 [140AA] FIPS 140-2 Annex A: Approved Security Functions 6/10/2019 [140AC] FIPS 140-2 Annex

solutions to help them build applications quickly without compromising reliability, agility and security. Relying on upstream Kubernetes isn't enough for teams deploying Kubernetes into production production. Basic Kubernetes installations are plagued by a lack of central visibility, inconsistent security practices and complex management processes. Therefore, Kubernetes management platforms need to confidently DevOps efficiencies with simplified cluster operations • Consistent Security Policy and User Management: best-practice security policy enforcement and advanced user management on any infrastructure

※※※ Multi-tenant Management ※※※※ ※※※ ※※※ Authentication and Authorization ※※※※ ※※※※※ ※※※※※ Security ※※※※ ※※※※※ ※※ Windows Container ※ ※※※※ ※※※※ 5 Support Commercial Services and Support ※※※※※ packaging and publishing Source-to-Image and Binary-to-Image supported Source-to-Image and Binary-to-Image supported Source-to-Image and Binary-to-Image not supported CI/CD Pipeline Jenkins of Kubernetes-native and Kubernetes-based container management platform via UI and API; Security policy configurations across multiple clusters Edge computing Deep integration with KubeEdge;

on software development. Kubernetes orchestration provides capabilities such as auto scaling, security, and management of containerized applications. A persistent and stable data store is required for PowerFlex SLES SUSE Linux Enterprise Server SSD Solid-State Disk TLS Transport Layer Security VLAN Virtual Local Area Network VM Virtual Machine PowerFlex product overview to run Kubernetes on-premises, in the cloud, and at the edge. It addresses the operational and security challenges of managing multiple Kubernetes clusters anywhere. SUSE Rancher also provides IT operators

that a minimal audit policy is created (Automated) 3.2.2 Ensure that the audit policy covers key security concerns (Manual) 4.1 Worker Node Configuration Files 4.1.1 Ensure that the kubelet service file (Automated) 5.1.6 Ensure that Service Account Tokens are only mounted where necessary (Manual) 5.2 Pod Security Policies 5.2.1 Minimize the admission of privileged containers (Manual) 5.2.2 Minimize the admission 4.2 Consider external secret storage (Manual) 5.5 Extensible Admission Control 5.5.1 Configure Image Provenance using ImagePolicyWebhook admission controller (Manual) 5.7 General Policies 5.7.1 Create

configurations and controls required to address Kubernetes benchmark controls from the Center for Information Security (CIS). This hardening guide describes how to secure the nodes in your cluster, and it is recommended configurations required to address Kubernetes benchmark controls from the Center for Information Security (CIS). For more detail about evaluating a hardened cluster against the official CIS benchmark, requires a private IP to be provided when registering the custom nodes. When setting the default_pod_security_policy_template_id: to restricted Rancher creates RoleBindings and ClusterRoleBindings on the

configurations and controls required to address Kubernetes benchmark controls from the Center for Information Security (CIS). This hardening guide describes how to secure the nodes in your cluster, and it is recommended configurations required to address Kubernetes benchmark controls from the Center for Information Security (CIS). For more detail about evaluating a hardened cluster against the official CIS benchmark, enable_network_policy: true default_pod_security_policy_template_id: "restricted" services: etcd: uid: 52034 gid: 52034 kube-api: pod_security_policy: true secrets_encryption_config:

CNI plug-in, CN2 is a networking platform that provides dynamic end-to-end virtual networking and security for cloud-native containerized and virtual machine (VM) workloads, across multi-cluster compute clusters to multi-cluster deployments, including: • Full overlay networking including load balancing, security and multi-tenancy, elastic and resilient VPNs, and gateway services in single-cluster and multi-cluster not only easier to configure and manage, but also easier to apply consistent network policy and security. Figure 5 on page 14 provides more detail on this setup. The Contrail controller sits in the Kubernetes

against the CIS 1.4.0 Kubernetes benchmark. This document is a companion to the Rancher v2.2.x security hardening guide. The hardening guide provides prescriptive guidance for hardening a production production installation of Rancher, and this benchmark guide is meant to help you evaluate the level of security of the hardened cluster against each control in the benchmark. Because Rancher and RKE install audit compliance in Rancher-created clusters. This document is to be used by Rancher operators, security teams, auditors and decision makers. For more detail about each audit, including rationales and

profile intend to: offer practical advice appropriate for the environment; deliver an obvious security benefit; and not alter the functionality or utility of the environment beyond an acceptable margin more of the following characteristics: are intended for use in environments or use cases where security is paramount act as a defense in depth measure may negatively impact the utility or performance the following directives to the kube-api section under services: services: kube-api: pod_security_policy: true extra_args: anonymous-auth: "false" profiling: "false" r