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

CIS benchmark output has missing checks #131

Open
silverhack opened this issue Dec 27, 2024 · 0 comments
Open

CIS benchmark output has missing checks #131

silverhack opened this issue Dec 27, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request impact-medium Issue with medium impact to codebase severity-medium Issue with medium severity

Comments

@silverhack
Copy link
Owner

Is your feature request related to a problem? Please describe.
If an specific resource (e.g. Virtual Machine) or service (e.g. SharePoint online) has a collector and an associated rule mapped in Monkey365 and for whatever reason the collector is unable to fetch data, results won't appear in any form of output. For example: Rule's output for SharePoint online won't appear in the output unless the Tenant have at least one site.

Apart from that, latest CIS benchmarks includes multiple checks that are not implemented in Monkey365. This generates confusion for end users because there is no way to see exactly what is audited/checked.

Describe the solution you'd like
Ideally, Monkey365 should map all the controls from specific benchmarks and mark rules as "manual" in the status field when a rule hasn't been validated for whatever reasons (e.g. If there is no automation for the rule, then the rule will be marked as a "manual").

Additional context
It should be noted that if collectors are unable to fetch data for whatever reason (e.g. permissions issue, lack of resources, etc..), associated rules will be removed and the rules won't appear in any form of output.

@silverhack silverhack added enhancement New feature or request impact-medium Issue with medium impact to codebase severity-medium Issue with medium severity labels Dec 27, 2024
@silverhack silverhack self-assigned this Dec 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request impact-medium Issue with medium impact to codebase severity-medium Issue with medium severity
Projects
None yet
Development

No branches or pull requests

1 participant