Queries the details of the risk items that are detected in the configuration checks on cloud services.
Debugging
Authorization information
The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action
policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:
- Operation: the value that you can use in the Action element to specify the operation on a resource.
- Access level: the access level of each operation. The levels are read, write, and list.
- Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level,
All Resources
is used in the Resource type column of the operation.
- Condition Key: the condition key that is defined by the cloud service.
- Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
Operation | Access level | Resource type | Condition key | Associated operation |
---|---|---|---|---|
yundun-sas:ListCheckResult | get | *All Resources * |
| none |
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
StandardIds | array | No | The standard IDs. | |
StandardId | long | No | The standard ID. | 2 |
RequirementIds | array | No | The IDs of the requirements. | |
RequirementId | long | No | The ID of the requirement. | 2 |
Statuses | array | No | The statuses of check items. Separate multiple statuses with commas (,). Valid values:
| |
string | No | The statuses of check items. Separate multiple states with commas (,). Valid values:
| PASS | |
RiskLevels | array | No | The risk levels of check items. Separate multiple risk levels with commas (,). Valid values:
| |
string | No | The risk levels of check items. Separate multiple risk levels with commas (,). Valid values:
| HIGH | |
Vendors | array | No | The cloud service providers. Valid values:
| |
string | No | The cloud service provider. Valid values:
| ALIYUN | |
InstanceTypes | array | No | The asset type of the cloud services. Valid values:
| |
string | No | The asset type of the cloud service. Valid values:
| ECS | |
CheckKey | string | No | The key that you want to use to search for check items in fuzzy match mode. | OSS |
CurrentPage | integer | No | The page number. | 2 |
PageSize | integer | No | The number of entries per page. Maximum value: 100. | 50 |
InstanceIds | array | No | The instance IDs of the cloud services that you want to query. Separate multiple IDs with commas (,). | |
string | No | The instance IDs of the cloud services that you want to query. Separate multiple IDs with commas (,). | i-bp1du66x6w07z4yya**** | |
Lang | string | No | The language of the content within the request and response. Default value: zh. Valid values:
| zh |
SortTypes | array | No | The types of the conditions based on which check items are sorted. Valid values:
| |
string | No | The type of the condition based on which check items are sorted. Valid values:
| STATUS | |
Types | array | No | The types of check standards. | |
string | No | The type of the check standard. Valid values:
| RISK | |
RegionId | string | No | The region ID of the instance. Valid values:
| cn-hangzhou |
CustomParam | boolean | No | Specifies whether the check item supports custom parameters. Valid values:
| true |
CheckIds | array | No | The IDs of the check items. | |
long | No | The ID of the check item. | 358 | |
OperationTypes | array | No | Specifies whether fixing is supported. Valid values:
| |
string | No | Specifies whether fixing is supported. Valid values:
| SUPPORT_REPAIR |
Response parameters
Examples
Sample success responses
JSON
format
{
"Checks": [
{
"CheckPolicies": [
{
"StandardId": 1,
"StandardShowName": "Best security practices",
"RequirementId": 2,
"RequirementShowName": "Alibaba cloud OSS best security practices",
"SectionId": 3,
"SectionShowName": "Log Audit"
}
],
"CheckId": 5,
"CheckShowName": "OSS-PublicReadOpenManifestFileWithoutEncryption",
"Vendor": "ALIYUN",
"VendorShowName": "Aliyun",
"InstanceType": "ECS",
"InstanceSubType": "DISK",
"RiskLevel": "HIGH",
"Status": "PASS",
"TaskId": "64",
"LastCheckTime": 1657793398000,
"TrialPermission": true,
"StatusMessage": "TIMEOUT",
"CheckSaleType": 1,
"AssetVendor": 3,
"AssetType": 0,
"AssetSubType": 0,
"OperationType": "NOT_SUPPORT_REPAIR"
}
],
"PageInfo": {
"CurrentPage": 1,
"PageSize": 20,
"TotalCount": 100,
"Count": 2
},
"RequestId": "F9B6DD67-B289-5406-B35C-B0F4A217S23"
}
Error codes
HTTP status code | Error code | Error message | Description |
---|---|---|---|
400 | IllegalParam | Illegal param | - |
403 | NoPermission | caller has no permission | You are not authorized to do this operation. |
500 | ServerError | ServerError | - |
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation |
---|---|---|
2024-10-10 | The Error code has changed. The request parameters of the API has changed. The response structure of the API has changed | View Change Details |
2024-08-06 | The Error code has changed. The response structure of the API has changed | View Change Details |
2024-07-22 | The Error code has changed. The request parameters of the API has changed | View Change Details |
2024-05-10 | The Error code has changed. The response structure of the API has changed | View Change Details |
2024-03-14 | The Error code has changed | View Change Details |
2023-07-17 | The Error code has changed. The request parameters of the API has changed. The response structure of the API has changed | View Change Details |
2023-01-11 | The API operation is not deprecated.. The Error code has changed | View Change Details |
2022-11-21 | The Error code has changed. The response structure of the API has changed | View Change Details |
2022-07-18 | The Error code has changed. The request parameters of the API has changed | View Change Details |
2022-07-15 | Add Operation | View Change Details |