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

Add default Yara paths to avoid long scans #1541

Closed
2 tasks done
paralta opened this issue Apr 8, 2024 · 1 comment · Fixed by #1774
Closed
2 tasks done

Add default Yara paths to avoid long scans #1541

paralta opened this issue Apr 8, 2024 · 1 comment · Fixed by #1774
Assignees
Labels
enhancement New feature or request go Pull requests that update Go code

Comments

@paralta
Copy link
Contributor

paralta commented Apr 8, 2024

Description

Currently, the Yara scanner might take more than one hour to scan an asset in AWS and GCP. Additionally, in Azure the scan never finishes. This can be avoided by limiting the list of paths that Yara needs to scan.

Steps to Reproduce

  1. Run a scan with the Misconfiguration family enabled
  2. Wait for scan to be over

Checklist

@paralta paralta added enhancement New feature or request go Pull requests that update Go code labels Apr 8, 2024
Copy link

github-actions bot commented Jun 9, 2024

Thank you for your contribution! This issue has been automatically marked as stale because it has no recent activity in the last 60 days. It will be closed in 14 days, if no further activity occurs. If this issue is still relevant, please leave a comment to let us know, and the stale label will be automatically removed.

@github-actions github-actions bot added the stale label Jun 9, 2024
@paralta paralta removed the stale label Jun 11, 2024
@paralta paralta linked a pull request Jun 12, 2024 that will close this issue
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request go Pull requests that update Go code
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants