-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GR7 | Validation 1 | Storage Accounts TLS 1.2 (M) #190
Labels
Comments
Created another ticket with all the recommended controls from here. |
Created another ticket with the app HTTPS configuration controls from here. |
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
TLS/ HTTPS Policy Checks
Description: The following are some new controls for the CaC Solution's Guardrail 7. The goal is to determine if TLS1.2+ or HTTPS encryption is being used for all cloud services including publicly accessible sites and external communications. The first check will focus on Storage Accounts while the second will look at Other Cloud Apps. The final check will consider firewall configurations. These are built-in policies provided by MS. Note: we will not be able to achieve this check entirely due to the limits in seeing configurations of non-native tools or virtual machines to host websites etc.,
ItemName: Storage Accounts TLS 1.2 (M)
ItemName: App Service HTTPS Configuration (M)
2. This check uses built-in Azure Policies and their evaluation to determine compliance. The following check is inside the Canada Federal PBMM:
If the PBMM initiative has been applied to the subscription, and the following policy has not been excluded, and the policy compliance results show all compliant resources then check is compliant. If there are no applicable resources in the environment default pass.
ItemName: Function App HTTPS Configuration (M)
3. This check uses built-in Azure Policies and their evaluation to determine compliance. The following check is inside the Canada Federal PBMM:
If the PBMM initiative has been applied to the subscription, and the following policy has not been excluded, and the policy compliance results show all compliant resources then check is compliant. If there are no applicable resources in the environment default pass.
The text was updated successfully, but these errors were encountered: