From 96a9ea5f68809b2b914d8cf7fb405e3a90c0bcbb Mon Sep 17 00:00:00 2001 From: Erwan Chevalier Date: Mon, 11 Mar 2024 09:11:15 +0100 Subject: [PATCH] fix(doc): old roadmap --- docs/xdr/FAQ/Detection_qa.md | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/docs/xdr/FAQ/Detection_qa.md b/docs/xdr/FAQ/Detection_qa.md index 5dfe15202b..9933e2a120 100644 --- a/docs/xdr/FAQ/Detection_qa.md +++ b/docs/xdr/FAQ/Detection_qa.md @@ -97,10 +97,4 @@ Here are the main steps involved in crafting Sekoia.io's verified detection rule - **Staging**: Once a rule has been successfully tested, it is moved to a staging environment. This is a production-like environment where the rule can be monitored for false positives before it is deployed to production. - **Approval**: If a rule performs well in staging, it is then approved for production deployment. -Sekoia.io is constantly working to improve its detection engineering process. Some of the improvements that we are planning include: - -- Requiring all rules to be in staging for two weeks before being deployed to production. -- Implementing an automatic check to ensure that rule mappings are up-to-date. -- Allowing partners and customers to contribute to the rule creation process. - -For more insights on how we create rules and how we test them, check our blogpost on that matter: [XDR detection engineering at scale: crafting detection rules for SecOps efficiency](https://blog.sekoia.io/xdr-detection-rules-at-scale/). \ No newline at end of file +For more insights on how we create rules and how we test them, check our blogpost on that matter: [XDR detection engineering at scale: crafting detection rules for SecOps efficiency](https://blog.sekoia.io/xdr-detection-rules-at-scale/).