CyberKit

Network ports

Port 22/tcp: SSH (Secure Shell) / SFTP / SCP

Category: File Sharing & Remote Access. Range: well-known. Status: iana registered.

What runs here

An encrypted remote-login and command-execution protocol (RFC 4251/4253) that also carries file transfer as SFTP and SCP subsystems over the same authenticated, encrypted session, plus arbitrary TCP port forwarding/tunneling. It is the de facto standard for administering Linux/Unix hosts and network appliances, and is increasingly available on Windows via OpenSSH.

Why it matters

SSH is the Unix/Linux/network-device equivalent of RDP for an intruder: a valid password or private key grants an interactive, encrypted shell, and because the session is encrypted end-to-end, network-level DFIR from packet capture is largely limited to metadata (who connected, when, for how long). The real evidence has to come from host-side authentication logs and, if configured, session logging. SSH's own persistence mechanism, planting a key in ~/.ssh/authorized_keys, is a well-documented technique in its own right.

Where you see it

Legitimately: system administration, automated deployment/CI over SFTP or SCP, git-over-SSH. Anomalously/maliciously: internet-facing SSH is one of the most continuously brute-forced services on the open internet; an attacker with any foothold may add their own public key to a user's authorized_keys file for persistence, or use SSH's built-in dynamic port forwarding (-D) as an improvised SOCKS proxy for further pivoting.

What to look for

Indicators
SignalWhat it means
sshd authentication log"Accepted password"/"Accepted publickey" versus repeated "Failed password" entries in auth.log/secure are the primary host-side record of who authenticated, from where, and by what method.
~/.ssh/authorized_keys modificationAn unexpected new key or an unexpected modification time on this file is the classic SSH persistence indicator (ATT&CK T1098.004).

ATT&CK techniques

Sources