port 22, 53 expose on nmap
Posted: Wed Dec 25, 2024 6:44 am
Hi All,
I have stopped service for rpcbind and uhttps, so that it won't show on nmap.
Can someone please advise if we can prevent exposing these ports 22, 53 on the wan side? I have scan my external ip and these ports are exposed.
can we allow port 22 and 53 to be internal network only.
=========================
Host is up (0.0026s latency).
Not shown: 996 closed tcp ports (reset)
PORT STATE SERVICE
22/tcp open ssh
53/tcp open domain
=========================
Thanks
I have stopped service for rpcbind and uhttps, so that it won't show on nmap.
Can someone please advise if we can prevent exposing these ports 22, 53 on the wan side? I have scan my external ip and these ports are exposed.
can we allow port 22 and 53 to be internal network only.
=========================
Host is up (0.0026s latency).
Not shown: 996 closed tcp ports (reset)
PORT STATE SERVICE
22/tcp open ssh
53/tcp open domain
=========================
Thanks