Remote Access / Network

PuTTY + SSH + RDP Investigation

A simulated investigation of suspicious remote-access tooling with emphasis on user intent, authentication, destination analysis and potential lateral movement.

ALERT→USER/HOST→PROCESS→PUTTY/SSH/RDP→DESTINATION→AUTH→LATERAL MOVEMENT→CONTAIN
▶

Video walkthrough pending

Upload your walkthrough to YouTube as Unlisted, then replace YOUR_YOUTUBE_ID in this page to embed it here.

Investigation Timeline

How I would work the incident.

PuTTYSSHRDPSIEMFirewall LogsAuthentication Logs
ALERT

Confirm host, user, detection source, time, severity and whether remote-access behavior is expected.

PROCESS

Review process tree, command line, binary path, signer, execution user and related processes.

DESTINATION

Identify remote IP/hostname, port, protocol, direction, reputation and whether it is internal or external.

AUTHENTICATION

Correlate SSH/RDP/VPN and identity events with the same user, host and timeline.

LATERAL MOVEMENT

Look for subsequent connections to additional internal systems, credential use and remote session creation.

SCOPE

Search for the same tools, destinations, accounts and IOCs across other hosts.

CONTAIN

Terminate unauthorized sessions, isolate affected systems and disable or reset compromised accounts where supported.

VALIDATE

Confirm no active sessions, repeated connections or new lateral movement after containment.

Key Findings

Evidence that drives the decision

  • Remote-access software is not malicious by itself; context, authorization and destination determine risk.
  • Authentication and process telemetry should line up with network evidence.
  • Unexpected internal hops can indicate lateral movement and increase incident scope.
  • Containment should preserve evidence while preventing continued access.
Response

Contain → Eradicate → Validate

  • Contain the affected user, host, account, connection, or IOC based on confirmed evidence.
  • Remove malicious artifacts, persistence, unauthorized sessions, or access paths.
  • Re-scan and re-check telemetry to confirm suspicious activity has stopped.
  • Document the timeline, evidence, business impact and response actions.
  • Use lessons learned to tune or create detections for similar behavior.
Lab disclosure: This case study is presented as a simulated/home-lab investigation for portfolio demonstration.