You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, when a new operating system is released, such as Windows Server 2025, how long does it usually take for the CSV file to become available in the Lists directory? Is there a way for us to find it ourselves, for example, in Microsoft's baseline security? Can I take it from Dev depot?
Thanks
The text was updated successfully, but these errors were encountered:
When a new operating system is released, such as Windows Server 2025, how long does it usually take for the CSV file to become available in the Lists directory?
After a new OS release and the release of benchmarks such as CIS or Microsoft Security Baselines, I'll create a finding list as soon as I find the time. It takes me several hours to create such a list, depending on the format (CIS PDFs are tedious) and the changes between releases. As this is a non-profit open source project, I do this on a best effort basis.
Anyone can use an existing list, compare the information with the CIS/MSFT documents, and then create a pull request with a proposal for a new list. Other ways to speed up the process is to provide me technical information such as registry keys, default values, recommended values, for both group policies and Intune.
Can I take it from Dev depot?
Yes, you can. In this case, you should also use the HardeningKitty version from the Dev repo. If you need a signed version of HardeningKitty, let me know. I release irregular versions in "prod", but most of the time I could sync the two repos without problems.
Hello, when a new operating system is released, such as Windows Server 2025, how long does it usually take for the CSV file to become available in the Lists directory? Is there a way for us to find it ourselves, for example, in Microsoft's baseline security? Can I take it from Dev depot?
Thanks
The text was updated successfully, but these errors were encountered: