InfraGuard

Port exposure risks

What each well-known port is, why exposing it to the internet is risky, and how to close it down.

File share

File-sharing ports: SMB, NFS, FTP, rsync.

Remote admin

Direct server-control access: SSH, RDP, Telnet, VNC, WinRM.

Mail

SMTP·IMAP·POP3 and their secure variants (SMTPS·IMAPS).

DNS

Domain name resolution (53/tcp·udp).

DHCP

Automatic IP assignment (67·68).

Web

HTTP/HTTPS plus alternate web ports like 8080/8443/8000.

Directory

Account/authentication directories such as LDAP and Kerberos.

RPC

Remote-procedure-call mappers such as rpcbind/portmapper.

Time (NTP)

Time synchronization (123/udp).

Monitoring

Observability / management UIs: SNMP, Syslog, Prometheus, Grafana.

VPN

Secure tunnels such as OpenVPN, IPsec, WireGuard.

Datastore

Ports where databases (MySQL, PostgreSQL, MongoDB, Oracle …) accept direct connections.

Container

Orchestration ports: Docker API, Kubernetes API, Kubelet.

Proxy

Forward/reverse proxy ports such as Squid.

Message queue

Message brokers such as RabbitMQ or Kafka.

Cache

In-memory stores such as Redis and Memcached.

Search engine

Search/index engines like Elasticsearch or OpenSearch.

Track these versions on your own servers

InfraGuard collects installed software versions from every server and flags the ones with known vulnerabilities. Self-hosted — nothing leaves your network.

Weekly exploited-vulnerability digest

The KEV additions that matter for self-hosted servers, once a week. No other mail.