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

Microsoft Windows 10 / BSI Benchmark SiSyPHuS 4.2.3.3 always compliant #516

Closed
PfeilImKopf opened this issue Mar 5, 2024 · 2 comments
Closed
Assignees
Labels
patch Includes bug fixes, focusing on enhancing stability.
Milestone

Comments

@PfeilImKopf
Copy link
Collaborator

Regardless of the path chosen for the firewall logging, the AuditTap consistently reports compliance.

@PfeilImKopf
Copy link
Collaborator Author

This may apply to other rules as well!

@TuemmlerKelch
Copy link
Collaborator

The proper implementation would look like this:

Change the helper function to abide these prerequisites:
A - Reg-Path and Value have to exist. Last part of value (filename) itself is irrelevant as long as it ends with .log
B - Add a check that makes sure the three firewallprofiles (public, private, domain) do not log into the same file. If two or more profiles log into the same file, this should lead to a warning with the following text: For better organization and identification of specific issues within each profile consider using separate logfiles for each profile.

@TuemmlerKelch TuemmlerKelch added the patch Includes bug fixes, focusing on enhancing stability. label Mar 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
patch Includes bug fixes, focusing on enhancing stability.
Projects
None yet
Development

No branches or pull requests

3 participants