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

Feature request: better error handling #1670

Open
rdegraaf-ncc3 opened this issue Sep 19, 2024 · 1 comment
Open

Feature request: better error handling #1670

rdegraaf-ncc3 opened this issue Sep 19, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@rdegraaf-ncc3
Copy link
Contributor

Is your feature request related to a problem? Please describe.

ScoutSuite can encounter various errors, including insufficient permissions to access something and rate-limiting errors. At this time, it logs an error message to the console and moves on. This isn't a terrible strategy, but it does mean that it's left with incomplete results. The problem is that the generated report does not indicate that results are incomplete. The rules engine also has no way to know that results are incomplete. As a result, the report may contain false positives or false negatives due to the incompleteness of the data that the rules engine processes.

Example: I recently had ScoutSuite tell me that some S3 Buckets were missing the "block public access" setting. But when I looked into the account, I didn't have permission to call s3:GetAccountPublicAccessBlock (due to an SCP on the account). So presumably the rule is giving a false positive when the data isn't present.

Describe the solution you'd like

There should be some way to expose to the rules engine that data may be missing. Generated reports should somehow display that certain rules could not be processed or may be missing targets due to incomplete data.

Describe alternatives you've considered

Right now, the only alternative is additional manual investigation.

@rdegraaf-ncc3 rdegraaf-ncc3 added the enhancement New feature or request label Sep 19, 2024
@x64-latacora
Copy link

Right now, the only alternative is additional manual investigation.

Looking at the errors file that gets generated along with the results can help you figure out what failed, but otherwise this is all valid.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants