For example:įor additional examples, refer to Example rules. Sometimes, you may wish to specify where to find the content objects, such as when the content is a Base64-encoded string within a JSON payload. However, the WAF will only perfom an action on requests with content considered malicious once you create a WAF custom rule. Once you enable the feature, the default content scanner behavior is to scan certain content objects such as multipart/form-data file uploads for malicious content. The scan results, along with additional metadata, are exposed as fields available in WAF custom rules, allowing you to implement fine-grained mitigation rules. When enabled, content scanning attempts to detect content objects, such as uploaded files, and scans them for malicious signatures like malware. Contact your account team to get access.Īt this stage, WAF content scanning API endpoints may change on short notice. This feature is only available for select customers on an Enterprise plan.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |