[RFC] Stage 0: Introducing new field in rule namespace #2330

smriti0321 · 2024-04-05T10:34:42Z

Updating the template for ECS RFC Stage 0 for adding 1 new rule fields:

rule.remediation

Have you signed the contributor license agreement? Yes
Have you followed the contributor guidelines? Yes
For proposing substantial changes or additions to the schema, have you reviewed the RFC process? Yes
If submitting code/script changes, have you verified all tests pass locally using make test?
If submitting schema/fields updates, have you generated new artifacts by running make and committed those changes?
Is your pull request against main? Unless there is a good reason otherwise, we prefer pull requests against main and will backport as needed.
Have you added an entry to the CHANGELOG.next.md?

Updating the temaplate for RFC Stage 0 for adding 2 new rule fields: rule.tags and rule.remediation

rfcs/0000-rfc-template.md

ebeahan

Left some initial comments.

ebeahan · 2024-04-08T15:29:52Z

rfcs/0000-rfc-template.md

@@ -97,6 +108,7 @@ e.g.:
 ## References

 <!-- Insert any links appropriate to this RFC in this section. -->
+EPIC with detailed discussion on addition of these fields - https:/elastic/security-team/issues/7658


I recommend removing any references to Elastic-only discussions or references. For anyone outside Elastic, these links will just return a 404 error.

If you want to link the two discussions, add a link on the private to the public.

ebeahan · 2024-04-08T15:31:04Z

rfcs/0000-rfc-template.md

+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 


How would this value be used as an array? From the description, I'd expect a block of text with the instructions?

There is possibility to have multiple remediation options for same misconfiguration, hence an array makes more sense. For example, we provide remediation manual steps, cli commands for CSPM misconfigurations.

@kfirpeled @maxcold thoughts on this? As @smriti0321 mentioned, from a product perspective, if there are multiple remediation options, we'd love to capture them all and present them in our flyout. From a technical perspective we can group all of these into one field we render as markdown, or as an array of values, etc. Can you help decide what the best path is here from a data type perspective? Thx!

Right now it's just a markdown text for our native integration, for Wiz it's also just a string. Unless we want to have a more complex structure for each remediation instruction, text should be enough as a type in my opinion.

There is possibility to have multiple remediation options for same misconfiguration, hence an array makes more sense. For example, we provide remediation manual steps, cli commands for CSPM misconfigurations.

I'm not sure I followed, currently, we don't have any examples of multiple remediation instructions. Can you please provide one?

and another FYI, it introduces a breaking change. so we need to think it through from a technical perspective as well

ebeahan · 2024-04-08T15:32:43Z

rfcs/0000-rfc-template.md

+
+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


ECS already provides a top-level tags field: https://www.elastic.co/guide/en/ecs/current/ecs-base.html#field-tags.

Could the existing tags field be used for the same purpose without creating another tags field?

This could be the right approach to reuse top-level tags to include rules tag.

rfcs/0000-rfc-template.md

clement-fouque

No comment from my side.

Incorporating review comments.

tinnytintin10

@smriti0321 it looks like you directly updated the RFC template file (rfcs/0000-rfc-template.md). Pls revert this change and create a new file in the rfcs/text folder.

tinnytintin10 · 2024-05-29T22:17:58Z

rfcs/0000-rfc-template.md

+
+Field | Type | Description /Usage
+-- | -- | -- 
+


The table isn't rendering. Removing this line break (31) will fix it.

tinnytintin10 · 2024-05-29T22:18:36Z

rfcs/0000-rfc-template.md

+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 


@kfirpeled @maxcold thoughts on this? As @smriti0321 mentioned, from a product perspective, if there are multiple remediation options, we'd love to capture them all and present them in our flyout. From a technical perspective we can group all of these into one field we render as markdown, or as an array of values, etc. Can you help decide what the best path is here from a data type perspective? Thx!

tinnytintin10 · 2024-05-29T22:40:17Z

@smriti0321 whats the plan for capturing benchmark/framework metadata? The existing rule.ruleset field has a type of keyword type that will only allow us to capture the benchmark/framework's name.

Change rule.ruleset to enable us to capture an array of objects. This might not be the right option as it will lead to break changes if this field is in use.
Introduce a new fieldset (ruleset?) to capture benchmark metadata. This would have to be an additional RFC.

For context, here is an example of a wiz findings that contains multiple mapped benchmarks/frameworks:

Just the benchmarks / frameworks

"securitySubCategories": [
    {
      "category": {
        "framework": { "id": "wf-id-115", "name": "UK Cyber Essentials" },
        "id": "wct-id-2360",
        "name": "1 Firewalls"
      },
      "id": "wsct-id-15168",
      "title": "1.1 Change default administrative passwords"
    },
    {
      "category": {
        "framework": { "id": "wf-id-13", "name": "NIST CSF v1.1" },
        "id": "wct-id-363",
        "name": "2 Business Environment (ID.BE)"
      },
      "id": "wsct-id-37",
      "title": "5 Resilience requirements to support delivery of critical services are established"
    },
    {
      "category": {
        "framework": { "id": "wf-id-13", "name": "NIST CSF v1.1" },
        "id": "wct-id-370",
        "name": "10 Information Protection Processes and Procedures (PR.IP)"
      },
      "id": "wsct-id-76",
      "title": "9 Response plans (Incident Response and Business Continuity) and recovery plans (Incident Recovery and Disaster Recovery) are in place and managed"
    },
    {
      "category": {
        "framework": { "id": "wf-id-13", "name": "NIST CSF v1.1" },
        "id": "wct-id-372",
        "name": "12 Protective Technology (PR.PT)"
      },
      "id": "wsct-id-689",
      "title": "5 Mechanisms (e.g., failsafe, load balancing, hot swap) are implemented to achieve resilience requirements in normal and adverse situations"
    },
    {
      "category": {
        "framework": { "id": "wf-id-14", "name": "CSA CCM v4.0.5" },
        "id": "wct-id-1062",
        "name": "5 - CEK Cryptography, Encryption \u0026 Key Management"
      },
      "id": "wsct-id-6165",
      "title": "CEK-01 Encryption and Key Management Policy and Procedures - Establish, document, approve, communicate, apply, evaluate and maintain\npolicies and procedures for Cryptography, Encryption and Key Management. Review\nand update the policies and procedures at least annually."
    },
    {
      "category": {
        "framework": { "id": "wf-id-14", "name": "CSA CCM v4.0.5" },
        "id": "wct-id-1074",
        "name": "17 - UEM Universal Endpoint Management"
      },
      "id": "wsct-id-6322",
      "title": "UEM-08 Storage Encryption - Protect information from unauthorized disclosure on managed endpoint\ndevices with storage encryption."
    },
    {
      "category": {
        "framework": { "id": "wf-id-48", "name": "NIST SP 800-53 Revision 4" },
        "id": "wct-id-1181",
        "name": "CM CONFIGURATION MANAGEMENT"
      },
      "id": "wsct-id-6836",
      "title": "CM-7 LEAST FUNCTIONALITY"
    },
    {
      "category": {
        "framework": { "id": "wf-id-1", "name": "Wiz for Risk Assessment" },
        "id": "wct-id-940",
        "name": "Operationalization"
      },
      "id": "wsct-id-10421",
      "title": "Informational configuration"
    },
    {
      "category": {
        "framework": { "id": "wf-id-13", "name": "NIST CSF v1.1" },
        "id": "wct-id-370",
        "name": "10 Information Protection Processes and Procedures (PR.IP)"
      },
      "id": "wsct-id-71",
      "title": "4 Backups of information are conducted, maintained, and tested periodically"
    },
    {
      "category": {
        "framework": { "id": "wf-id-3", "name": "ISO/IEC 27001" },
        "id": "wct-id-589",
        "name": "A.12 Operations security"
      },
      "id": "wsct-id-635",
      "title": "A.12.3.1 Information backup"
    },
    {
      "category": {
        "framework": { "id": "wf-id-14", "name": "CSA CCM v4.0.5" },
        "id": "wct-id-1061",
        "name": "4 - CCC Change Control and Configuration Management"
      },
      "id": "wsct-id-6164",
      "title": "CCC-09 Change Restoration - Define and implement a process to proactively roll back changes to\na previous known good state in case of errors or security concerns."
    },
    {
      "category": {
        "framework": { "id": "wf-id-105", "name": "Wiz (Legacy)" },
        "id": "wct-id-2136",
        "name": "Operationalization"
      },
      "id": "wsct-id-5540",
      "title": "Operationalization"
    }
  ]

Full finding

{
  "analyzedAt": "2024-05-29T01:03:24.600785Z",
  "firstSeenAt": "2024-05-29T01:03:26.815114Z",
  "id": "bb379d62-72bf-57c8-8e68-a043696a072b",
  "ignoreRules": null,
  "remediation": "To monitor an instance stop scheduled event for the EC2 instance, follow [this link](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/monitoring-instances-status-check_sched.html).\n",
  "resource": {
    "id": "72b98370-615e-5136-a614-71269ddef677",
    "name": "Demo vulns findings",
    "nativeType": "virtualMachine",
    "projects": [
      {
        "id": "83b76efe-a7b6-5762-8a53-8e8f59e68bd8",
        "name": "Project 2",
        "riskProfile": { "businessImpact": "MBI" }
      },
      {
        "id": "af52828c-4eb1-5c4e-847c-ebc3a5ead531",
        "name": "project 4",
        "riskProfile": { "businessImpact": "MBI" }
      },
      {
        "id": "d6ac50bb-aec0-52fc-80ab-bacd7b02f178",
        "name": "Project1",
        "riskProfile": { "businessImpact": "MBI" }
      }
    ],
    "providerId": "arn:aws:ec2:us-east-2:998231069301:instance/i-07602bddd9c7a3052",
    "region": "us-east-2",
    "subscription": {
      "cloudProvider": "AWS",
      "externalId": "998231069301",
      "id": "94e76baa-85fd-5928-b829-1669a2ca9660",
      "name": "wiz-integrations"
    },
    "tags": [{ "key": "Name", "value": "Demo vulns findings" }],
    "type": "VIRTUAL_MACHINE"
  },
  "result": "FAIL",
  "rule": {
    "description": "This rule checks whether there is an instance stop scheduled event for the EC2 instance.  \nThis rule fails if there is at least one `Events` element whose `Code` field is set to `instance-stop`.  \nThe event applies to instances backed by Amazon EBS. This event indicates that at the scheduled time, the instance is stopped, and when it is started again, it is migrated to a new host. Be aware of instance-stop scheduled events to avoid unexpected data loss and downtime.\n\u003e**Note**  \n\u003eThis rule does not indicate any misconfiguration and is informational only.",
    "functionAsControl": false,
    "graphId": "0dd0ca67-e17e-5e0d-b296-08ce779953f6",
    "id": "5076dc62-3fbd-4ee9-9495-3ca295aeac99",
    "name": "EC2 instance with an upcoming instance stop scheduled event",
    "remediationInstructions": "To monitor an instance stop scheduled event for the EC2 instance, follow [this link](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/monitoring-instances-status-check_sched.html).\n"
  },
  "securitySubCategories": [
    {
      "category": {
        "framework": { "id": "wf-id-115", "name": "UK Cyber Essentials" },
        "id": "wct-id-2360",
        "name": "1 Firewalls"
      },
      "id": "wsct-id-15168",
      "title": "1.1 Change default administrative passwords"
    },
    {
      "category": {
        "framework": { "id": "wf-id-13", "name": "NIST CSF v1.1" },
        "id": "wct-id-363",
        "name": "2 Business Environment (ID.BE)"
      },
      "id": "wsct-id-37",
      "title": "5 Resilience requirements to support delivery of critical services are established"
    },
    {
      "category": {
        "framework": { "id": "wf-id-13", "name": "NIST CSF v1.1" },
        "id": "wct-id-370",
        "name": "10 Information Protection Processes and Procedures (PR.IP)"
      },
      "id": "wsct-id-76",
      "title": "9 Response plans (Incident Response and Business Continuity) and recovery plans (Incident Recovery and Disaster Recovery) are in place and managed"
    },
    {
      "category": {
        "framework": { "id": "wf-id-13", "name": "NIST CSF v1.1" },
        "id": "wct-id-372",
        "name": "12 Protective Technology (PR.PT)"
      },
      "id": "wsct-id-689",
      "title": "5 Mechanisms (e.g., failsafe, load balancing, hot swap) are implemented to achieve resilience requirements in normal and adverse situations"
    },
    {
      "category": {
        "framework": { "id": "wf-id-14", "name": "CSA CCM v4.0.5" },
        "id": "wct-id-1062",
        "name": "5 - CEK Cryptography, Encryption \u0026 Key Management"
      },
      "id": "wsct-id-6165",
      "title": "CEK-01 Encryption and Key Management Policy and Procedures - Establish, document, approve, communicate, apply, evaluate and maintain\npolicies and procedures for Cryptography, Encryption and Key Management. Review\nand update the policies and procedures at least annually."
    },
    {
      "category": {
        "framework": { "id": "wf-id-14", "name": "CSA CCM v4.0.5" },
        "id": "wct-id-1074",
        "name": "17 - UEM Universal Endpoint Management"
      },
      "id": "wsct-id-6322",
      "title": "UEM-08 Storage Encryption - Protect information from unauthorized disclosure on managed endpoint\ndevices with storage encryption."
    },
    {
      "category": {
        "framework": { "id": "wf-id-48", "name": "NIST SP 800-53 Revision 4" },
        "id": "wct-id-1181",
        "name": "CM CONFIGURATION MANAGEMENT"
      },
      "id": "wsct-id-6836",
      "title": "CM-7 LEAST FUNCTIONALITY"
    },
    {
      "category": {
        "framework": { "id": "wf-id-1", "name": "Wiz for Risk Assessment" },
        "id": "wct-id-940",
        "name": "Operationalization"
      },
      "id": "wsct-id-10421",
      "title": "Informational configuration"
    },
    {
      "category": {
        "framework": { "id": "wf-id-13", "name": "NIST CSF v1.1" },
        "id": "wct-id-370",
        "name": "10 Information Protection Processes and Procedures (PR.IP)"
      },
      "id": "wsct-id-71",
      "title": "4 Backups of information are conducted, maintained, and tested periodically"
    },
    {
      "category": {
        "framework": { "id": "wf-id-3", "name": "ISO/IEC 27001" },
        "id": "wct-id-589",
        "name": "A.12 Operations security"
      },
      "id": "wsct-id-635",
      "title": "A.12.3.1 Information backup"
    },
    {
      "category": {
        "framework": { "id": "wf-id-14", "name": "CSA CCM v4.0.5" },
        "id": "wct-id-1061",
        "name": "4 - CCC Change Control and Configuration Management"
      },
      "id": "wsct-id-6164",
      "title": "CCC-09 Change Restoration - Define and implement a process to proactively roll back changes to\na previous known good state in case of errors or security concerns."
    },
    {
      "category": {
        "framework": { "id": "wf-id-105", "name": "Wiz (Legacy)" },
        "id": "wct-id-2136",
        "name": "Operationalization"
      },
      "id": "wsct-id-5540",
      "title": "Operationalization"
    }
  ],
  "severity": "NONE",
  "status": "OPEN",
  "targetExternalId": "i-07602bddd9c7a3052",
  "targetObjectProviderUniqueId": "arn:aws:ec2:us-east-2:998231069301:instance/i-07602bddd9c7a3052"
}

smriti0321 · 2024-06-26T15:05:22Z

@tinnytintin10 we plan to capture ruleset through a separate RFC as per my discussion with @trisch-me

smriti0321 · 2024-06-27T12:37:10Z

@ebeahan and @tinnytintin10 could you please review the changes.

rfcs/0000-additional-rule-field.md

… number in series.

trisch-me

lgtm for the stage 0

smriti0321 · 2024-09-02T14:01:05Z

@tinnytintin10 Requested changes are taken care of, could you please approve this?

tinnytintin10

LGTM

@trisch-me

* Add .caseless subfield to process.name & process.executable (elastic#2341) Adds a subfield to the process.name and process.executable fields to improve the compatibility of data sources like System, Sysmon, etc., with our Elastic Defend data, which enables us to handle language limitations in KQL more effectively. * Revert "Add .caseless subfield to process.name & process.executable" (elastic#2350) This reverts commit 7815b3f from elastic#2341. This is being reverted due to storage concerns. The goal will be to advance the native querying capabilities (ES|QL, KQL) of the Elastic stack such that this extra normalized multi-field is not necessary. In the meantime, localized overrides of the ECS field definition will be used to add the additional multi-field where needed. The downside of localized overrides are that it creates inconsistency across usages of the this field. * [RFC] Apple Platform specific fields (elastic#2338) Adds RFS stage 0 --------- Co-authored-by: Alexandra Konrad <[email protected]> Co-authored-by: Michael Wolf <[email protected]> * Add renovate.json (elastic#2352) Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> Co-authored-by: Michael Wolf <[email protected]> * Update template fields (elastic#2354) Update some templated fields that were missed before merging the RFC * Pin dependencies (elastic#2355) Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> Co-authored-by: Michael Wolf <[email protected]> * Update dependency PyYAML to v6.0.2 (elastic#2356) Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> Co-authored-by: Michael Wolf <[email protected]> * Update dependency gitpython to v3.1.43 (elastic#2358) Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> Co-authored-by: Michael Wolf <[email protected]> * Update dependency yamllint to v1.35.1 (elastic#2361) Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> Co-authored-by: Michael Wolf <[email protected]> * Update stale PR message (elastic#2369) Add a friendlier stale PR message, based from the [Beats stale message](https:/elastic/beats/blob/main/.github/stale.yml#L63-L74). This will hopefully also prompt contributors to respond, so we'll be better able to track PRs people are still interested in contributing. * Update actions/checkout action to v4 (elastic#2362) Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> Co-authored-by: Michael Wolf <[email protected]> * Update actions/github-script action to v7 (elastic#2363) Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> Co-authored-by: Michael Wolf <[email protected]> * Update actions/setup-python action to v5 (elastic#2364) Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> Co-authored-by: Michael Wolf <[email protected]> * Update actions/stale action to v9 (elastic#2365) Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> Co-authored-by: Michael Wolf <[email protected]> * Update dependency mock to v5 (elastic#2367) Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> Co-authored-by: Michael Wolf <[email protected]> * Update dependency ubuntu to v22 (elastic#2368) Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> Co-authored-by: Michael Wolf <[email protected]> * Update dependency autopep8 to v1.7.0 (elastic#2359) Update dependency autopep8 to v1.7.0 --------- Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> Co-authored-by: Michael Wolf <[email protected]> * Update dependency autopep8 to v2 (elastic#2366) * Update dependency autopep8 to v2 --------- Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> Co-authored-by: Michael Wolf <[email protected]> * add license header (elastic#2377) * Update actions/setup-python digest to f677139 (elastic#2374) Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> Co-authored-by: Michael Wolf <[email protected]> * [RFC] Stage 0: Introducing new field in rule namespace (elastic#2330) * Update 0000-rfc-template.md Updating the temaplate for RFC Stage 0 for adding 2 new rule fields: rule.tags and rule.remediation * Update 0000-rfc-template.md Incorporating review comments. * Renaming the template file with recommended name * Resolving conflicts * Removing Tag Field * Resolving comments from @trisch-me * Moving file to rfcs/text folder as per @trisch-me comment. using next number in series. * I saw number 44 was used in a recent RFC, using next number in series --------- Co-authored-by: Eric Beahan <[email protected]> Co-authored-by: Alexandra Konrad <[email protected]> * [RFC] Stage 2: Adding Apple Platform specific fields (elastic#2370) Updating the RFC and moving it to stage two. * code blocks specified language yaml (elastic#2380) Co-authored-by: Michael Wolf <[email protected]> * trim trailing whitespace in schema (elastic#2379) Co-authored-by: Michael Wolf <[email protected]> * [RFC] Stage 0: Introducing new fields in ECS vulnerability field set (elastic#2331) * RFC to add new fields in ECS vulnerability field set RFC to add new fields in ECS vulnerability field set * Moving to separate file * set title and add stage 0 PR # * clean up fields table markdown * Moving to (rfcs/text) and renaming file to next number in series. * Resolving the comments from @trisch-me * Update rfcs/text/0045-additional-vulnerability-fields.md Co-authored-by: Alexandra Konrad <[email protected]> * Update rfcs/text/0045-additional-vulnerability-fields.md Co-authored-by: Alexandra Konrad <[email protected]> * Making changed to the date format as per comments from @trisch-me * Resolving @trisch-me comments * Resolving latest comments * Update rfcs/text/0045-additional-vulnerability-fields.md Co-authored-by: Alexandra Konrad <[email protected]> --------- Co-authored-by: Eric Beahan <[email protected]> Co-authored-by: Alexandra Konrad <[email protected]> * Fix type in code signature (elastic#2382) Change the type of code_signature.flags to keyword, which is what it should be. Also add a unit test that will verify all types are valid. * Enforce yamllint in CI (elastic#2381) Start running and enforcing yamllint checks in CI. * Add Stage0 RFC for new fields for fileless execution on Linux (elastic#2322) * Add support for settings * Fix settings merging * Restrict test workflow * Fix merge conflicts * Less restrictive * Add docker files and pipeline * Make building more restrictive * Simplify build workflow * Update tagging strategy * Removing unused variable * Kick? * Anchors aren't supported 😭 * Fix role name * Test branch name * Remove extra default update (#3) * Remove extra default update * Fix role name * Add support for a top-level type (#4) * Add support for a top-level type * Actually, don't need to be all the complicated * Type needs to be nested within the field name (#5) * Add documention for parameters field (#6) * Add undocumented field argument * Remove the PR template --------- Co-authored-by: Jonhnathan <[email protected]> Co-authored-by: Andrew Kroh <[email protected]> Co-authored-by: Thijs Xhaflaire <[email protected]> Co-authored-by: Alexandra Konrad <[email protected]> Co-authored-by: Michael Wolf <[email protected]> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> Co-authored-by: Stefan Bischof <[email protected]> Co-authored-by: Smriti <[email protected]> Co-authored-by: Eric Beahan <[email protected]> Co-authored-by: Michal Stanek <[email protected]>

Update 0000-rfc-template.md

8f880e8

Updating the temaplate for RFC Stage 0 for adding 2 new rule fields: rule.tags and rule.remediation

smriti0321 requested a review from a team as a code owner April 5, 2024 10:34

trisch-me reviewed Apr 5, 2024

View reviewed changes

rfcs/0000-rfc-template.md Outdated Show resolved Hide resolved

ebeahan reviewed Apr 8, 2024

View reviewed changes

smriti0321 requested review from clement-fouque, oren-zohar, tinnytintin10 and orouz April 9, 2024 08:07

clement-fouque reviewed Apr 15, 2024

View reviewed changes

Update 0000-rfc-template.md

0bee3ac

Incorporating review comments.

orouz mentioned this pull request May 7, 2024

Adopt ECS fields for Findings and Vulnerabilities elastic/cloudbeat#2187

Open

1 task

Merge branch 'main' into rule-fields

8ee34ce

ebeahan requested a review from a team May 29, 2024 16:51

tinnytintin10 requested changes May 29, 2024

View reviewed changes

smriti0321 added 3 commits June 27, 2024 14:21

Renaming the template file with recommended name

0dce6ad

Resolving conflicts

6a66ed1

Removing Tag Field

af356f6

smriti0321 requested review from ebeahan and tinnytintin10 June 27, 2024 12:36

trisch-me changed the title ~~[RFC] Stage 0: Introducing 2 new fields in rule field set~~ [RFC] Stage 0: Introducing new field in rule namespace Jul 1, 2024

trisch-me reviewed Jul 1, 2024

View reviewed changes

rfcs/0000-additional-rule-field.md Outdated Show resolved Hide resolved

trisch-me reviewed Jul 1, 2024

View reviewed changes

rfcs/0000-additional-rule-field.md Outdated Show resolved Hide resolved

trisch-me reviewed Jul 1, 2024

View reviewed changes

rfcs/0000-additional-rule-field.md Outdated Show resolved Hide resolved

trisch-me reviewed Jul 1, 2024

View reviewed changes

rfcs/0000-additional-rule-field.md Outdated Show resolved Hide resolved

smriti0321 added 2 commits July 4, 2024 14:39

Resolving comments from @trisch-me

8fcb9b7

Moving file to rfcs/text folder as per @trisch-me comment. using next…

63e9f39

… number in series.

smriti0321 requested a review from trisch-me July 4, 2024 13:20

smriti0321 and others added 2 commits July 4, 2024 16:00

I saw number 44 was used in a recent RFC, using next number in series

9f2c005

Merge branch 'main' into rule-fields

660404c

trisch-me approved these changes Jul 23, 2024

View reviewed changes

tinnytintin10 approved these changes Sep 5, 2024

View reviewed changes

Merge branch 'main' into rule-fields

a8244ca

trisch-me merged commit 029cf00 into elastic:main Sep 10, 2024
3 checks passed

lksnyder0 mentioned this pull request Oct 9, 2024

elastic main huntresslabs/ecs#8

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[RFC] Stage 0: Introducing new field in rule namespace #2330

[RFC] Stage 0: Introducing new field in rule namespace #2330

smriti0321 commented Apr 5, 2024 •

edited

Loading

ebeahan left a comment

ebeahan Apr 8, 2024

smriti0321 Apr 25, 2024

ebeahan Apr 8, 2024

smriti0321 Apr 25, 2024

tinnytintin10 May 29, 2024 •

edited

Loading

maxcold May 31, 2024

kfirpeled Jul 14, 2024 •

edited

Loading

ebeahan Apr 8, 2024

smriti0321 Apr 25, 2024

clement-fouque left a comment

tinnytintin10 left a comment

tinnytintin10 May 29, 2024

tinnytintin10 May 29, 2024 •

edited

Loading

tinnytintin10 commented May 29, 2024

smriti0321 commented Jun 26, 2024

smriti0321 commented Jun 27, 2024

trisch-me left a comment

smriti0321 commented Sep 2, 2024

tinnytintin10 left a comment

[RFC] Stage 0: Introducing new field in rule namespace #2330

[RFC] Stage 0: Introducing new field in rule namespace #2330

Conversation

smriti0321 commented Apr 5, 2024 • edited Loading

ebeahan left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

tinnytintin10 May 29, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

kfirpeled Jul 14, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

clement-fouque left a comment

Choose a reason for hiding this comment

tinnytintin10 left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

tinnytintin10 May 29, 2024 • edited Loading

Choose a reason for hiding this comment

tinnytintin10 commented May 29, 2024

smriti0321 commented Jun 26, 2024

smriti0321 commented Jun 27, 2024

trisch-me left a comment

Choose a reason for hiding this comment

smriti0321 commented Sep 2, 2024

tinnytintin10 left a comment

Choose a reason for hiding this comment

smriti0321 commented Apr 5, 2024 •

edited

Loading

tinnytintin10 May 29, 2024 •

edited

Loading

kfirpeled Jul 14, 2024 •

edited

Loading

tinnytintin10 May 29, 2024 •

edited

Loading