search

elastic / kibana

Your window into the Elastic Stack
https://www.elastic.co/products/kibana
Other
19.79k stars 8.19k forks source link

[Security Solution] [QUERY] Unassigned impact is not allowed while adding in the asset criticality via bulk upload #195393

Open muskangulati-qasource opened 6 days ago

muskangulati-qasource commented 6 days ago

Describe the bug Unassigned impact is not allowed while adding in the asset criticality via bulk upload

Kibana/Elasticsearch Stack version

VERSION: 8.16.0
BUILD: 78825
COMMIT: a805375758e4bc931cf13dfdcac89b8d877a15d2

Steps

  1. Kibana version 8.16.0 or above should exist without endpoints
  2. securitySolution:enableAssetCriticality flag should be enabled for Asset Criticality
  3. Navigate to Security >> Manage >> Asset criticality
  4. Create a file according to the example given
  5. Click on ‘select or drag and drop a file’
  6. Add the file created
  7. Click on assign and observe for the output message: with error for unassigned value

Screenshot Image

elasticmachine commented 6 days ago

Pinging @elastic/security-solution (Team: SecuritySolution)

muskangulati-qasource commented 6 days ago

@amolnater-qasource please review!

amolnater-qasource commented 6 days ago

Reviewed & assigned to @MadameSheema

elasticmachine commented 6 days ago

Pinging @elastic/security-entity-analytics (Team:Entity Analytics)

jaredburgettelastic commented 6 days ago

👀

jaredburgettelastic commented 6 days ago

@hop-dev what is the new string value for unassignment, now that the /delete API is a soft delete?