Forum Discussion
Jan 08, 2019
ASM violate_details construction explained
We send the ASM log to a 3rd party SIEM. I could not find a document explaining the detail of the XML variable "violate_details".
The parameter name & value are Base64 encoded.
Does anyone has a...
samstep
Cirrocumulus
Jan 20, 2019The problem seem to be in the SIEM and its format. To assist the investigation it is best to use SupportID to search for the request which triggered the violation in F5 ASM WEB GUI and compare with the one logged by SIEM
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects