CreateFileProtectRule - Security Center - Alibaba Cloud Documentation Center

Creates a core file monitoring rule.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Debug

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

Operation: the value that you can use in the Action element to specify the operation on a resource.
Access level: the access level of each operation. The levels are read, write, and list.
Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
Condition Key: the condition key that is defined by the cloud service.
Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.

Operation	Access level	Resource type	Condition key	Associated operation
yundun-sas:CreateFileProtectRule	create	All Resources ``	none	none

Request parameters

Parameter	Type	Required	Description	Example
RuleName	string	Yes	The name of the rule.	tetsRule
ProcPaths	array	Yes	The paths to the processes that you want to monitor. Wildcard characters are supported.
	string	Yes	The path to the process that you want to monitor.	/usr/local/*
FilePaths	array	Yes	The paths to the files that you want to monitor. Wildcard characters are supported.
	string	Yes	The path to the file that you want to monitor.	/usr/*
FileOps	array	Yes	The operations that you want to perform on the files.
	string	Yes	The operation that you want to perform on the file. Valid values: WRITE READ DELETE RENAME CHMOD: change permissions	CHMOD
RuleAction	string	Yes	The handling method of the rule. Valid values: pass: allow alert	pass
AlertLevel	integer	No	The severity of alerts. Valid values: 0: does not generate alerts 1: sends notifications 2: suspicious 3: high-risk	0
SwitchId	string	No	The switch ID of the rule.	FILE_PROTECT_RULE_SWITCH_TYPE_0000
Status	integer	No	Specifies whether to enable the rule. Valid values: 1: yes 0: no	1
Platform	string	No	The type of the operating system. Valid values: windows: Windows linux: Linux	linux

Response parameters

Parameter	Type	Description	Example
	object	Schema of Response
RequestId	string	The request ID.	EC7C8984-D108-516F-9D36-3DF1D1228CCA
RuleId	long	The ID of the rule.	123

Examples

Sample success responses

JSONformat

{
  "RequestId": "EC7C8984-D108-516F-9D36-3DF1D1228CCA",
  "RuleId": 123
}

Error codes

HTTP status code	Error code	Error message	Description
403	NoPermission	caller has no permission	You are not authorized to do this operation.
500	ServerError	ServerError	-

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

Change history

Change time	Summary of changes	Operation
2024-09-02	The request parameters of the API has changed	View Change Details