Lion Cipher Lab

Work a MISP instance for real: ingest a feed, correlate events, and export IOCs your tools can actually consume

Why it matters

Most people who install MISP never actually use it. They stand up the containers, click through the demo event, and quietly go back to the spreadsheet — because setup is a tutorial problem and operating a threat-intelligence platform is a judgement problem, and nobody taught them the judgement. This lab is the second half. You will do the four things that make a MISP instance worth the RAM it eats: put real, well-typed intelligence in by hand; pull in a public feed so your data has something to collide with; read the collisions honestly, separating a genuine campaign link from two events that…

What you'll learn

Steps in this lab

  1. Recap in ninety seconds: get a MISP running (and skip this if yours is already up)
  2. The mental model: MISP is a graph, not a list of bad IPs
  3. Build an event by hand from a real public threat report
  4. Add the attributes — and treat to_ids as a decision, not a checkbox
  5. Tag it: TLP 2.0, a taxonomy tag, and a galaxy cluster
  6. Turn on a feed — and understand caching versus pulling before you click
  7. Correlation: the payoff, the noise, and the warninglists that separate them
  8. Search like an analyst: the UI first, then the REST API
  9. Export to things that actually enforce — then wire one in
  10. Indicator lifecycle: why every IOC has a shelf life
  11. Sharing: distribution levels, synchronisation, and the trust you are actually spending
  12. When you actually need this — MISP, OpenCTI, or an honest spreadsheet

Open the full interactive lab →