Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[7.x] [Security Solution][Detection Engine] Test cases for alias failure test cases where we don't copy aliases correctly (#101437) #101490

Merged

Commits on Jun 7, 2021

  1. [Security Solution][Detection Engine] Test cases for alias failure te…

    …st cases where we don't copy aliases correctly (elastic#101437)
    
    ## Summary
    
    Test cases for signals and aliases, including a failure of where we do not copy alias data at the moment even if the target is an ECS compatible field.
    
    For example with this mapping:
    
    ```json
    {
      "dynamic": "strict",
      "properties": {
        "@timestamp": {
          "type": "date"
        },
        "host": {
          "properties": {
            "name": {
              "type": "alias",
              "path": "host_alias.name"
            }
          }
        },
        "host_alias": {
          "properties": {
            "name": {
              "type": "keyword"
            }
          }
        }
      }
    }
    ```
    
    If we detect this as a signal hit we should be copying over both:
    * `host_alias.name` -> `host.name`
    * `host_alias.name` -> `host_alias.name`
    
    to the target signal index, but we only copy:
    * `host_alias.name` -> `host_alias.name`
    
    ### Checklist
    
    - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
    FrankHassanabad committed Jun 7, 2021
    Configuration menu
    Copy the full SHA
    5b28ee0 View commit details
    Browse the repository at this point in the history