Check ID:
Provider: AWS
Service:
Severity: MEDIUM
Categories:
Resource type:
efs_access_point_enforce_user_identityProvider: AWS
Service:
efsSeverity: MEDIUM
Categories:
identity-accessResource type:
AwsEfsAccessPointWhat this check verifies
Amazon EFS access points are evaluated for a defined POSIX user (uid, gid, optional secondary groups). The check inspects each access point on a file system and flags those without a configured POSIX user identity.
Risk
Without enforced POSIX identity, NFS clients can supply arbitrary UIDs/GIDs, enabling impersonation, unauthorized reads/writes, and ownership spoofing. This undermines confidentiality and integrity of shared data and can enable lateral movement across applications sharing the file system.Recommendation
Enforce a POSIX user identity on every access point using least-privilegeuid/gid (avoid 0). Apply separation of duties with dedicated access points per application and minimal groups. Use IAM to require access point usage and add defense in depth by enforcing a restricted root directory.
Remediation
- Terraform
- Native IaC
- Dashboard steps
References
- https://docs.aws.amazon.com/efs/latest/ug/efs-access-points.html
- https://repost.aws/knowledge-center/efs-access-points-directory-access
- https://www.plerion.com/cloud-knowledge-base/efs-access-points-should-be-configured-to-enforce-a-user-identity
- https://docs.aws.amazon.com/efs/latest/ug/enforce-identity-access-points.html
- https://docs.aws.amazon.com/securityhub/latest/userguide/efs-controls.html#efs-4
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = efs_access_point_enforce_user_identity. 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