For a PC that only needs basic internet access, for web browsers and updates, generally speaking, is there any need for incoming ports to be opened on the pc's firewall?
If outgoing port filtering is enabled on a pc's outgoing firewall, how do you determine the ports needed for the application? I guess there could be documentation\google\forum somewhere, but if not, is packet netstat\packet filtering the only way to go?
Does microsoft have a list of all the services that come in Windows that need network connectivity? like a list of them all. Because if outgoing connections are filtered, they need to each be whitelisted.
closed as too broad by Robert Mennell, LvB, WhiteWinterWolf, Steffen Ullrich, Stephane Jun 15 '16 at 8:43
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
- No. Incoming ports should only be whitelisted when the computer is intentionally providing a service to the outside world (e.g. web server, RDP, etc.).
- Yes, inspecting the traffic is the only way unless you already have an exhaustive list of software running on the machine and know which ports it relies on. However, this is generally not necessary for home users and extremely difficult to do correctly. If you are the user, it's far easier to educate yourself about avoiding malware. If you have other, less technical, people in the house, you may want to go the software firewall (e.g. ZoneAlarm) route and set it up to block everything by default (perhaps even require a password to whitelist, if that feature is offered).
- There are knowledge-base articles, but they may not be 100% lists. In any case, please refer to #2 before going this route.