silverhack
Update to latest CIS Benchmarks
Is your feature request related to a problem? Please describe. Some rules and rulesets for both Azure and Microsoft 365 are quite old and would benefit from further work.
Describe the solution you'd like Update rules and rulesets to at least a close version of the latest benchmark.
Additional context Once the rules have been updated consider to add additional benchmarks such as CISA, BIO compliance, etc..
Hi all,
Additionaly, the following benchmarks will be deprecated, and will be retired soon:
- CIS for Microsoft 365 1.4
- CIS for Microsoft 365 1.5
- CIS for Azure 1.4
- CIS for Azure 1.5
- CIS for Azure 2.0
Cheers,
I'm in progress of updating all the rules. Multiple statements should be reworded or adapted to latest CIS benchmark for clarity. Additionally, multiple checks were removed from benchmarks some months ago, and will be removed from codebase.
Updated comment. CIS 2.0 for Azure will also be updated to 3.0 version, so 2.0 version will be removed from codebase.
Cheers,
This issue has been automatically marked as stale because it has not had recent activity. We kindly ask you to check again if the issue you reported is still relevant in the current version of Monkey365. If it is, update this issue with a comment, otherwise it will be automatically closed if no further activity occurs. Thank you for your contributions.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
CIS 4.0 for Azure will also be added soon, as well as CIS 5.0 for Microsoft 365
Cheers,
This issue has been automatically marked as stale because it has not had recent activity. We kindly ask you to check again if the issue you reported is still relevant in the current version of Monkey365. If it is, update this issue with a comment, otherwise it will be automatically closed if no further activity occurs. Thank you for your contributions.
This issue was closed because it has been inactive for 14 days since being marked as stale. If the issue is still relevant, feel free to re-open it or open a new one.