Forum Discussion
Enforcement Readiness Summary and HTTP Protocol Compliance
Hi Piotr, i can't explain the 9 "Not Enforced" configuration I'm afraid, looks odd to me. I'm probably being too simplistic here, but Enforcement Readiness and whether you Enforce, or items are Ready to be Enforced, is just a simple way of removing the Staging check against an item. Staging is there to not block whilst ASM learns the properties of that item, i.e. the query length of an allowed File Type. Because HTTP Protocol Compliance (and Evasion Techniques) don't have properties then there is no Staging check for them. Hence N/A against enforcing these items. For me, this makes sense.
Obviously the 9 doesn't make sense, can you click on this number?
Not sure about the Bad Host Header bit, can you confirm this again please?
N
Recent Discussions
Related Content
* 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