Connect rule update

Updates rules in a connect rule policy.

PATCH https://<API_HOST>/api/v1/policies/policy1_uuid/configuration/rules/connect/accept

PATCH https://<API_HOST>/api/v1/policies/policy1_uuid/configuration/rules/connect/deny

PATCH https://<API_HOST>/api/v1/policies/policy1_uuid/configuration/rules/connect/throttle

PATCH https://<API_HOST>/api/v1/policies/policy1_uuid/configuration/rules/connect/tls

PATCH https://<API_HOST>/api/v1/policies/policy1_uuid/configuration/rules/connect/trusted_sender

Note

If the value to be deleted is not available in the database, the request is ignored.

If the value to be added is already available in the database, a duplicate error will be returned.

TLS rules accept sender_domains only.

Trusted Sender rules accept sender_domains and sender only.

Required headers:

If the domain you use to access the Trellix UI ends in fireeye.com:

x-fireeye-api-key: <key>—Specifies your personal API key.

If the domain you use to access the Trellix UI ends in trellix.com:

authorization: bearer <access_token>—Specifies your personal access token.

Content-Type: “application/json”—Content type of the request body.

Options

policy1_uuid—(string) Universally unique identifier (UUID) of the policy.

accept—Specifies rule type: accept.

deny—Specifies rule type: deny.

throttle—Specifies rule type: throttle.

tls—Specifies rule type: tls.

trusted_sender—Specifies rule type: trusted_sender.

Request body

{
    "add":
    {
        "sender_domains": ["d1.com", "d2.com"],
    },
    "delete":
    {
        "recipients": ["abc@xyz.com"],
    }
}

cURL code sample: connect rule update

curl -k -X PATCH https://API_HOST/api/v1/policies/755defef-b30c-4ea5-a19c-dd97f8ed697c/configuration/rules/connect/accept -H "Content-Type: application/json" -H "x-fireeye-api-key: xxxxxxxxxxxxx" -d'{"add": {"sender_domains": ["d1.com", "d2.com"],}, "delete": {"recipients": ["abc@xyz.com"],}}'

This cURL sample includes the following options: