Code literacy: Identify Python, Bash, PowerShell, JavaScript, Java, C/C++ in logs and investigations. You don't need to write code — you need to recognize it when it appears in evidence. Codecademy · freeCodeCamp · Harvard CS50
Insider threat analysis is high-stakes, low-base-rate work. The biases that trip us up aren't exotic — they're the ones we use every day without noticing. Training on these is not optional.
Free training: Harvard — Critical Thinking & Argument · CIA — Psychology of Intelligence Analysis (PDF) · Coursera — Critical Thinking
Each quote demonstrates the bias it describes. Can you name them all before clicking?
You can't improve what you don't measure. These frameworks provide structured approaches to assessing program maturity, identifying gaps, and building evidence-based roadmaps for improvement.
AI is reshaping insider threat operations at every level — from automated triage to behavioral modeling to workforce planning. "Digital employee" isn't metaphor; it's how mature programs think about AI agents that augment analyst capacity.
Hover for definitions.
■ Detection ■ Monitoring ■ Protection ■ Investigation ■ Assessment ■ Management
Start with your SIEM. Learn the query language (SPL, KQL, or Lucene). Get comfortable with your EDR console. Layer DLP data as a source, not a program. Beyond tools, build sysadmin and network fundamentals — IAM, data movement patterns, privilege escalation paths. The tools change every budget cycle; the concepts don't.
Minimum viable toolstack: SIEM + EDR + DLP + IAM + case management. Cover detection, protection, and tracking with what you have.
Growing program: Add UEBA, UAM, PAM, CASB, a TIP, and structured risk assessment. This is where behavioral analytics transform your program.
Mature additions: NDR, CSPM, data classification, deception, SOAR, comms monitoring, forensic imaging. Layer these when you have the staff to operate them.
Open-source starter stack: Elastic SIEM + Wazuh (EDR) + TheHive (case mgmt) + MISP (TIP). Production-grade and zero licensing cost — just bring ops time.
The collection and analysis of publicly available information to produce actionable intelligence. OSINT is a discipline, not a Google search — it requires methodology, legal awareness, evidence preservation, and operational security.
⚠ OPSEC reminder: OSINT investigations require managed attribution (non-attributable accounts, VPNs, separate infrastructure). Your collection activity is itself observable. Sock puppet hygiene, legal boundaries, and evidence preservation methodology are not optional — they're prerequisites. Covered in SANS SEC487, Tulane cert, and OSINT Academy.
■ Cyber/tech ■ Intelligence ■ Physical security ■ Human/organizational ■ Legal
Linked roles go to NICCS work role descriptions. KSAs from adjacent roles appear with purple tags in the KSA panel.
Fields flow into PDF and job description exports.