Modify attack payload logging settings for a policy

put

https://{hostname}/appsec/v1/configs/{configId}/versions/{versionNumber}/security-policies/{policyId}/advanced-settings/logging/attack-payload

All products Update attack payload logging settings for a specific policy. This operation applies at the security policy level, and overrides the attack payload logging settings at the configuration level on a per-policy basis. When set to NONE, the request body and response body appear as redacted in the log. For example, JSON_PAIRS:redacted.

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

enabled

boolean

required

When enabled, log attack payloads in requests and responses.

override

boolean

required

When true, use the security policy's attack payload logging settings instead of the settings at the configuration level. Note that when type is NONE, the request body and response body show as redacted in the log. For example, JSON_PAIRS:redacted.

requestBody

object

required

The settings for how Akamai's network logs attack payloads in request bodies.

responseBody

object

required

The settings for how Akamai's network logs attack payloads in response bodies.

Headers

string

enum

Defaults to application/json

Generated from available response content types

Allowed:

Responses

Language

URL

Response

Choose an example:

application/json

application/problem+json

200Successfully updated the policy attack payload logging settings.

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

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

404Not found. The 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 or contact support if the error persists.