Skip to content

Commit 5322692

Browse files
authored
Merge pull request #175831 from shisriva-msft/shisriva-kvvm-docs
Adding certificates use cases
2 parents 8398b3e + 0f3f314 commit 5322692

File tree

1 file changed

+13
-0
lines changed

1 file changed

+13
-0
lines changed

articles/key-vault/certificates/about-certificates.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -152,6 +152,19 @@ Certificate contacts contain contact information to send notifications triggered
152152

153153
Access control for certificates is managed by Key Vault, and is provided by the Key Vault that contains those certificates. The access control policy for certificates is distinct from the access control policies for keys and secrets in the same Key Vault. Users may create one or more vaults to hold certificates, to maintain scenario appropriate segmentation and management of certificates. For more information on certificate access control, see [here](certificate-access-control.md)
154154

155+
156+
## Certificate Use Cases
157+
158+
### Secure communication and authentication
159+
160+
TLS certificates can help encrypt communications over the internet and establish the identity of websites, making the entry point and mode of communication secure. Additionally, a chained certificate signed by a public CA can help verify that the entities holding the certificates are whom they claim to be. As an example, the following are some excellent use cases of using certificates to secure communication and enable authentication:
161+
* Intranet/Internet websites: protect access to your intranet site and ensure encrypted data transfer over the internet using TLS certificates.
162+
* IoT and Networking devices: protect and secure your devices by using certificates for authentication and communication.
163+
* Cloud/Multi-Cloud: secure cloud-based applications on-prem, cross-cloud, or in your cloud provider's tenant.
164+
165+
### Code signing
166+
A certificate can help secure the code/script of software, thereby ensuring that the author can share the software over the internet without being changed by malicious entities. Furthermore, once the author signs the code using a certificate leveraging the code signing technology, the software is marked with a stamp of authentication displaying the author and their website. Therefore, the certificate used in code signing helps validate the software's authenticity, promoting end-to-end security.
167+
155168
## Next steps
156169

157170
- [About Key Vault](../general/overview.md)

0 commit comments

Comments
 (0)