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.

Sign up for GitHub

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

Jump to bottom

[Security Solution] Source field for Risk score override is not properly displayed on created rule when the name is long #81304

Open
MadameSheema opened this issue Oct 21, 2020 · 0 comments
Open

[Security Solution] Source field for Risk score override is not properly displayed on created rule when the name is long #81304

MadameSheema opened this issue Oct 21, 2020 · 0 comments
Labels
bug Fixes for quality problems that affect the customer experience Feature:Rule Details Security Solution Detection Rule Details impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team:Detection Rule Management Security Detection Rule Management Team Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.

Comments

@MadameSheema
Copy link
Member

Info:

  • Found during testing BC8

Preconditions:

  • To have a rule created with Risk score override activated and a long Source field. I.e: destination.as.number

Steps to reproduce:

  1. Go to Security > Detections
  2. Click on Manage detection rules
  3. Open the created rule

Current behaviour:

  • The Source field for the Risk score override is not properly displayed

Screenshot 2020-08-11 at 12 47 22

Expected behaviour:

  • The Source field for the Risk score override is properly displayed

Extra information:

  • This is happening in all the supported browsers
@MadameSheema MadameSheema added bug Fixes for quality problems that affect the customer experience Team:Detections and Resp Security Detection Response Team labels Oct 21, 2020
@MindyRS MindyRS added the Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. label Oct 27, 2020
@peluja1012 peluja1012 added the impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. label Oct 28, 2020
@peluja1012 peluja1012 added the Feature:Detection Rules Anything related to Security Solution's Detection Rules label Nov 17, 2020
@spong spong removed their assignment Nov 10, 2021
@peluja1012 peluja1012 added the Team:Detection Rule Management Security Detection Rule Management Team label Mar 18, 2022
@peluja1012 peluja1012 added Feature:Rule Details Security Solution Detection Rule Details and removed Feature:Detection Rules Anything related to Security Solution's Detection Rules labels May 19, 2022
@MadameSheema MadameSheema mentioned this issue May 12, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Fixes for quality problems that affect the customer experience Feature:Rule Details Security Solution Detection Rule Details impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team:Detection Rule Management Security Detection Rule Management Team Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@peluja1012 @MindyRS @spong @MadameSheema