A Collective CTI Doctrine
summary
A federated CTI program builds a 60-rule Doctrine and uses OpenCTI + STIX + MISP to force graph‑based, atomic objects from public blog posts and vendor writeups, converting hundreds of posts into structured indicators and relationships. About 650 people across the CampusCyber communities prototype and share outputs (24 commons produced), the effort takes two years, enforces TLP and PAP tagging, and yields a working central repository that improves analyst time but still needs final governance and licensing rules.
AI-written summary · about
chapters (7)
- 0:00Compus Cyber CTI intro
- 6:12Need for collective CTI
- 10:25Goals for shared CTI
- 15:09Methodology for collective CTI
- 20:32CTI platform selection
- 24:30Key takeaways
- 27:42Q&A
related talks
22mSolving CTI Sector Incoherence in a Living Growing OpenCTI Repository: Extend STIX 2.1 FTW
27mStandard Classification: Connecting the Dots: How Threat Intelligence Protect...
30mHow to Create Effective Structured Intelligence Extensions for TIPs
30mCTI-Transmute: Harmonizing Threat Intelligence in a Multi-Standard Ecosystem
32mTen Years of Cyber Threat Intelligence: Retrospectives
43mCyber Threat Intelligence (Experts recommendations to enhance your security posture)
26mScaling cyber threat intelligence sharing with the AUS Cyber Security Center
28mCyber Threat Intelligence Analysts and You
