Forum Discussion
ASM ready to be enforced
Think about staging as a timer which was set to 7 days. Now, each time there is a policy change event on the staged entity, the timer is reset back to count down 7 days again. Example: you have a new parameter called username which you configured with a specific character set - only allow a-z and A-Z characters. After 2 days, you see a request with the O'reilly value in the username parameter and you have a suggestion to accept the ' metacharacter on the username parameter value. At this moment, the staging timer has 5 days left, however, if you accept the learning suggestion, it will reset itself to 7 Days and start to count down again. The reason behind this functionality is to give the ASM admin a period (staging period) in which if this time has passed , and no changes happened to the staged entity (it can a parameter, a file , a URL etc.) it means that this entity's configuration is accurate (it doesn't create false positives anymore)and it is ready to be enforced. Ya Salam.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)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