Web Application Firewall (WAF) - Optimized the Simple Log Service for WAF Feature in WAF 3.0
Sep 03 2024
Web Application Firewall (WAF)Content
Target customers: Customers who have advanced requirements for log operations analysis. The customers can analyze full request header fields to identify unknown risks. Customers who have fine-grained planning for log capacity. The customers can store all fields for core business and store only the required fields for other business. Features released: Feature optimization: ● You can configure global field settings. You can also configure protected object-level settings. ● The request_headers_all field is added to optional fields. ● The names of log fields are standardized. The following fields are added to required fields: src_ip, src_port, dst_port, request_uri, and start_time. The following fields are moved to optional fields and are selected by default: remote_addr, remote_port, server_port, request_path, and querystring. You can clear the fields if required. ● If you add your web services to WAF in hybrid cloud mode, you can deliver the request_header, request_body, response_info, and hostname fields and specify the lengths of the request_body and response_info fields for delivery. The Compression Type and Custom CA parameters are added to deliver hybrid cloud logs to ApsaraMQ for Kafka. Experience optimization: ● The features on the hybrid cloud log management page are integrated into the Log Service page. You can manage log delivery settings in a centralized manner. ● You can click the protected object drop-down list on the Log Service page to check whether the Simple Log Service for WAF feature is enabled for protected objects. ● You can enable or disable the Simple Log Service for WAF feature and hybrid cloud log delivery for multiple protected objects at a time.