Google Cloud supports multiple TLS cipher suites. To meet security or compliance requirements, you may want to deny requests from clients that use less secure TLS cipher suites.

The [`gcp.restrictTLSCipherSuites`](https://docs.cloud.google.com/docs/security/compliance/restrict-tls-cipher-suites.md.txt)
organization policy constraint provides this capability.

## Before you begin


To get the permissions that
you need to set, change, or delete organization policies,

ask your administrator to grant you the
[Organization Policy Administrator](https://docs.cloud.google.com/iam/docs/roles-permissions/orgpolicy.md.txt#orgpolicy.policyAdmin) (`roles/orgpolicy.policyAdmin`) IAM role on the organization.


For more information about granting roles, see [Manage access to projects, folders, and organizations](https://docs.cloud.google.com/iam/docs/granting-changing-revoking-access.md.txt).


You might also be able to get
the required permissions through [custom
roles](https://docs.cloud.google.com/iam/docs/creating-custom-roles) or other [predefined
roles](https://docs.cloud.google.com/iam/docs/roles-overview#predefined).

## Setting the organization policy

The `gcp.restrictTLSCipherSuites` organization policy constraint can be applied to Looker (Google Cloud core) instances that use a [public IP networking configuration](https://docs.cloud.google.com/looker/docs/looker-core-networking-options.md.txt#public_ip_connections).

You can apply the constraint before or after you create the instance.

Follow the instructions on the [Restrict TLS cipher suites](https://docs.cloud.google.com/docs/security/compliance/restrict-tls-cipher-suites.md.txt#restrict) documentation page to set the organization policy. Looker (Google Cloud core) is compliant with the Google-managed [MODERN SSL policy profile](https://docs.cloud.google.com/load-balancing/docs/ssl-policies-concepts.md.txt#defining_an_ssl_policy) and supports the cipher suites that are in that profile.

If you set or change the organization policy after the Looker (Google Cloud core) instance is created, you must perform one of the following actions to apply the organization policy update to the Looker (Google Cloud core) instance:

- [Restart](https://docs.cloud.google.com/looker/docs/looker-core-delete-restart.md.txt#restart_a_instance) the instance.
- [Edit](https://docs.cloud.google.com/looker/docs/looker-core-view-console.md.txt#config_edit) a Looker (Google Cloud core) setting within the Google Cloud console or through the `gcloud` CLI.

## Policy violations

If you set the organization policy restraint to allow no [MODERN cipher suites](https://docs.cloud.google.com/load-balancing/docs/ssl-policies-concepts.md.txt#defining_an_ssl_policy) supported by Looker (Google Cloud core), you will be unable to create, update, or restart the Looker (Google Cloud core) instance and will receive the following error:

```bash
com.google.apps.framework.request.FailedPreconditionException:
Constraint`constraints/gcp.restrictTLSCipherSuites` is violated for resource
`resourcemanager_projects``PROJECT_ID` Code: FAILED_PRECONDITION
```

This output includes the `PROJECT_ID` value, which is the ID of the project that is hosting the Looker (Google Cloud core) instance.

To address the violation, update the `gcp.restrictTLSCipherSuites` organization policy to allow at least one supported cipher suite.