From 0bee3ac821ffb862b3cd18e324119f85fee6008f Mon Sep 17 00:00:00 2001 From: Smriti <152067238+smriti0321@users.noreply.github.com> Date: Thu, 25 Apr 2024 12:40:17 +0200 Subject: [PATCH] Update 0000-rfc-template.md Incorporating review comments. --- rfcs/0000-rfc-template.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/rfcs/0000-rfc-template.md b/rfcs/0000-rfc-template.md index 82f0b5c488..d2770cdef4 100644 --- a/rfcs/0000-rfc-template.md +++ b/rfcs/0000-rfc-template.md @@ -27,8 +27,8 @@ Stage X: Provide a brief explanation of why the proposal is being marked as aban The `rule` fields being proposed are as follows: Field | Type | Description /Usage --- | -- | -- | -- | -- -rule.tags | array | Used to track the set of tags applied to a rule | Customers can use it to indicate: author, benchmark partial name, rule number, rule category etc. It will be useful when we extend the capability to add more rules +-- | -- | -- + rule.remediation | array | Used to capture remediation instructions that come from the benchmark / framework the rule is from -EPIC with detailed discussion on addition of these fields - https://github.com/elastic/security-team/issues/7658 + ### RFC Pull Requests