Open Common Requirement Enumeration (OpenCRE)
summary
A live demo shows a working open catalog that maps standards into a graph via one common requirement ID so links replace exponential pairwise mappings; the database hosts 600+ CREs and already maps ISO 27001 ASVS OWASP Top10 and tool findings. Features include retrieval‑augmented answers from an OpenCRE chat, visual map/gap analysis, and containerized local deployments that sync with upstream. The claim is concrete: searchable, referenceable requirements, programmatic mappings, and usable gap reports that demonstrably run.
AI-written summary · about
chapters (22)
- 0:00OpenCRE introduction
- 1:28Problem with fragmented standards
- 5:49OpenCRE as solution
- 7:15What OpenCRE is
- 9:20OpenCRE database & mappings
- 10:25Live demo of OpenCRE
- 12:10Semantic web in cybersecurity
- 13:56Mapping new content challenge
- 15:45Fixing broken links dynamically
- 16:50OpenCRE chatbot intro
- 17:33Chatbot demo
- 19:21How chatbot works
- 20:46Map analysis for gaps
- 21:50Demo of map analysis
- 22:34Exploring the OpenCRE catalog in detail
- 23:14OpenCRE graph visualization
- 23:36Running OpenCRE locally
- 24:18Deploying OpenCRE privately
- 25:41Custom standards & contributions
- 26:02Why OpenCRE matters
- 27:27Q&A: Community involvement
- 28:54Q&A: Custom databases
related talks
28mThe future is simple - introducing the CRE
32mBridging Security & Privacy Standards: Harnessing OpenCRE for Effective Mapping
01h 51mOpen Interchange on CPE - Purl Between Communities of Interest and the CVE and NVD Programs
46mTurn CRA Awareness into Action
27mWhat's New in CSAF and OpenEoX
42mMaking EU CRA (Cyber Resilience Act) Simplified and Non-scary for OSS Contributors
31mOpen Source SCA
42mSecuring Software Supply Chains: OpenCode as Building Block for Sovereign Digital Infrastructure