[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