![Lead Image © momo5287, 123RF.com Lead Image © momo5287, 123RF.com](/var/ezflow_site/storage/images/archive/2015/26/tcp-stealth-hides-open-ports/123rf_11959629_camouflage-mantis_momo5287_resized.png/110944-1-eng-US/123RF_11959629_Camouflage-Mantis_momo5287_resized.png_medium.png)
Lead Image © momo5287, 123RF.com
TCP Stealth hides open ports
TCP Camouflage
Finding open UDP or TCP ports on Linux is easy. Hardcore hackers use Netcat [1]. If you prefer an easier approach, you can use Nmap [2]. In addition to identifying active services, you can even profile the underlying operating system in many cases. In fact, a port scan can be a useful troubleshooting tool for an administrator's bottom line.
There is a dark side to port scanning, too, however. Unfriendly people can use the same methods to spy on IT systems. After identifying what are basically open doors, an attacker can start on other investigations. In a worst-case scenario, the attacker learns which version of which program is keeping a port open. A short search on the Internet for potential vulnerabilities or exploits is quickly accomplished.
Administrators can effectively block this attack vector by obfuscating the open ports. For an outsider, it looks as if there were no easy targets; only experts know how to gain access. Probably the best-known technology in this context is port knocking, and there are several implementations [3].
What Happened Thus Far
Figure 1 shows a typical setup with port knocking. The components involved here are the client and the server application, with a firewall to keep out uninvited guests and another process that waits for the agreed upon knock signal. This process is often known as the port knock daemon. The daemon and the clients have a shared secret. This can be a knock sequence or network packets with specific content.
...Buy this article as PDF
(incl. VAT)