OBJECTIVE

Compare a supplied indicator list with local synthetic events while controlling false matches.

TIME PLAN

Prepare 20m · Build 110m · Verify 30m · Document 20m

Working boundary

Work only inside the folder created by Smartphone-Academy.py prepare ioc-matching. Use the supplied samples or systems you personally administer.

Prepare the Termux workspace

Open Termux in the Academy root and prepare this lab with the local companion. It creates safe samples, notes and evidence files under your Termux account.

Android + Termuxpython Smartphone-Academy.py prepare ioc-matchingNo root. Use the supplied files and keep the workspace under $HOME.

Practical mission

  1. Validate and normalize domains, addresses and hashes
  2. Use exact matching where substring matching is unsafe
  3. Attach surrounding event context to every hit
  4. Explain why an indicator match is a lead rather than a verdict
EVIDENCE TO PRODUCE

A match report with normalization rules, context and confidence.

Quality gate

The deliverable states a clear scope and date for Match Indicators Carefully.
A second learner can reproduce the commands and paths.
Original samples remain unchanged and verifiable.
Limitations are recorded beside the conclusions.

Analyst reflection

Which result from “Explain why an indicator match is a lead rather than a verdict” would need more evidence before it could support an operational decision?

Complete in Termux

After checking the evidence, run python Smartphone-Academy.py complete ioc-matching. Progress is stored locally in the Termux home directory.

14 · Defensive Monitoring

Continue learning

Back to Smartphone Academy