azuresql-db-auth
Pass
Audited by Gen Agent Trust Hub on Aug 21, 2026
Risk Level: SAFE
Full Analysis
- [Least-Privilege Principles]: The skill explicitly advises against using the administrative
salogin for application connections. It provides clear SQL patterns for creating dedicated logins and users with only the necessary database roles (e.g.,db_datareader,db_datawriter), which reduces the potential impact of a compromised application. - [Secure Secret Management]: The documentation includes robust guidance on avoiding hardcoded credentials. It recommends using git-ignored environment files,
dotnet user-secrets, and Azure Key Vault, aligning with industry security standards for protecting sensitive connection strings. - [Encrypted Communication]: The instructions mandate the use of
Encrypt=truefor all connections to ensure data is encrypted in transit. It also correctly advises restricting theTrustServerCertificate=truesetting to local development environments only, ensuring that certificate validation remains active for cloud production environments. - [Modern Authentication Methods]: It promotes the use of Microsoft Entra ID and Managed Identities in production. These methods eliminate the need for long-lived passwords in connection strings, significantly improving the security posture of the application infrastructure.
- [Vendor-Owned Resources]: The skill references a preview container image from a Microsoft-owned Azure Container Registry (
azurecr.io). This resource is consistent with the skill's intended use for Azure SQL development and preview testing.
Audit Metadata