Network hardening is the practice of reducing a service’s exposure by limiting who can reach it and what they can do once connected. For a database, that often means binding the service to trusted interfaces only, blocking unnecessary ports, enforcing authentication, and restricting traffic with firewalls, allowlists, or network segmentation. The goal is to shrink the attack surface before an attacker can probe it.
It matters because many breaches begin with an exposed service that should never have been reachable from the public internet or from untrusted internal networks. Hardening helps stop scans, brute-force login attempts, exploitation of management interfaces, and lateral movement after a foothold elsewhere in the environment. In defense, it works best alongside patching and access control: even if a flaw exists, a hardened network path can keep it out of reach. In practice, good hardening means only the systems and users that truly need access can see the service.