<button class="button button-with-icon cloud-select-dropdown__button button-primary" aria-haspopup="true">Version 1.15 </button>

- [Latest](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/latest/how-to/security-overview)
- [Version 1.16](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.16/how-to/security-overview.md.txt)
- [Earlier versions (unsupported)](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.15/getting-support.md.txt#version-support)

<br />

This page provides an introduction to establishing good security practices for
Google Distributed Cloud. The guidance on this page is not intended to provide you with
a comprehensive list of best practices.

Using good practices for security on Google Distributed Cloud involves applying
concepts from Kubernetes and Google Kubernetes Engine (GKE), as well as concepts
that are unique to Google Distributed Cloud.

## Kubernetes security

We recommend that you follow general Kubernetes guidelines for security when
you're using Google Distributed Cloud.

For an introduction to Kubernetes security guidelines, see the [Security
Checklist](https://kubernetes.io/docs/concepts/security/security-checklist/)
and [Overview of Cloud Native
Security](https://kubernetes.io/docs/concepts/security/overview/)
in the Kubernetes documentation.

## GKE security

Google Distributed Cloud extends GKE to let you create
GKE clusters on your own Linux servers on your own premises. To
learn more about GKE security, see the [GKE
security overview](https://docs.cloud.google.com/kubernetes-engine/docs/concepts/security-overview). As
you're reading, keep in mind that because your control plane and nodes run
on-premises, the suggestions for
[control plane security](https://docs.cloud.google.com/kubernetes-engine/docs/concepts/security-overview.md.txt#control_plane_security)
and [node security](https://docs.cloud.google.com/kubernetes-engine/docs/concepts/security-overview.md.txt#node_security)
don't apply.

## Google Distributed Cloud security

The following sections provide guidance for establishing good security practices
for Google Distributed Cloud.

### Hardware security

- Secure your on-premises data centers with industry standard physical
  security and safety features.

- Ensure that access to your [admin workstation](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.15/installing/workstation-prerequisites.md.txt)
  is highly restricted. The admin workstation stores sensitive data such as
  `kubeconfig` files, SSH keys, and service account keys.

### Node security

- Keep your operating system up-to-date by updating software packages and installing security patches.

### Cluster security

- [Harden the security of your Google Distributed Cloud
  clusters](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.15/how-to/hardening-your-cluster).

- Isolate your traffic and data by using an [admin and user cluster
  deployment](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.15/installing/install-prep#admin_user_model). This
  deployment type helps you to achieve the following types of isolation:

  - Workload traffic is isolated from administrative, or management plane traffic.
  - Cluster access is isolated by group or role.
  - Production workloads are isolated from development workloads.
- [Upgrade your clusters](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.15/how-to/upgrade-best-practices.md.txt) to a
  [supported version](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.15/getting-support.md.txt#version-support). Using a
  supported version provides you with the following security benefits:

  - Fixes for security vulnerabilities.
  - New features and functions that take advantage of latest security posture and technologies.
  - Updates for bundled software and components.

### Workload security

- [Secure your containers using Security-Enhanced Linux
  (SELinux)](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.15/installing/configure-selinux).

- [Secure your workloads with
  Binary Authorization](https://docs.cloud.google.com/binary-authorization/docs/overview-on-prem).
  Binary Authorization is a service on Google Cloud that provides software
  supply-chain security for applications that run in the cloud. With
  Binary Authorization, you can ensure that internal processes that safeguard the
  quality and integrity of your software have successfully completed before an
  application is deployed to your production environment.

- Use [Workload Identity Federation for GKE](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/workload-identity.md.txt)
  to give Pods access to Google Cloud resources. Workload Identity Federation for GKE
  allows a Kubernetes service account to run as an IAM service account. Pods
  that run as the Kubernetes service account have the permissions of the IAM
  service account.

- [Follow the best practices for GKE
  RBAC](https://docs.cloud.google.com/kubernetes-engine/docs/best-practices/rbac).

### Network security

- [Choose a secure connection between your Google Distributed Cloud and
  Google Cloud](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.15/concepts/connect-on-prem-gcp#enhancing_your_fundamental_connection).
  After your fundamental connection is in place, add features that enhance the
  security of your connection.

- Limit the exposure of your clusters to the public internet by [installing
  them behind a proxy and creating firewall
  rules](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.15/installing/proxy). Also use
  the appropriate controls in your network environment to limit public access
  to the cluster.

### Authentication security

- [Manage identity with
  GKE Identity Service](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.15/installing/identity-manage).
  GKE Identity Service is an authentication service that lets you bring
  your existing identity solutions for authentication to multiple
  Google Kubernetes Engine (GKE) Enterprise edition environments. You can sign in to and use your
  Google Distributed Cloud clusters from the command line (all providers) or from
  the Google Cloud console (OIDC only), all using your existing identity
  provider.

- [Connect to registered clusters with the
  Connect gateway](https://docs.cloud.google.com/anthos/multicluster-management/gateway). The
  Connect gateway builds on the power of fleets to let
  GKE Enterprise users connect to and run commands against
  registered clusters in a simple, consistent, and secured way.

### Credential security

- [Rotate certificate
  authorities](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.15/how-to/ca-rotation).
  Google Distributed Cloud uses certificates and private keys to authenticate
  and encrypt connections between system components in clusters. To maintain
  secure cluster communication, rotate your user cluster certificate
  authorities periodically and whenever there is a possible security breach.

- [Rotate service account
  keys](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.15/how-to/update-secrets). To
  reduce the security risk caused by leaked keys, we recommend that you
  regularly rotate your service keys.

### Monitor your security

- [Use Kubernetes audit
  logging](https://docs.cloud.google.com/anthos/clusters/docs/bare-metal/1.15/how-to/audit-logging). Audit logging provides a way for administrators to retain, query, process, and alert on events that occur in your Google Distributed Cloud environments.

For more information about monitoring cluster security, see
[Monitor fleet security posture](https://docs.cloud.google.com/anthos/fleet-management/docs/secure#monitor-fleets-scale).