Check provider logo

Storage Gateway file share is encrypted with KMS CMK

storagegateway_fileshare_encryption_enabled

Severitymedium
by Prowler

Storage Gateway file shares configured with customer-managed KMS keys (CMKs) for server-side encryption of objects written to S3.

File shares without an explicit KMS key (e.g., SSE-KMS or DSSE-KMS) are identified.

Risk

Without CMEK, encryption relies on provider-managed keys, reducing control over who can decrypt and when. This weakens confidentiality by limiting key-policy enforcement, revocation, and auditable key use, increasing exposure from stolen S3 credentials or overly permissive roles.

Run this check with Prowler CLI

prowler aws --checks storagegateway_fileshare_encryption_enabled

Recommendation

Use a customer-managed KMS key for each file share's server-side encryption (SSE-KMS; consider DSSE-KMS for multilayer needs). Apply least privilege and separation of duties to key access, rotate keys, monitor key usage, and restrict scope to necessary principals and regions.

Remediation

CLI

aws storagegateway update-nfs-file-share --file-share-arn <example_resource_arn> --kms-encrypted --kms-key <example_kms_key_arn>

Native IaC
Terraform
Other
  1. In the AWS Console, go to Storage Gateway > File shares
  2. Select the affected file share and click Edit
  3. Under Encryption, choose AWS KMS key
  4. Select the CMK to use (or paste its ARN)
  5. Save changes

Source Code

Resource Type

Other

References