Harden Bicep IaC: enforce HTTPS, TLS 1.2, SQL TDE, auditing, and diagnostic settings #27
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Identified and remediated 12 security misconfigurations across Bicep infrastructure definitions. All changes maintain backward compatibility.
Network Security
httpsOnly,minTlsVersion: '1.2', disable FTPSpublicNetworkAccess: 'Disabled')Data Protection
Observability
Configuration Example
SQL Server now supports optional Azure AD authentication:
Compliance
Aligns to CIS Azure 4.1.x, 5.1.x, 9.x; NIST 800-53 SC-7/8/28, AU-2; Azure Security Benchmark DP-3/4, LT-4/5, NS-1/8, PA-7.
See
BICEP_SECURITY_REPORT.mdfor detailed findings and control mappings.Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
aka.ms/usr/local/bin/bicep bicep build resources.bicep(dns block)/usr/local/bin/bicep bicep build main.bicep(dns block)If you need me to access, download, or install something from one of these locations, you can either:
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.