feat(query): implements "Beta - Storage Account Using Unsafe SMB Channel Encryption" #7830
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.








Reason for Proposed Changes
Currently there is no query to ensure that resources of type "azurerm_storage_account" has the "share_properties.smb.channel_encryption_type" array set to
["AES-256-GCM"].Quoting CIS_Microsoft_Azure_Foundations_Benchmark_v5.0.0 page 482:
Implement SMB channel encryption with AES-256-GCM for SMB file shares to ensure data confidentiality and integrity in transit. This method offers strong protection against eavesdropping and man-in-the-middle attacks, safeguarding sensitive information.."AES-256-GCM encryption enhances the security of data transmitted over SMB channels by safeguarding it from unauthorized interception and tampering."In the CIS Benchmark it is also stated that, by default, "
the following SMB channel encryption algorithms are allowed: AES-128-CCM, AES-128-GCM, AES-256-GCM". (all "Possible values" from the terraform documentation).Proposed Changes
Implemented the missing query.
The query will flag a "azurerm_storage_account" resource given any one of these 6 scenarios :
Note the "issueType" will be "MissingAttribute" for the first 3 scenarios and "IncorrectValue" for the last 3.
I submit this contribution under the Apache-2.0 license.