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

[muskangulati-qasource]

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

[elasticmachine]

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

[muskangulati-qasource]

@amolnater-qasource please review!

[amolnater-qasource]

Reviewed & assigned to @MadameSheema

[elasticmachine]

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

[jaredburgettelastic]

👀

[jaredburgettelastic]

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

[machadoum]

This is a great feature request, but it isn't a bug.

[muskangulati-qasource]

Thank you for the update @machadoum,

Please let us know if we need to change this ticket type from Query to Enhancement

Thanks!

[jaredburgettelastic]

Please let us know if we need to change this ticket type from Query to Enhancement

@muskangulati-qasource that works, thank you! We've gone ahead and added to our prioritized backlog

[muskangulati-qasource]

Hi @jaredburgettelastic,

We have updated the ticket and labels for the same.

Thanks!