Typorithm · medium

Investigator OPSEC

osint-opsecosintopsecsock-puppetattribution

Saved on this device

Full lesson · 8 learning steps Open any exercise for focused practice

Step 1 of 8 · intro card

Learn Investigator OPSEC

Foundations

Protect the investigation and yourself: use a dedicated research account and an isolated VM or VPN, never interact with or alert the subject, avoid logging into personal accounts that leak your identity, and record sources and timestamps so findings are defensible in the report.

OPSEC protects both the investigation and the investigator. Start with identity: use a dedicated research (sock-puppet) account, not your personal one, so your real self never appears in the trail you leave on a site.

Keep the work contained on the network side — a VPN or an isolated VM. Never contact or otherwise touch the target; OSINT is passive, and reaching out can tip off the subject or contaminate the evidence.

Guard attribution by avoiding logins that leak who you are, and record the source and a timestamp for every finding. Good records make the report defensible later, when someone asks where a fact came from.

Use a dedicated research account, not personal logins.

Work from a VPN or isolated VM; never contact the target.

Timestamp and cite every source for a defensible report.

opsec:
  identity: research-account-only
  network: vpn-or-isolated-vm
  no_contact: never-touch-target
  attribution: avoid-leaking-self
  records: timestamp-and-source

Read the implementation

Connect each part of the code to the concept before you type.

1. Identity

Use a dedicated research (sock-puppet) account, never your personal logins.

identity: research-account-only

2. Network

Work from a VPN or an isolated VM so the investigation is contained.

network: vpn-or-isolated-vm

3. No contact

Never interact with or alert the subject — passive collection only.

no_contact: never-touch-target

4. Attribution

Avoid logins or footprints that leak your real identity back to you.

attribution: avoid-leaking-self

5. Records

Record source and timestamp for every finding so the report is defensible.

records: timestamp-and-source

A complete learning loop

Understand

Read the concept map and follow the code breakdown.

Reconstruct

Type the implementation, repair mistakes and work through every recall exercise.

Verify

Use the final check without hints; revisit weak concepts in short practice sessions.