Cloud Native Anti-DDoS Advanced (CNAD)

The Service Control Policies (SCPs) in the Organizations service can use these authorization elements to set access control policies.

SCPs do not actually grant any permissions to a principal. They only set the permission boundary for the principal. When SCPs are attached to a member account or an organizational unit (OU), they do not directly grant permissions to that member account or OU. Instead, the SCPs just determine what permissions are available for that member account or the member accounts under that OU.

This section describes the elements used by Organizations SCPs. The elements include actions, resources, and conditions.

For details about how to use these elements to create a custom SCP, see Creating an SCP.

Actions

Actions are specific operations that are allowed or denied in an SCP.

The Access Level column describes how the action is classified (List, Read, or Write). This classification helps you understand the level of access that an action grants when you use it in a policy.
The Resource Type column indicates whether the action supports resource-level permissions.
- You can use a wildcard (*) to indicate all resource types. If this column is empty (-), the action does not support resource-level permissions and you must specify all resources ("*") in your SCP policy statements.
- If this column includes a resource type, you must specify a URN for the Resource element in your identity policy statements.
- Required resources are marked with asterisks (*) in the table.
For details about the resource types defined by CNAD, see Resource.
The Condition Key column includes keys that you can specify in the Condition element of a SCP policy statement.
- If the Resource Type column has values for an action, the condition key only takes effect only for the listed resource types.
- If the Resource Type column is empty (-) for an action, the condition key takes effect for all resources that action supports.
- If the Condition Key column is empty (-) for an action, the action does not support any condition keys.
For details about the condition keys defined by CNAD, see Conditions.

The following table lists the actions that you can define in SCP statements for CNAD.

**Table 1** Actions supported by CNAD
Action	Description	Access Level	Resource Type (* required)	Condition Key
cnad:schedule:update	Grant permission to update scheduling specifications.	write	schedule *	-
cnad:schedule:list	Grant permission to query the scheduling rule list.	list	schedule *	-
cnad:schedule:get	Grant permission to query scheduling rules.	read	schedule *	-
cnad:schedule:delete	Grant permission to delete scheduling rules.	write	schedule *	-
cnad:schedule:create	Grant permission to create scheduling rules.	write	schedule *	-
cnad:quota:update	Grant permission to modify quotas.	write	-	-
cnad:blockade:release	Grant permission to unblock IP addresses.	write	-	-
cnad:blockade:list	Grant permission to query the blocking list.	list	-	-
cnad:blockade:get	Grant permission to query blocking records.	read	-	-
cnad:alarmConfig:update	Grant permission to modify alarm notifications.	write	-	-
cnad:alarmConfig:create	Grant permission to create alarm notifications.	write	-	-
cnad:alarmConfig:delete	Grant permission to delete alarm notifications.	write	-	-
cnad:alarmConfig:get	Grant permission to query alarm notifications.	read	-	-
cnad:attackReport:list	Grant permission to query attack events.	list	-	-
cnad:attackReport:update	Grant permission to update attack event configurations.	write	-	-
cnad:attackTop:list	Grant permission to query top 10 attacked IP addresses.	list	-	-
cnad:attackTypeReport:list	Grant permission to query attack type distribution.	list	-	-
cnad:bindPolicy:create	Grant permission to bind protection policies to protected IP addresses.	write	-	-
cnad:blackWhiteIpList:create	Grant permission to create an IP address blacklist or whitelist.	write	-	-
cnad:blackWhiteIpList:delete	Grant permission to delete an IP address blacklist or whitelist.	write	-	-
cnad:cleanCountReport:list	Grant permission to query the DDoS protection trend.	list	-	-
cnad:cleanKbpsReport:list	Grant permission to query statistics on peak scrubbing traffic.	list	-	-
cnad:cleanScaleDropList:list	Grant permission to query the scrubbing scope.	list	-	-
cnad:countReport:get	Grant permission to query statistics.	read	-	-
cnad:ipTag:put	Grant permission to update the tags of protected IP addresses.	write	-	-
cnad:package:create	Create an instance.	write	package *	g:EnterpriseProjectId g:ResourceTag/<tag-key>
cnad:package:get	Grant permission to query an instance.	read	package *	g:EnterpriseProjectId g:ResourceTag/<tag-key>
cnad:package:list	Query the DB instance list.	list	package *	-
cnad:package:put	Grant permission to update an instance.	write	package *	g:EnterpriseProjectId g:ResourceTag/<tag-key>
cnad:packageDropList:list	Grant permission to query the instance summary list.	list	-	-
cnad:packetAttackReport:list	Grant permission to query attack data packets.	list	-	-
cnad:policy:create	Grant permission to create protection policies.	write	policy *	g:EnterpriseProjectId
cnad:policy:delete	Grant permission to delete protection policies.	write	policy *	g:EnterpriseProjectId
cnad:policy:get	Grant permission to query details about a protection policy.	read	policy *	g:EnterpriseProjectId
cnad:policy:list	Grant permission to query protection policy details.	list	policy *	-
cnad:policy:put	Grant permission to update protection policies.	write	policy *	g:EnterpriseProjectId
cnad:policyDropList:list	Grant permission to query the protection policy list.	list	-	-
cnad:protectedIp:create	Grant permission to bind protected IP addresses to an instance.	write	-	-
cnad:protectedIp:list	Grant permission to query the protected IP address list.	list	-	-
cnad:protectedIpDropList:list	Grant the permission to query the protected IP address drop-down list.	list	-	-
cnad:quota:get	Grant permission to query quotas.	read	-	-
cnad:securityStatusReport:get	Grant permission to query asset security status.	read	-	-
cnad:trafficAttackReport:list	Grant permission to query attack traffic.	list	-	-
cnad:policy:unbind	Grant permission to remove a protection policy from a protected IP address.	write	-	-
cnad:weekStatisticsReport:get	Grant permission to query weekly security statistics.	read	-	-

Each API of CNAD usually supports one or more actions. Table 2 lists the supported actions and dependencies.

**Table 2** Actions and dependencies supported by CNAD APIs
API	Action	Dependency
GET /v1/unblockservice/{domain_id}/unblock-quota-statistics	cnad:quota:get	-
POST /v1/unblockservice/{domain_id}/unblock	cnad:blockade:release	-
GET /v1/unblockservice/{domain_id}/unblock-record	cnad:blockade:list	-
GET /v1/unblockservice/{domain_id}/block-statistics	cnad:blockade:get	-
POST /v1/cnad/alarm-config	cnad:alarmConfig:update	-
DELETE /v1/cnad/alarm-config	cnad:alarmConfig:delete	-
GET /v1/cnad/alarm-config	cnad:alarmConfig:get	-
POST /v1/cnad/policies/{policy_id}/bind	cnad:bindPolicy:create	-
POST /v1/cnad/policies/{policy_id}/ip-list/add	cnad:blackWhiteIpList:create	-
POST /v1/cnad/policies/{policy_id}/ip-list/delete	cnad:blackWhiteIpList:delete	-
PUT /v1/cnad/protected-ips/tags	cnad:ipTag:put	-
GET /v1/cnad/packages	cnad:package:list	-
PUT /v1/cnad/packages/{package_id}/name	cnad:package:put	-
POST /v1/cnad/policies	cnad:policy:create	-
DELETE /v1/cnad/policies/{policy_id}	cnad:policy:delete	-
GET /v1/cnad/policies/{policy_id}	cnad:policy:get	-
GET /v1/cnad/policies	cnad:policy:list	-
PUT /v1/cnad/policies/{policy_id}	cnad:policy:put	-
POST /v1/cnad/packages/{package_id}/protected-ips	cnad:protectedIp:create	-
GET /v1/cnad/protected-ips	cnad:protectedIp:list	-
GET /v1/cnad/packages/{package_id}/unbound-protected-ips	cnad:protectedIpDropList:list	-
POST /v1/cnad/policies/{policy_id}/unbind	cnad:policy:unbind	-

Resource

A resource type indicates the resources that an SCP policy applies to. If you specify a resource type for any action in Table 3, the resource URN must be specified in the SCP policy statements using that action, and the policy applies only to resources of this type. If no resource type is specified, the Resource element is marked with an asterisk (*) and the policy applies to all resources. You can also set condition keys in a policy to define resource types.

The following table lists the resource types that you can define in SCP policy statements for CNAD.