Check ID:
Provider: AWS
Service:
Severity: MEDIUM
Categories:
Resource type:
storagegateway_fileshare_encryption_enabledProvider: AWS
Service:
storagegatewaySeverity: MEDIUM
Categories:
encryptionResource type:
OtherWhat this check verifies
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.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
- Terraform
- Native IaC
- Dashboard steps
aws storagegateway update-nfs-file-share —file-share-arn <example_resource_arn> —kms-encrypted —kms-key <example_kms_key_arn>
References
- https://www.trendmicro.com/trendaivisiononecloudriskmanagement-staging/knowledge-base/aws/StorageGateway/file-shares-encrypted-with-cmk.html#
- https://docs.aws.amazon.com/filegateway/latest/files3/encrypt-objects-stored-by-file-gateway-in-amazon-s3.html
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = storagegateway_fileshare_encryption_enabled. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to AWS checks