Loading...
Loading...
JSON profile signature override does not include legacy signature after Automatic Signature Update (ASU).
-- Unexpected block on a previously white-listed signature. -- Confusing logging for why the signature was blocked (should indicate it was due to using an old signature version).
Signature override on content profile ASU with major update to targeted sig.
-- Create the signature override at higher context, e.g., the URL. Removing the URL context override again keeps it fixed. -- Enforce new version of sig globally.
Signature Overrides for Content Profiles now work after signature update.
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.