Modify vulnerability scan configurations using ModifyVulConfig - Security Center - Alibaba Cloud - Security Center

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

The table below describes the authorization required to call this API. You can define it in a Resource Access Management (RAM) policy. The table's columns are detailed below:

Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.
API: The API that you can call to perform the action.
Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.
Resource type: The type of the resource that supports authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.
- For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding Alibaba Cloud Resource Name (ARN) in the Resource element of the policy.
- For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.
Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys applicable across all RAM-supported services.
Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action

Access level

Resource type

Condition key

Dependent action

yundun-sas:ModifyVulConfig

update

*All Resource

*

None

Request parameters

Parameter	Type	Required	Description	Example
Type	string	No	The type of vulnerability to modify. Valid values: cve: Linux software vulnerability sys: Windows system vulnerability cms: Web-CMS vulnerability emg: emergency vulnerability app: application vulnerability yum: YUM/APT source configuration scanMode: real risk	cve
Config	string	No	Specifies whether to enable or disable vulnerability detection. Valid values: on: Enables vulnerability detection. off: Disables vulnerability detection. Note If the type is set to real risk, valid values: real: Real risk vulnerabilities. all: All vulnerabilities.	on
ClientToken	string	No	The client token that is used to ensure the idempotence of the request. Different requests must use different tokens. The token can contain only ASCII characters and cannot exceed 64 characters in length.
		No	Specifies whether to perform only a dry run of the request. Valid values: true: performs only a dry run without performing the actual operation. false: performs the actual request. Default value: false.

Response elements

Element	Type	Description	Example
	object
RequestId	string	The request ID.	24DDBE06-58FF-5E5E-9241-D2010D7913C1

Examples

Success response

JSON format

{
  "RequestId": "24DDBE06-58FF-5E5E-9241-D2010D7913C1"
}

Error codes

HTTP status code	Error code	Error message	Description
400	IdempotentParameterMismatch	相同的 ClientToken 被用于不同的请求参数。
500	ServerError	ServerError
403	NoPermission	caller has no permission	You are not authorized to do this operation.
409	IdempotentRequestInProgress	使用相同 ClientToken 的请求正在处理中。

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.