Sep 30, 2026— Improvements to Web Security Analytics
in about 2 hours
Enhancements:
- Support for Firewall for AI in the Samples view. You can now analyze requests that triggered Firewall for AI rules using three new dedicated fields in the Samples view: Transmission Protocol, Original Request ID, and Late Deny.
Bug fixes:
- Reliable feedback submission in AI Assistant. You can now consistently submit updated feedback and enter comments without interruptions, even after restarting a chat session.
- Clean text formatting in AI Assistant chat responses. AI Assistant chat responses now render with proper line breaks and clear text formatting.
- Seamless custom rule creation from remediable insights. You can now create custom rules from remediable insights directly within AI Assistant without chat delays or interruptions.
- Accurate retrieval of additional remediable insights. Selecting Show me more remediable insights in AI Assistant now consistently loads new, unique insights for your review.
- Formatted Markdown hyperlinks in AI Assistant chat. AI Assistant now presents clean, clickable hyperlinks with descriptive text to simplify navigation.
- Consistent widget display during data loading. Chart widgets in Web Security Analytics now display complete frames immediately on page load while background queries execute.
- Updated tracking links for remediable insights. The tracking links provided during guided remediation in AI Assistant now direct you to the specific security configuration version created for the update rather than taking you to a general configuration versions list.
- Updated Bot Score filter validation. The Bot Score filter now accepts numerical score ranges to ensure accurate and reliable query results.
- Reliable time range retention when updating saved views. Web Security Analytics now validates and preserves your selected date range when you update saved views, ensuring seamless updates across custom timeframes.
- Corrected Transmission Protocol display logic in Samples view. We updated the Samples view to ensure standard HTTP values do not populate the Transmission Protocol field. The field now remains omitted for standard HTTP sessions, displaying transport protocols only when persistent streaming or WebSocket channels (such as WSS, SSE, or JSONL) are used.
