Get Compliance Trend for Standard ID - POST
POST/compliance/posture/trend/:complianceId
This endpoint has been deprecated and may be replaced or removed in future versions of the API.
Returns a compliance posture summary that describes the passed/failed statistics trend for the specified compliance standard ID.
Replacement Endpoint: Get Compliance Trend for Standard ID V2 - POST
The fields request 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 request body parameter enables you to narrow your request for alerts. See Get Compliance Overview Filters and Options for for an API request to list all the valid filters.
This endpoint will only be able to access data from the past 1 year. This change is implemented to optimize system performance and reduce data storage requirements of deprecated endpoints.
Request
Path Parameters
Compliance standard ID
- application/json
Body
- Array [
- ]
- RelativeTimeRangeConfigModel
- AbsoluteTimeRangeConfigModel
- ToNowTimeRangeConfigModel
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
timeRange object
See the Time Range Model for details.
Possible values: [BACKWARD
, FORWARD
]
Direction in which to count time. Default = BACKWARD
value objectrequired
Model for RelativeTimeDuration
Number of time units
Possible values: [minute
, hour
, day
, week
, month
, year
]
Time unit
value objectrequired
Model for Time
End timestamp
Start timestamp
Possible values: [MINUTE
, HOUR
, DAY
, WEEK
, MONTH
, YEAR
, EPOCH
, LOGIN
]
Time range object
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