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

[Security Solution] [Detections] Wrong error message displayed for ServiceNow, Jira and IBM Resilient actions #84472

Closed
MadameSheema opened this issue Nov 30, 2020 · 4 comments
Assignees
Labels
bug Fixes for quality problems that affect the customer experience fixed impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. v7.10.2 v7.11.0

Comments

@MadameSheema
Copy link
Member

Describe the bug:

  • Wrong error message displayed for ServiceNow, Jira and IBM Resilient actions when editing or creating a rule when leaving the action mandatory fields empty.

Kibana/Elasticsearch Stack version:

  • 7.10.1

Functional Area (e.g. Endpoint management, timelines, resolver, etc.):

  • Detections
  • Actions

Initial Context:

  • To have the following connectors created for the rule actions: ServiceNow, Jira and IBM Resilient

Steps to reproduce:

  1. Create or edit a detection rule with actions leaving the mandatory fields empty.

Current behavior:
localhost_5601_app_security_detections_rules_id_c61cd66d-ab31-4951-99b8-e66cdb611403_edit_sourcerer=(default_!()) timerange=(global_(linkTo_!(timeline),timerange_(from_%272020-11-29T09_27_32 475Z%27,fromStr_now-24h,kind_relative,to_%272 (1)

localhost_5601_app_security_detections_rules_id_c61cd66d-ab31-4951-99b8-e66cdb611403_edit_sourcerer=(default_!()) timerange=(global_(linkTo_!(timeline),timerange_(from_%272020-11-29T09_27_32 475Z%27,fromStr_now-24h,kind_relative,to_%272 (2)

localhost_5601_app_security_detections_rules_id_c61cd66d-ab31-4951-99b8-e66cdb611403_edit_sourcerer=(default_!()) timerange=(global_(linkTo_!(timeline),timerange_(from_%272020-11-29T09_27_32 475Z%27,fromStr_now-24h,kind_relative,to_%272 (3)

Expected behavior:

  • The error message maps with the displayed fields
  • We should be aligned in the way we display the error below the field. Or we display an error for all the connectors or we don't.
@MadameSheema MadameSheema added bug Fixes for quality problems that affect the customer experience impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. labels Nov 30, 2020
@cnasikas cnasikas added the fixed label Dec 2, 2020
@cnasikas
Copy link
Member

@MadameSheema Should we close this?

@MadameSheema
Copy link
Member Author

Did we backported this to 7.10.2?

@cnasikas
Copy link
Member

@MadameSheema Yes!

@ghost
Copy link

ghost commented Jan 7, 2021

Hi @MadameSheema

We have validated this ticket on 7.10.2 BC1 as well as 7.11.0 BC2 Cloud Builds and found that issue is now Fixed . Correct error message is displaying for ServiceNow, Jira and IBM Resilient when create or edit the rule.

Build Details:

Version: 7.10.2 BC1
Build: 36136
Commit: a0b793698735eb1d0ab1038f8e5d7a951524e929
Version: 7.11.0 BC2
Build: 37605
Commit: a5126f7a280a6f4a27dc3aca65c1c89ccd1ac694

Artifacts: https://staging.elastic.co/7.10.2-e6b2b8c2/summary-7.10.2.html
Artifacts: https://staging.elastic.co/7.11.0-8f5ce7c2/summary-7.11.0.html

Screenshots:

  • 7.10.2 IBM
    7 10 2_IBM

  • 7.10.2 Jira
    7_10 2_jira

  • 7.10.2 Service Now
    7_10_2_SN

  • 7.11.0 IBM
    7_11_0_ibm

  • 7.11.0 Jira
    7_11_0_Jira

  • 7.11.0 Service Now
    7_11_0_SN

Thanks!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience fixed impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. v7.10.2 v7.11.0
Projects
None yet
Development

No branches or pull requests

2 participants