Blocked Ports Still Show up on Nmap?
Btw I apologize if I sound kinda stupid, I'm not new to cyber security as a whole but I don't have much knowledge of the topic and how stuff works, but anyways; I was pen testing today and found open, vulnerable, ports on Nmap (those being 135, 139, 445, 53, 80, 443, and some other random ones), and on my Windows Defender Firewall settings I made inbound rules to block connections to those ports, but after running Nmap again, as well as "netstat -ano" the ports I thought I had closed were still in fact open (according to Nmap), and listening on cmd.
Is this normal? Is there something else I need to do to ensure my ports are closed?
Thanks for your understanding and your help!
Is this normal? Is there something else I need to do to ensure my ports are closed?
Thanks for your understanding and your help!
At Cyber Info, we strive to empower every individual with easy access to cybersecurity education
183,284Members
Resources
Similar Threads
Was this page helpful?
