Modify the mode

put https://{hostname}/appsec/v1/configs/{configId}/versions/{versionNumber}/security-policies/{policyId}/mode

Kona Site Defender, App & API Protector with the Advanced Security module, Adaptive Security Engine The mode you set determines how your rule sets are updated. Use KRS mode to update the rule sets manually, or AAG to have them update automatically. If you're using Adaptive Security Engine, use ASE_AUTO to update the rules automatically, or ASE_MANUAL to update them yourself.

Path Params

configId

int64

required

A unique identifier for each configuration.

versionNumber

integer

required

A unique identifier for each version of a configuration.

policyId

string

required

A unique identifier for a security policy.

Query Params

accountSwitchKey

string

For customers who manage more than one account, this runs the operation from another account. The Identity and Access Management API provides a list of available account switch keys.

Body Params

mode

string

required

The security policy rule update mode. Use KRS to update rules manually, or AAG to update rules automatically. For Adaptive Security Engine (ASE), use ASE_AUTO for automatic updates or ASE_MANUAL to manually get current rules. When switching from one mode to another, any rule actions you have migrate to the new mode. For example, your rule actions for ASE_AUTO become the rule actions for ASE_MANUAL when you switch from auto to manual modes, and vice versa. Rule actions for ASE_AUTO are currently in beta. Contact your account team to access this option.

Responses

Language

Authentication

Remember to add your authentication credentials to run this code.

URL


xxxxxxxxxx
1
curl --request PUT \
2
     --url https://hostname/appsec/v1/configs/configId/versions/versionNumber/security-policies/policyId/mode \
3
     --header 'accept: application/json' \
4
     --header 'content-type: application/json' \
5
     --data '{"mode":"KRS"}'


xxxxxxxxxx
 
1
{
2
  "current": "KRS 1.0 (Apr 20, 2020)",
3
  "mode": "KRS"
4
}

200Successfully set the security policy mode.

400Invalid. Client error, such as invalid or malformed input.

403Forbidden. You don't have permission to write to this resource.

404Not found. The named security policy doesn't exist, doesn't carry application layer controls, or no rule with this ID is available for use in this policy.

500Internal server error. Something went wrong on our side. Try again in a few minutes, and contact support if the error persists.