Skip to content
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

[Bug]: efs_not_publicly_accessible does not consider recommended AWS condition. #3865

Closed
lucasaboud0 opened this issue Apr 26, 2024 · 3 comments · Fixed by #3872
Closed

[Bug]: efs_not_publicly_accessible does not consider recommended AWS condition. #3865

lucasaboud0 opened this issue Apr 26, 2024 · 3 comments · Fixed by #3872
Assignees
Labels
bug provider/aws Issues/PRs related with the AWS provider severity/low Bug won't result in any noticeable breakdown of the execution.

Comments

@lucasaboud0
Copy link

lucasaboud0 commented Apr 26, 2024

Steps to Reproduce

Just run:
prowler -c efs_not_publicly_accessible -M json -F **** -R arn:aws:iam::****:role/**** -f us-east-1

Expected behaviour

Maybe set PASS to this issues.

Actual Result with Screenshots or Logs

{
  "AssessmentStartTime": "2024-04-26T16:24:14.909086",
  "FindingUniqueId": "prowler-aws-efs_not_publicly_accessible-****-us-east-1-fs-****",
  "Provider": "aws",
  "CheckID": "efs_not_publicly_accessible",
  "CheckTitle": "Check if EFS have policies which allow access to everyone",
  "CheckType": [
    "Protect",
    "Data protection"
  ],
  "ServiceName": "efs",
  "SubServiceName": "",
  "Status": "FAIL",
  "StatusExtended": "EFS fs-**** has a policy which allows access to everyone.",
  "Severity": "critical",
  "ResourceType": "AwsEFSFileSystem",
  "ResourceDetails": "",
  "Description": "Check if EFS have policies which allow access to everyone",
  "Risk": "EFS accessible to everyone could expose sensitive data to bad actors",
  "RelatedUrl": "",
  "Remediation": {
    "Code": {
      "NativeIaC": "",
      "Terraform": "",
      "CLI": "",
      "Other": ""
    },
    "Recommendation": {
      "Text": "Ensure efs has some policy but it does not have principle as *",
      "Url": "https://docs.aws.amazon.com/efs/latest/ug/access-control-block-public-access.html"
    }
  },
  "Compliance": {
    "MITRE-ATTACK": [
      "T1530"
    ],
    "AWS-Well-Architected-Framework-Security-Pillar": [
      "SEC03-BP07"
    ]
  },
  "Categories": [],
  "DependsOn": [],
  "RelatedTo": [],
  "Notes": "",
  "Profile": null,
  "AccountId": "****",
  "OrganizationsInfo": null,
  "Region": "us-east-1",
  "ResourceId": "****",
  "ResourceArn": "arn:aws:elasticfilesystem:us-east-1:****:file-system/fs-****",
  "ResourceTags": {
    "ManagedByAmazonSageMakerResource": "arn:aws:sagemaker:us-east-1:****:domain/d-****"
  }
}

How did you install Prowler?

Cloning the repository from github.com (git clone)

Environment Resource

EFS

OS used

Mac

Prowler version

3.15.0

Pip version

23.2.1

Context

Hello everyone,

I recently came across the alert "efs_not_publicly_accessible" on AWS. I followed the recommendations provided by AWS (https://docs.aws.amazon.com/efs/latest/ug/access-control-block-public-access.html), but Prowler still identifies it as an issue.

I reached out to Amazon to confirm if the solution presented in the documentation is sufficient, and they confirmed that it is.

Could you please check the possibility of making an exception when the condition "elasticfilesystem:AccessedViaMountTarget": "true" is present?

@lucasaboud0 lucasaboud0 added bug status/needs-triage Issue pending triage labels Apr 26, 2024
@jfagoagas jfagoagas added the provider/aws Issues/PRs related with the AWS provider label Apr 29, 2024
@jfagoagas
Copy link
Member

Hi @lucasaboud0, we will take a look at this as soon as possible. Thanks for using Prowler 🚀

Note for reviewers: Implement the following conditions https://docs.aws.amazon.com/efs/latest/ug/access-control-block-public-access.html#what-is-a-public-policy

@sergargar sergargar self-assigned this Apr 29, 2024
@sergargar sergargar added severity/low Bug won't result in any noticeable breakdown of the execution. and removed status/needs-triage Issue pending triage labels Apr 29, 2024
@sergargar sergargar linked a pull request Apr 29, 2024 that will close this issue
@sergargar
Copy link
Member

Hey @lucasaboud0 , I have done a PR to cover all possible cases including the one that you mentioned. Let me know if it works for you !

@lucasaboud0
Copy link
Author

Yeah! It works well.

Captura de Tela 2024-04-29 às 14 28 23

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug provider/aws Issues/PRs related with the AWS provider severity/low Bug won't result in any noticeable breakdown of the execution.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants