The Azure Security Benchmark provides recommendations on Guidelines for System Hardening - Authentication hardening Secure transfer to storage accounts should be enabled Guidelines for Database Systems - Database serversĬommunications between database servers and web servers - 1277 Storage accounts should restrict network access Guidelines for Networking - Network design and configuration To review how the available Azure Policy built-ins for all Azure services map to this complianceĪzure Policy Regulatory Compliance - Australian Government ISM PROTECTED.įor more information about this compliance standard, seeĪustralian Government ISM PROTECTED. The associations between controls and Azure Policy Regulatory Compliance definitions for these compliance standards can change over time. Therefore, compliance in Azure Policy is only a partial view of your overall compliance status. In addition, the compliance standard includes controls that aren't addressed by any Azure Policy definitions at this time. This doesn't ensure that you're fully compliant with all requirements of a control. As such, Compliant in Azure Policy refers only to the policies themselves. However, there often isn't a one-to-one or complete match between a control and one or more policies. These policies might help you assess compliance with the control. Each control is associated with one or more Azure Policy definitions.
0 kommentar(er)
