Get Compliance Trend for Requirement ID V2 - POST
POST/v2/compliance/posture/trend/:complianceId/:requirementId
Returns the compliance posture summary that describes the passed/failed statistics trend for the given compliance standard ID and compliance requirement ID.
The fields body parameter allows you to request specific fields. These fields are separate from the filters you specify. The following are valid fields items.
- cloud.account
- account.group
- cloud.region
- cloud.type
- policy.complianceStandard
- policy.complianceRequirement
- policy.complianceSection
The filters body parameter enables you to narrow your request for alerts. See Get Compliance Overview Filters and Options for the API request to list all valid filters.
Request
Path Parameters
Compliance standard ID
Compliance requirement ID
- application/json
Body
- Array [
- ]
Detailed
Array of specific fields to return
filters object[]
Filtering parameters.
For filter names, refer to List Filters API.
For filter values, refer to List filter suggestions.
The only exception is resource.tagv2 filter name, provide filter value for it in the following format: "{"key":"'CustomerTagKey'","value":"'CustomerTagValue'"}"
Name
Possible values: [tag:yaml.org,2002:value =
]
Operator
Value
For asset or data inventory only. Group returned items by cloud.type, cloud.service, cloud.region, cloud.account, and/or resource.type
Maximum number of items to return. When data is paginated, maximum number of items per page.The maximum cannot exceed 10,000. The default is 10,000.
The number of items to skip before selecting items to return. Default is zero
Setting this pagination Token to the nextPageToken from a response object returns the next page of data
Array of sort properties. Append :asc or :desc to the key to sort by ascending or descending order respectively. Example sort properties are id:asc and timestamp:desc
Responses
- 200
- 400
success
- application/json
- Schema
- Example (from schema)
Schema
- Array [
- ]
Number of scanned compliance resources whose highest policy failure is critical
Number of failed scanned compliance resources
Number of scanned compliance resources that failed high severity policies
Number of scanned compliance resources whose highest policy failure is informational
Number of scanned compliance resources whose highest policy failure is low
Number of scanned compliance resources whose highest policy failure is medium
Number of passed scanned compliance resources
Timestamp
Total number of scanned compliance resources
[
{
"criticalSeverityFailedResources": 0,
"failedResources": 0,
"highSeverityFailedResources": 0,
"informationalSeverityFailedResources": 0,
"lowSeverityFailedResources": 0,
"mediumSeverityFailedResources": 0,
"passedResources": 0,
"timestamp": 0,
"totalResources": 0
}
]
bad_request