Forum Discussion
Policy buiding for multiple VS's
The blocking action will only occur on those violations which are enforced after the enforcement readiness period expires. Think attack signatures, and any specific entity learning (parameters, file types, etc.) for which learning is enabled. During the enforcement readiness period, attack signatures are in staging. They won't be enforced until the period expires and no violations have been seen. Those violations are related to the application. If you export that policy to a new virtual server, but the application is different, then all of the learning done by that policy is meaningless because the app is different. In the case of a new/different application, start with a new policy. If the app is the same, then the policy would pick up where it left off in terms of learning. But do not forget that the automatic policy is in blocking mode by default. This means that enforcement of attack signatures and/or other entities can result in false positives if anything changes on the application. Make sense?
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