Skip to content

Commit 6d5c590

Browse files
committed
wording
1 parent ab4f734 commit 6d5c590

File tree

1 file changed

+7
-5
lines changed

1 file changed

+7
-5
lines changed

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

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

3232
## Deploy an SSL/TLS certificate
3333

34-
After you've created your SSL/TLS certificate as required and have it installed on a trusted storage, deploy it to your OT sensor or on-premises management console.
34+
Deploy your SSL/TLS certificate by importing it to your OT sensor or on-premises management console.
35+
36+
Verify that your SSL/TLS certificate [meets the required parameters](#verify-certificate-file-parameter-requirements), and that you have [access to a CRL server](#verify-crl-server-access).
3537

3638
### Import the SSL/TLS certificate
3739

@@ -105,7 +107,7 @@ If validation fails, communication between the relevant components is halted and
105107

106108
## Create a certificate
107109

108-
Add description.
110+
Create either a CA-signed SSL/TLS certificate or a self-signed SSL/TLS certificate (not recommended).
109111

110112
### Create CA-signed SSL/TLS certificates
111113

@@ -119,7 +121,7 @@ You can also convert existing certificate files if you don't want to create new
119121

120122
### Create self-signed SSL/TLS certificates
121123

122-
Create self-signed SSL/TLS certificates by first [downloading a security certificate](#import-a-downloaded-security-certificate-to-a-trusted-store) from the OT sensor or on-premises management console and then exporting it to the required file types.
124+
Create self-signed SSL/TLS certificates by first [downloading a security certificate](#download-a-security-certificate) from the OT sensor or on-premises management console and then exporting it to the required file types.
123125

124126
> [!NOTE]
125127
> While you can use a locally-generated and self-signed certificate, we do not recommend this option.
@@ -198,7 +200,7 @@ If these tests fail, review [certificate file parameter requirements](#verify-ce
198200

199201
### Import a downloaded security certificate to a trusted store
200202

201-
**Download a security certificate:**
203+
#### Download a security certificate
202204

203205
1. After [installing your OT sensor software](ot-deploy/install-software-ot-sensor.md) or [on-premises management console](ot-deploy/install-software-on-premises-management-console.md), go to the sensor's or on-premises management console's IP address in a browser.
204206

@@ -210,7 +212,7 @@ If these tests fail, review [certificate file parameter requirements](#verify-ce
210212

211213
1. In the **Certificate viewer** pane, select the **Details** tab, then select **Export** to save the file on your local machine.
212214

213-
**Import the sensor's locally signed certificate to your certificate store:**
215+
#### Import the sensor's locally signed certificate to your certificate store
214216

215217
After creating your locally signed certificate, import it to a trusted storage location. For example:
216218

0 commit comments

Comments
 (0)