📎 AI Summary:
The thread discusses configuring Windows Firewall outbound rules, specifically why setting service customization to "apply to services only" doesn't work for executables like Internet Explorer. The original poster seeks clarification on restricting firewall rules further but discovers that Windows treats programs and services differently, with services running outside interactive sessions. Respondents clarify that services are also programs and point out limitations in restricting inter-process communication, suggesting that firewall rules primarily control network traffic rather than local process interactions. The overall sentiment is technical clarification, highlighting the nuances of Windows Firewall configurations.

Masao

New Member
Joined
May 31, 2017
Messages
13
Thread Author #1
The outbound rules allowed in windows firewall require the service customization to be set to allow all programs and services.

Any reason this doesn't work for "apply to services only" for an executable such as internet explorer? Is there some other program that is needed?

The security audit log in event viewer doesn't show anything new whether I set to "allow all programs and services" or "services only"; except it allows for "all" and blocks for "services only". Any other auditing or event logs I can look at?
 

Last edited:
Solution
Not really sure I understand what you're trying to accomplish. There is very little distinction between a program and a service. They are both technically programs. Services simply run outside the interactive session and can't directly interact with the interactive session and can also run without the interactive session in use (someone logged in). Inter process communication can't be blocked by a firewall since it's not network traffic. There is nothing from preventing say a malicious service from running a local application that in turns communicates out if that program is allowed. As far as the firewall is concerned in your scenario "allow all programs" is satisfied.

Masao

New Member
Joined
May 31, 2017
Messages
13
Thread Author #3
Agreed. Is the setting for "all programs and services" just a self-reference. I don't understand why I can't select all services or a single service.
 

Last edited:

Masao

New Member
Joined
May 31, 2017
Messages
13
Thread Author #4
From the audit log, windows filtering blocks the process (PID) for the .exe selected for the firewall rule without all programs and services selected in service customization.

I created another rule for the executable that blocked all services. So between the two rules my service customization becomes "allow all programs and no services.

Does that mean that any program can call the executable for communication through the firewall but no services can? If so, is there anyway to restrict that further to allow no other executables but the one referenced?
 

Last edited:

Neemobeer

Windows Forum Team
Staff member
Joined
Jul 4, 2015
Messages
8,995
Not really sure I understand what you're trying to accomplish. There is very little distinction between a program and a service. They are both technically programs. Services simply run outside the interactive session and can't directly interact with the interactive session and can also run without the interactive session in use (someone logged in). Inter process communication can't be blocked by a firewall since it's not network traffic. There is nothing from preventing say a malicious service from running a local application that in turns communicates out if that program is allowed. As far as the firewall is concerned in your scenario "allow all programs" is satisfied.
 

Solution