AzPolicyAdvertizer

last sync: 2024-Apr-25 17:46:59 UTC

A Microsoft Entra administrator should be provisioned for PostgreSQL servers

Azure BuiltIn Policy definition

Source Azure Portal
Display name A Microsoft Entra administrator should be provisioned for PostgreSQL servers
Id b4dec045-250a-48c2-b5cc-e0c4eec8b5b4
Version 1.0.1
Details on versioning
Category SQL
Microsoft Learn
Description Audit provisioning of a Microsoft Entra administrator for your PostgreSQL server to enable Microsoft Entra authentication. Microsoft Entra authentication enables simplified permission management and centralized identity management of database users and other Microsoft services
Mode Indexed
Type BuiltIn
Preview False
Deprecated False
Effect Default
AuditIfNotExists
Allowed
AuditIfNotExists, Disabled
RBAC role(s) none
Rule aliases none
Rule resource types IF (1)
Microsoft.DBforPostgreSQL/servers
THEN-Details (1)
Microsoft.DBforPostgreSQL/servers/administrators
Compliance
The following 1 compliance controls are associated with this Policy definition 'A Microsoft Entra administrator should be provisioned for PostgreSQL servers' (b4dec045-250a-48c2-b5cc-e0c4eec8b5b4)
Control Domain Control Name MetadataId Category Title Owner Requirements Description Info Policy#
Azure_Security_Benchmark_v3.0 IM-1 Azure_Security_Benchmark_v3.0_IM-1 Microsoft cloud security benchmark IM-1 Identity Management Use centralized identity and authentication system Shared **Security Principle:** Use a centralized identity and authentication system to govern your organization's identities and authentications for cloud and non-cloud resources. **Azure Guidance:** Microsoft Entra ID is Azure's identity and authentication management service. You should standardize on Microsoft Entra ID to govern your organization's identity and authentication in: - Microsoft cloud resources, such as the Azure Storage, Azure Virtual Machines (Linux and Windows), Azure Key Vault, PaaS, and SaaS applications. - Your organization's resources, such as applications on Azure, third-party applications running on your corporate network resources, and third-party SaaS applications. - Your enterprise identities in Active Directory by synchronization to Microsoft Entra ID to ensure a consistent and centrally managed identity strategy. Note: As soon as it is technically feasible, you should migrate on-premises Active Directory based applications to Microsoft Entra ID. This could be a Microsoft Entra Enterprise Directory, Business to Business configuration, or Business to consumer configuration. **Implementation and additional context:** Tenancy in Microsoft Entra ID: https://docs.microsoft.com/azure/active-directory/develop/single-and-multi-tenant-apps How to create and configure a Microsoft Entra instance: https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-access-create-new-tenant Define Microsoft Entra ID tenants: https://azure.microsoft.com/resources/securing-azure-environments-with-azure-active-directory/ Use external identity providers for an application: https://docs.microsoft.com/azure/active-directory/b2b/identity-providers n/a link 14
Initiatives usage
Initiative DisplayName Initiative Id Initiative Category State Type
Microsoft cloud security benchmark 1f3afdf9-d0c9-4c3d-847f-89da613e70a8 Security Center GA BuiltIn
History
Date/Time (UTC ymd) (i) Change type Change detail
2023-11-17 19:29:28 change Patch (1.0.0 > 1.0.1)
2023-02-10 18:41:56 add b4dec045-250a-48c2-b5cc-e0c4eec8b5b4
JSON compare
compare mode: version left: version right:
JSON
api-version=2021-06-01
EPAC