Free sample lesson: what an auth log proves
This is the kind of lesson members get every week. Read the excerpt, then answer
one question: what does the evidence prove, and what is only suggested?
Nov 17 02:14:01 lab sshd[1421]: Failed password for root from 192.0.2.44 port 51234 ssh2
Nov 17 02:14:04 lab sshd[1421]: Failed password for root from 192.0.2.44 port 51238 ssh2
Nov 17 02:14:07 lab sshd[1421]: Failed password for root from 192.0.2.44 port 51244 ssh2
Nov 17 02:15:22 lab sshd[1430]: Accepted publickey for deploy from 192.0.2.44 port 51240 ssh2
Nov 17 03:02:44 lab sshd[1601]: Failed password for monitor from 198.51.100.10 port 40122 ssh2
Nov 17 03:07:44 lab sshd[1602]: Failed password for monitor from 198.51.100.10 port 40130 ssh2
Proved: sshd recorded three failed root logins and one accepted public-key
login for deploy, all from 192.0.2.44, within 81 seconds. It also recorded two
failed logins for monitor from 198.51.100.10, five minutes apart.
Suggested: the sequence is suspicious. The failures and the success share a
source address, and the timing is tight.
Not proved: that the key login was unauthorized. The key may belong to
deploy, and 192.0.2.44 may be its documented jump host. The monitor failures
may be a stale health check.
The next checks: the SSH key fingerprint, last -F -i deploy, the sudo log
for the same window, and whether 192.0.2.44 is the deploy host's normal source.
The full dataset, answer key and a model prompt are in Member Resources.
If you want the guided version, ask in Ask the Lab with your sanitized
excerpt and the check you already ran.