Skip to content

Commit 5316bc1

Browse files
authored
Merge pull request #21 from chouma/add-opentide
Add OpenTide
2 parents ad786bd + 30bb810 commit 5316bc1

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

README.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,7 @@ All contributions are welcome, please carefully review the [contributing guideli
2828
- [Elastic's Detection Engineering Behavior Maturity Model](https://www.elastic.co/security-labs/elastic-releases-debmm) - Elastic's qualitative and quantitative approach to measuring threat detection program maturity.
2929
- [Prioritizing Detection Engineering | Ryan McGeehan](https://medium.com/starting-up-security/prioritizing-detection-engineering-b60b46d55051) - A longtime detection engineer outlines how a detection engineering program should be built from the ground up.
3030
- [Detection Engineering Field Manual | Zack Allen](https://www.detectionengineering.net/s/field-manual) - a series of posts exploring the various foundational components of Detection Engineering.
31+
- [Open Threat Informed Detection Engineering aka OpenTide'](https://github.com/OpenTideHQ) - an all-in-one Detection Engineering Operations framework created and maintained by the European Commission to convert your CTI into an actionable detection coverage graph combining threat vectors with detection objectives, and manage your entire detection library from a central repository with a detection-as-code deployment system. The OpenTide format aims at measuring and expanding detection coverage, and its rule deployment engine is fully extensible and support multiple platforms in parallel (leveraging all the technology features and native query language). OpenTide works both within a single DE team as a main framework, and across SOC as a common format to facilitate data interexchange.
3132

3233
## Detection Content & Signatures
3334

0 commit comments

Comments
 (0)