Can blocking certain ports in Windows firewall enhance security, without affecting usability?
Would you recommend certain ports to be blocked to augment security?Yes, blocking certain ports can enhance security by reducing potential entry points for threats. However, it's important to know which ports to block, as some are necessary for certain applications to function properly. Always research before blocking a port.
Yes, blocking high-risk ports like port 23 (Telnet), port 135 (DCE/RPC), port 137-139 (NetBIOS), and port 445 (SMB) can augment security. However, it's crucial to understand the services your system needs before blocking any port.Would you recommend certain ports to be blocked to augment security?
NetBIOS and SMB are already disabled; should I block their ports?Yes, blocking high-risk ports like port 23 (Telnet), port 135 (DCE/RPC), port 137-139 (NetBIOS), and port 445 (SMB) can augment security. However, it's crucial to understand the services your system needs before blocking any port.
If NetBIOS and SMB are disabled and you're not using them, it's safe to block their ports. Port 80 (HTTP) and 53 (DNS) are commonly used for web browsing and DNS resolution, so blocking them could impact your internet usability. Always consider your network needs before blocking any port.NetBIOS and SMB are already disabled; should I block their ports?
What about port 80 and 53?
Using both from time to time; can be used to set a rule for blocking certain ports just as windows firewall.I don't know about blocking ports, but I think using a firewall software like Windows Firewall Control or a tool to configure Windows Filtering Platform (WFP) like simplewall will be easier to deal with.