Skip to content

Commit 563c4c8

Browse files
Replace /ssl/ links from overview and create new outline for Min TLS version
1 parent 96241d0 commit 563c4c8

File tree

1 file changed

+22
-9
lines changed
  • src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management

1 file changed

+22
-9
lines changed

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls.mdx

Lines changed: 22 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -8,13 +8,13 @@ head:
88
content: TLS Settings — Cloudflare for SaaS
99
---
1010

11-
import { AvailableNotifications, Details, Render } from "~/components";
11+
import { AvailableNotifications, Details, Render, APIRequest } from "~/components";
1212

1313
[Mutual TLS (mTLS)](https://www.cloudflare.com/learning/access-management/what-is-mutual-tls/) adds an extra layer of protection to application connections by validating certificates on the server and the client. When building a SaaS application, you may want to enforce mTLS to protect sensitive endpoints related to payment processing, database updates, and more.
1414

15-
[Minimum TLS Version](/ssl/edge-certificates/additional-options/minimum-tls/) allows you to choose a cryptographic standard per custom hostname. Cloudflare recommends TLS 1.2 to comply with the Payment Card Industry (PCI) Security Standards Council.
15+
[Minimum TLS Version](#minimum-tls-version) only allows HTTPS connections from visitors that support the selected TLS protocol version or newer. Cloudflare recommends TLS 1.2 to comply with the Payment Card Industry (PCI) Security Standards Council. As a SaaS provider, you can control the Minimum TLS version for your zone as a whole, as well as for individual custom hostnames.
1616

17-
[Cipher suites](/ssl/edge-certificates/additional-options/cipher-suites/) are a combination of ciphers used to negotiate security settings during the [SSL/TLS handshake](https://www.cloudflare.com/learning/ssl/what-happens-in-a-tls-handshake/). As a SaaS provider, you can [specify configurations for cipher suites](#cipher-suites) on your zone as a whole and cipher suites on individual custom hostnames via the API.
17+
[Cipher suites](#cipher-suites) are a combination of ciphers used to negotiate security settings during the [SSL/TLS handshake](https://www.cloudflare.com/learning/ssl/what-happens-in-a-tls-handshake/). As a SaaS provider, you can specify configurations for cipher suites on your zone as a whole and cipher suites on individual custom hostnames via the API.
1818

1919
:::caution
2020
When you [issue a custom hostname certificate](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/) with wildcards enabled, any cipher suites or Minimum TLS settings applied to that hostname will only apply to the direct hostname.
@@ -27,22 +27,35 @@ However, if you want to update the Minimum TLS settings for all wildcard hostnam
2727
Once you have [added a custom hostname](/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started/), you can enable mTLS by using Cloudflare Access. Go to [Cloudflare Zero Trust](https://one.dash.cloudflare.com/) and [add mTLS authentication](/cloudflare-one/identity/devices/access-integrations/mutual-tls-authentication/) with a few clicks.
2828

2929
:::note
30-
3130
Currently, you cannot add mTLS policies for custom hostnames using [API Shield](/api-shield/security/mtls/).
32-
3331
:::
3432

3533
## Minimum TLS Version
3634

35+
:::note
36+
While TLS 1.3 is the most recent and secure version, it is not supported by some older devices. Refer to Cloudflare's recommendations when [deciding what version to use](/ssl/reference/protocols/#decide-which-version-to-use).
37+
:::
38+
39+
### Scope
40+
41+
- For custom hostnames created via API, it is possible not to explicitly define a value for `min_tls_version`. When that is the case, whatever value is defined as your zone's [minimum TLS version](/ssl/edge-certificates/additional-options/minimum-tls/) (under **Edge certificates** > **Minimum TLS Version**) will be applied. To confirm whether a given custom hostname has a specific minimum TLS version set, use the following API call.
42+
43+
<Details header="Example: check custom hostname settings">
44+
45+
In the API documentation, refer to [Custom Hostname Details](/api/resources/custom_hostnames/methods/get/).
46+
47+
48+
</Details>
49+
50+
- If you specify any other settings for that custom hostname via Dashboard, whichever value is set for Minimum TLS version will then override your zo
51+
52+
### Setup
53+
3754
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account and website.
3855
2. Go to **SSL/TLS** > **Custom Hostnames**.
3956
3. Find the hostname to which you want to apply Minimum TLS Version. Select **Edit**.
4057
4. Choose the desired TLS version under **Minimum TLS Version** and select **Save**.
4158

42-
:::note
43-
While TLS 1.3 is the most recent and secure version, it is not supported by some older devices. Refer to Cloudflare's recommendations when [deciding what version to use](/ssl/reference/protocols/#decide-which-version-to-use).
44-
:::
45-
4659
## Cipher suites
4760

4861
For security and regulatory reasons, you may want to only allow connections from certain cipher suites. Cloudflare provides recommended values and full cipher suite reference in our [Cipher suites documentation](/ssl/edge-certificates/additional-options/cipher-suites/#resources).

0 commit comments

Comments
 (0)