Skip to content

Commit 799cfb4

Browse files
committed
splitting the 2 procedures
1 parent 3e4db9f commit 799cfb4

File tree

1 file changed

+14
-4
lines changed

1 file changed

+14
-4
lines changed

articles/defender-for-iot/organizations/how-to-deploy-certificates.md

Lines changed: 14 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,20 @@ To perform the procedures described in this article, make sure that:
3131

3232
## Create SSL/TLS certificates
3333

34-
Create SSL/TLS certificates by first downloading a security certificate from the OT sensor or on-premises management console and then exporting it to the required file types.
34+
Use a certificate management platform, such as an automated PKI management platform, to create a certificate. Verify that the certificate meets [certificate file requirements](#verify-certificate-file-parameter-requirements), and then [test the certificate](#test-your-ssltls-certificates) file you created when you're done.
35+
36+
If you are not carrying out certificate validation, remove the CRL URL reference in the certificate. For more information, see [certificate file requirements](#verify-certificate-file-parameter-requirements).
37+
38+
Consult a security, PKI, or other qualified certificate lead if you don't have an application that can automatically create certificates.
39+
40+
You can also convert existing certificate files if you don't want to create new ones.
41+
42+
## Create self-signed SSL/TLS certificates
43+
44+
Create self-signed SSL/TLS certificates by first downloading a security certificate from the OT sensor or on-premises management console and then exporting it to the required file types.
45+
46+
> [!NOTE]
47+
> While you can use a locally-generated and self-signed certificate, we do not recommend this option.
3548
3649
### Download a security certificate
3750

@@ -213,9 +226,6 @@ After you've created your SSL/TLS certificate as required and have it installed
213226

214227
Select **Enable certificate validation** to validate the certificate against a [CRL server](#verify-crl-server-access).
215228

216-
> [!NOTE]
217-
> While you can also use a locally-generated and self-signed certificate, we do not recommend this option.
218-
219229
1. Select **Save** to save your certificate settings.
220230

221231
**To deploy a certificate on an on-premises management console sensor**:

0 commit comments

Comments
 (0)