All Products
Search
Document Center

Security Center:UpdateFileProtectRule

Last Updated:Feb 20, 2024

Modifies the content of a core file monitoring rule based on the ID of the rule.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

Authorization information

There is currently no authorization information disclosed in the API.

Request parameters

ParameterTypeRequiredDescriptionExample
RuleNamestringYes

The name of the rule.

test-rule-1
ProcPathsarrayYes

The paths to the monitored processes.

stringYes

The path to the monitored process.

/usr/local/*
FilePathsarrayYes

The paths to the monitored files. Wildcard characters are supported.

stringYes

The path to the monitored file. Wildcard characters are supported.

/usr/*
FileOpsarrayYes

The operations performed on the files.

stringYes

The operation performed on the file. Valid values:

  • WRITE
  • READ
  • DELETE
  • RENAME
  • CHMOD: change permissions
WRITE
RuleActionstringNo

The handling method of the rule. Valid values:

  • pass: allow
  • alert
pass
AlertLevelintegerNo

The severity of alerts. Valid values:

  • 0: does not generate alerts
  • 1: sends notifications
  • 2: suspicious
  • 3: high-risk
0
StatusintegerNo

The status of the rule. Valid values:

  • 0: disabled
  • 1: enabled
1
IdlongNo

The ID of the rule.

1062

Response parameters

ParameterTypeDescriptionExample
object

Schema of Response

RequestIdstring

The request ID.

339227F4-C9E1-526F-8347-1099C11F65FB

Examples

Sample success responses

JSONformat

{
  "RequestId": "339227F4-C9E1-526F-8347-1099C11F65FB"
}

Error codes

HTTP status codeError codeError messageDescription
403NoPermissioncaller has no permissionYou are not authorized to do this operation.
500ServerErrorServerError-

For a list of error codes, visit the Service error codes.