Alert queue

Connecting…

Clear
Alert queue, sorted by severity then recency
SeverityCategorySource IPSensorReasoningReceived
S4successful_intrusion2.57.122.168hp-use-01The session shows a successful SSH login using weak credentials (root/123), which constitutes a foothold on the honeypot. Per rubric, any successful login is at
S4successful_intrusion120.48.0.142hp-use-01The session shows a successful SSH login using root/ubuntu, which constitutes a foothold on the honeypot and maps directly to successful_intrusion. Per tool out
S4successful_intrusion193.32.162.84hp-use-01The session shows a successful SSH login to the honeypot using root/111111, which constitutes a foothold. Per rubric, any successful login is at least severity
S4successful_intrusion193.32.162.84hp-use-01The session shows a successful SSH login to the honeypot using root/!root, which constitutes a foothold. Per rubric, any successful login is at least severity 4
S4successful_intrusion50.114.172.201hp-use-01A successful SSH login occurred using root/ubuntu, which establishes a foothold on the honeypot. Per the rubric, any successful login is at least severity 4 and
S4successful_intrusion117.50.119.132hp-use-01The session shows a successful SSH login using root/ubuntu, which constitutes a foothold on the honeypot. Per the rubric, any successful login is at least sever
S4successful_intrusion149.233.152.179hp-use-01A successful SSH login occurred using default Raspberry Pi credentials (pi/raspberry), which establishes a foothold and meets severity 4 by rubric. Tool output
S4successful_intrusion149.233.152.179hp-use-01A successful SSH login occurred using username 'pi', which establishes a foothold on the honeypot. Per rubric, any successful login is at least severity 4 and f
S4successful_intrusion157.151.29.21hp-use-01The session shows a successful SSH login using root/ubuntu, which constitutes a foothold on the honeypot. Per rubric, any successful login is at least severity
S4successful_intrusion195.178.110.217hp-use-01A successful SSH login occurred using root:1234, which constitutes a foothold on the honeypot. Per rubric, any successful login is at least severity 4 and falls
S4successful_intrusion195.178.110.217hp-use-01The session shows a successful SSH login to the honeypot using root:123123, which establishes a foothold and meets the severity-4 rubric. Retrieved session comm
S4successful_intrusion195.178.110.217hp-use-01A successful SSH login occurred using root/111111, which establishes a foothold and meets the severity-4 rubric. Per tool output, there were no post-login comma
S4successful_intrusion195.178.110.217hp-use-01A successful SSH login occurred using root/!root, which constitutes a foothold on the honeypot. Per rubric, any successful login is at least severity 4 and fall
S4successful_intrusion2.57.122.74hp-use-01A successful SSH login occurred using root/password1, which establishes a foothold on the honeypot. Per the rubric, any successful login is severity 4 even if n
S4successful_intrusion2.57.122.74hp-use-01The session shows a successful SSH login to the honeypot using root/1234567890. Per rubric, any successful login constitutes a foothold and maps to successful_i
S4successful_intrusion101.91.114.194hp-use-01The session shows a successful SSH login using root/ubuntu, which establishes a foothold and meets the severity-4 threshold. Tool output confirms there were no
S4successful_intrusion120.48.52.177hp-use-01A successful SSH login occurred using root/ubuntu, which constitutes a foothold on the honeypot and meets severity 4 by rubric. Session command retrieval shows
S4successful_intrusion193.32.162.84hp-use-01A successful SSH login occurred using root/123, which constitutes a foothold on the honeypot and meets severity 4 by rubric. Post-login evidence shows no comman
S4successful_intrusion193.32.162.84hp-use-01A login succeeded with root/111111, which establishes a foothold on the honeypot and meets the severity-4 rubric. Retrieved session commands show no post-login
S4successful_intrusion125.82.67.84hp-use-01The session shows a successful SSH login to the honeypot using root:10101984. Per rubric, any successful login constitutes a foothold and maps to successful_int
S4successful_intrusion125.82.67.84hp-use-01The session shows a successful SSH login to the honeypot using root/130287, which constitutes a foothold. Per rubric, any successful login is severity 4 and cat
S4successful_intrusion125.82.67.84hp-use-01A successful SSH login occurred using root with password 141087, which constitutes a foothold on the honeypot. Per rubric, any successful login is at least seve
S4successful_intrusion125.82.67.84hp-use-01A successful SSH login occurred using root/150989, which establishes a foothold on the honeypot. Per rubric, any successful login is at least severity 4 and fal
S4successful_intrusion125.82.67.84hp-use-01The session shows a successful SSH login to the honeypot using root/181181. Per rubric, any successful login constitutes a foothold and maps to severity 4 and c
S4successful_intrusion125.82.67.84hp-use-01The session shows a confirmed successful SSH login to the honeypot using root with password authentication. Per rubric, any successful login constitutes a footh