Upsert an asset criticality record

deprecated

Base URL: https://{kibana_url}

POST /api/asset_criticality

Deprecated in 9.4.0. Use the Entity Store APIs to assign asset criticality to an entity.

Create or update an asset criticality record for a specific entity.

If a record already exists for the specified entity, that record is overwritten with the specified value. If a record doesn't exist for the specified entity, a new record is created.

Authentication

Api key

Authorization: <value>

These APIs use key-based authentication. You must create an API key and use the encoded value in the request header. For example: Authorization: ApiKey base64AccessApiKey

Basic

Authorization: Basic <credentials>

Request body

Responses

Successful response

application/json

id_field enum required: Values: host.name user.name service.name entity.id
id_value string required: The ID value of the asset.
criticality_level enum required: The criticality level of the asset.; Values: low_impact medium_impact high_impact extreme_impact
asset object required
entity object
host object
service object
user object
@timestamp string · format: date-time required: The time the record was created or updated.

400

Invalid request

Base URL: https://{kibana_url}

Examples

Request Console 1 / 2 languages

Console Kibana Dev Tools

POST kbn:/api/asset_criticality
{
  "criticality_level": "high_impact",
  "id_field": "host.name",
  "id_value": "my_host"
}

Generated from the API spec

curl Shell

curl -X POST "${KIBANA_URL}/api/asset_criticality" \
  -H "Authorization: ApiKey ${API_KEY}" \
  -H "Content-Type: application/json" \
  -d '{
    "criticality_level": "high_impact",
    "id_field": "host.name",
    "id_value": "my_host"
  }'

Generated from the API spec

Response

No example

Authentication

Request body { }

Responses

Request body