Skip to content

Commit 1f8770e

Browse files
Update liveness-detection-shared-responsibility.md
1 parent f26ace7 commit 1f8770e

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/ai-services/computer-vision/liveness-detection-shared-responsibility.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
2-
title: Shared Responsibility For Face Liveness Detection
2+
title: Shared responsibility for Face liveness detection
33
titleSuffix: Azure AI services
4-
description: Azure and customers share responsibility for liveness detection solutions, covering connections, client apps, devices, and abuse monitoring
4+
description: Azure and customers share responsibility for liveness detection solutions, covering connections, client apps, devices, and abuse monitoring.
55
author: JinyuID
66
ms.author: lijiny
77
manager: nitinme
@@ -10,9 +10,9 @@ ms.date: 01/15/2025
1010
ms.topic: security
1111
---
1212

13-
# Shared Responsibility for Face Liveness Detection
13+
# Shared responsibility for Face liveness detection
1414

15-
It's the shared responsibility between Azure and the customer to build a secure and compliance solution. You can learn more about Azure shared responsibility model at here: [Shared responsibility in the cloud - Microsoft Azure](/azure/security/fundamentals/shared-responsibility). Understanding the shared responsibility model is especially important for liveness detection solutions, this document covers three aspects about how to secure the solution and monitor the solution.
15+
It's the shared responsibility between Azure and its customers to build a secure and compliant face liveness solution. You can learn more about Azure's shared responsibility model here: [Shared responsibility in the cloud - Microsoft Azure](/azure/security/fundamentals/shared-responsibility). Understanding the shared responsibility model is especially important for liveness detection solutions, this document covers three aspects about how to secure the solution and monitor the solution.
1616

1717
## Secure the Connections
1818

0 commit comments

Comments
 (0)