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

Category Windows Firewall clarification #29

Closed
FLeven opened this issue Jan 29, 2023 · 8 comments
Closed

Category Windows Firewall clarification #29

FLeven opened this issue Jan 29, 2023 · 8 comments
Assignees

Comments

@FLeven
Copy link

FLeven commented Jan 29, 2023

Why are the settings in the registry path:
HKLM:\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\DomainProfile

also checked ? For a compliance check SOFTWARE\Policies\Microsoft\WindowsFirewall should be enough?

@0x6d69636b
Copy link
Member

I noticed during testing that the values are sometimes different, so I am doing a double check. This may happen if the settings were changed via GUI before group policies were applied. Depending on whether local settings are taken over/merged, this could have an influence. I have not yet tested how it is under Windows 11. Better safe than sorry ;-)

@0x6d69636b 0x6d69636b self-assigned this Jan 29, 2023
@FLeven
Copy link
Author

FLeven commented Jan 29, 2023

ok, but we are not able to see if we are 100% compliant anymore, which is not a good thing. Maybe create a test list for yourself, the lists should never include anything else then the original baselines we are testing against.

@0x6d69636b
Copy link
Member

0x6d69636b commented Jan 30, 2023

Okay, I hear you. But that would not only affect the Windows Firewall config but also ASR (Registry and MPPreference Check) and Services (for CIS benchmarks), is this an issue as well?

I have added the checks to detect a potential discrepancy which in my eyes offers added value to a " simple" compliance check.

For which use cases exactly do you use HardeningKitty and how did you come across the issue?

@FLeven
Copy link
Author

FLeven commented Jan 31, 2023

HardeningKitty is my replacement for the .... ms policy analyzer, I deploy all the important Microsoft product baselines to my domains and check with HardeningKitty if they stay in there original state.

Then, I decide if I will implement more strict policys, like BSI, CIS, dod etc.

Extra checks are a good idea, but I would prefer them to be separated, from the official ones. As this tools is for compliance/security checks, the confusion of what is in each of the lists/checks should be kept to a minimum. If the description reads "ms win11 22h1 machine", it should contain onlz the corresponding policy settings version 22h1 from the ms download.
I also believe there are more people that need a replacement for the policy analyzer, because it might be deprecated already and has problems on non US lang OS. I also mentioned HardeningKitty on the policy analyzer forum,.

Next would be to do some lists for any custom policys that have to be implemented and maybe add Citrix:
https://www.citrix.com/about/legal/security-compliance/common-criteria.html

@FLeven
Copy link
Author

FLeven commented Jan 31, 2023

All other settings are fine, besides the one I reported in other issues. Firewall has 12 items notset/conflicting.

@0x6d69636b
Copy link
Member

Don't worry, I haven't forgotten about the issue. I have a lot to do at the moment and would like to test the firewall history properly (do local settings have an effect or does the GPO always take effect). I will be back

@FLeven
Copy link
Author

FLeven commented Feb 8, 2023

No hurry, I disable local FW rules entirely, then you can only set FW rules by GPs. This way, I am 100% sure my settings always win and not even local admins can add rules or overwrite anything.

@0x6d69636b
Copy link
Member

I removed the local Windows Firewall settings in the Microsoft Security Baseline lists in the development repo and it will be updated here in the next update.

@FLeven FLeven closed this as completed Feb 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants