Skip to content

SOC & Blue Team

Behind every serious company (tiers 3, 5 and 6) sits a hidden blue team: named SOC and incident-response analysts who sign the tickets on the intranet board and in the IT mailbox. They are the defenders you rarely see, and the hardest targets in the home pivot.

SOC analysts are real employees. Their accounts live on the company Domain Controller, so john on the DC’s /etc/shadow cracks them, and their real credentials authenticate the corporate VPN pivot.

They do not appear in the public staff roster or on FaceLink: a SOC handle shows as a minimal locked profile, never as a missing page.

The dox payoff: discover the SOC team from the Domain Controller’s roster and deliver it to an FTP dead drop. The roster names each analyst, their mobile number and a Base city, which is your lead for the next step.

A SOC analyst lives in a hardened home: pfSense, VLANs and an EDR-protected work laptop. It can be found through the ISP customer DB and DHCP-DNS, and SIGINT groups analysts by their Base city. The full chain:

  1. Breach the Domain Controller.
  2. Read the roster: name, mobile, Base city.
  3. SIGINT-sweep that city for the mobile number.
  4. Follow the broadband breadcrumb to the ISP.
  5. Dump the ISP’s customer DB for the home IP.
  6. Breach the hardened home.
  7. Recover the cached Domain Controller credentials from the work laptop.
  8. Pivot back into the company as the blue team itself.

If the SOC notices you, their firewall blocks your source IP on that box: a containment kick. It clears after a cooldown, or you route around it with failover or proxychains (a different apparent source). On monitored boxes the analysts also hunt you live; see When they fight back.