Linux SSH hardening baseline that does not lock you out

Why this matters

SSH is often the last administrative door left open when every other management plane is broken. The useful baseline is not 'turn everything off'; it is to keep key-based access working, remove password and root-login paths, and test syntax before the daemon reloads.^{[source-1, source-2]}

Prescriptive baseline

PermitRootLogin no
PasswordAuthentication no
KbdInteractiveAuthentication no
PubkeyAuthentication yes
MaxAuthTries 3
AllowTcpForwarding no
X11Forwarding no

sudo sshd -t
sudo systemctl reload ssh || sudo systemctl reload sshd
ssh -o PreferredAuthentications=publickey admin@example-host

Rollback and evidence

BlackShield context

BlackShield can keep this as owner-assigned remediation work with validation evidence attached, rather than a one-off hardening note that disappears after the maintenance window.

Affected systems and scope

Treat this topic as a scoping exercise before it becomes a queue of tickets. The systems in scope include Linux servers, bastion hosts, cloud VMs, administrative jump boxes, emergency access paths, and monitored SSH daemon configuration. Inventory alone is not enough: the responder has to know whether the asset is production, externally reachable, ownerless, business critical, or covered by an accepted exception. That context prevents a shallow severity score from driving every decision and lets teams separate urgent exposure from routine hardening work.^{[source-1, source-2, source-3]}

Exposure path

The exposure path is the chain that turns a public recommendation into tenant risk: SSH risk increases when password authentication, root login, forwarding, weak retry limits, or unmanaged configuration drift remain available on reachable hosts. A good investigation writes that chain down in plain language, including what is verified, what is assumed, and what still needs a bounded check. That discipline matters because teams often over-rotate on the public headline while missing the local preconditions that decide whether immediate remediation, temporary isolation, or planned maintenance is the right response.^{[source-1, source-2, source-3]}

Detection and triage

Detection should start with evidence that can be repeated by another operator. For this topic, sshd configuration, authentication logs, running daemon state, Wazuh or OSSEC alerts, package posture, and failed-login patterns should be reviewed before and after rollout. Triage is stronger when it records negative evidence as well as positive matches, because a clean result from one scanner may only mean that the scanner could not see a host, region, namespace, package manager, or runtime path. The response owner should preserve enough context for a later reviewer to understand why the finding was prioritized, deferred, or closed.^{[source-1, source-2, source-3]}

Investigation workflow

A mature response should move through the same sequence even when the topic feels urgent: confirm the asset set, confirm the risky condition, confirm reachability, confirm ownership, choose the response path, and capture validation evidence. The order matters. Teams that jump straight to patching can miss unsupported assets, regional copies, unmanaged hosts, old containers, or exceptions that need leadership approval. Teams that stay in analysis too long can leave a reachable weakness open while arguing over perfect certainty. The workflow should make the next bounded action obvious.^{[source-1, source-2, source-3]}

Compensating control review

Compensating controls are useful when they materially change attacker opportunity, not when they merely postpone a difficult change. For SSH risk increases when password authentication, root login, forwarding, weak retry limits, or unmanaged configuration drift remain available on reachable hosts, the control review should ask whether the risky path is now unreachable, less privileged, more observable, or isolated from sensitive data and production dependencies. The review should also name the expected failure mode: what signal would show that the temporary control stopped working, and who is accountable for reacting before the exception expires.^{[source-1, source-2, source-3]}

Operational handoff

The handoff from security to engineering should be specific enough that the assignee can act without reverse-engineering the advisory. Include the affected resource, the observed evidence, the required change, the validation command or scanner check, the rollback note, and the deadline. If a team rejects the recommendation, capture the reason and compensating control in the same record. That makes risk acceptance visible as a managed decision rather than an unresolved comment thread.^{[source-1, source-2, source-3]}

Remediation and compensating controls

The remediation plan should be short enough to execute and specific enough to audit. In this case, rollout should preserve an open session, test syntax, verify key-based non-root access, and stage changes through lower-risk host groups before broad enforcement. If the preferred fix cannot land immediately, the compensating control should reduce reachability, reduce privilege, increase monitoring, or isolate the affected component while keeping an owner and expiry date attached. Temporary controls are useful only when everyone can see that they are temporary and when the validation step proves they still cover the risk.^{[source-1, source-2, source-3]}

Operational pitfalls

Validation evidence

Validation is where a security update becomes an operationally useful record. For this article, operators should keep sshd test output, the drop-in file, reload timestamp, successful key-based login proof, and monitoring evidence for rejected password attempts. The evidence should be durable enough to survive a staff change, an audit request, or an incident review months later. A screenshot may help, but machine-readable output, ticket links, scanner run identifiers, command transcripts, and timestamps are easier to compare across teams and reruns.^{[source-1, source-2, source-3]}

Archive quality

Forward-looking public articles should remain useful after the first news cycle. That means the reader should be able to understand the issue, decide whether it applies, choose a bounded first probe, see what evidence matters, and avoid predictable rollout mistakes. Short posts can announce that something happened; a research archive should help a defender make and justify an operational decision. This is why new automated and checked-in articles carry the 8-minute floor while older remote posts remain valid at their original URLs.^{[source-1, source-2, source-3]}

Prioritization and ownership

Priority should be a function of verified exposure, business consequence, exploit maturity, and the cost of delay. A queue sorted only by severity tends to hide the work that needs immediate coordination, while a queue sorted only by scanner freshness rewards noisy tools. The owner should see why the task is urgent, what evidence supports that urgency, which control is expected, and how closure will be judged. When that information is missing, the first assignment should be investigation, not remediation theater.^{[source-1, source-2, source-3]}