Merge pull request #7566 from nabilat/user/nabilat/add-web-caution

[SCOPED] Adding security disclaimer for using the web solution

Author: denrea

articles/ai-services/computer-vision/concept-face-liveness-detection.md

@@ -74,7 +74,8 @@ We do not store any images or videos from the Face Liveness Check. No image/vide
 
 ## Security
 
-We include additional runtime application self-protections (RASP), provided by [GuardSquare]( https://www.guardsquare.com/blog/why-guardsquare), in our Mobile SDKs (iOS and Android). 
+> [!IMPORTANT]
+> It is important for developers to be aware of the security implications when choosing the right solution — either Web or Mobile. While both the Web and Mobile solutions conform to iBeta Level 1 and Level 2 ISO/IEC 30107-3 PAD standards, the Mobile solution includes additional Runtime Application Self-Protections (RASP) provided by [GuardSquare](https://www.guardsquare.com/blog/why-guardsquare), which are not available in the Web solution. Notably, the Web solution has limitations inherent to running in browser environments and may be more vulnerable to certain attacks — for example, those involving virtual cameras — due to browser sandbox restrictions that limit runtime attack detection. We recommend using the Mobile solution whenever possible. If you choose the Web solution, it is critical that you closely follow the [shared-responsibility best practices](./liveness-detection-shared-responsibility.md) and consider implementing additional safeguards and monitoring to mitigate potential runtime attacks.
 
 ## Abuse Detection
 

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

@@ -12,7 +12,10 @@ ms.topic: conceptual
 
 # Shared responsibility for Face liveness detection
 
-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 at [Shared responsibility in the cloud](/azure/security/fundamentals/shared-responsibility). Understanding the shared responsibility model is especially important for liveness detection solutions. This document covers three aspects of how to secure and monitor your solution.
+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 at [Shared responsibility in the cloud](/azure/security/fundamentals/shared-responsibility). Understanding the shared responsibility model is especially important for liveness detection solutions. This document covers various aspects of how to secure and monitor your solution.
+
+> [!IMPORTANT]
+> It is important for developers to be aware of the security implications when choosing the right solution — either Web or Mobile. While both the Web and Mobile solutions conform to iBeta Level 1 and Level 2 ISO/IEC 30107-3 PAD standards, the Mobile solution includes additional Runtime Application Self-Protections (RASP) provided by [GuardSquare](https://www.guardsquare.com/blog/why-guardsquare), which are not available in the Web solution. Notably, the Web solution has limitations inherent to running in browser environments and may be more vulnerable to certain attacks — for example, those involving virtual cameras — due to browser sandbox restrictions that limit runtime attack detection. We recommend using the Mobile solution whenever possible. If you choose the Web solution, it is critical that you closely follow the guidance in this document and consider implementing additional safeguards and monitoring to mitigate potential runtime attacks.
 
 ## Secure the connections