Usage of ASM Parent and Child Policies

There are three main use cases for deploying a Parent policy:

1. To impose mandatory policy elements on all application security policies of the enterprise or on a subset of policies. For example, specific attack signatures protecting known vulnerabilities will be imposed on all public facing applications. The policies with mandated configuration elements are defined by security administrators in the enterprise.

    

2. To create and maintain policies that have common elements and settings. For example, the enterprise requires the same blocking response page for all policies and also requires common geolocation enforcement settings across all policies.

    

3. To push change(s) to multiple policies. For example, information leakage or HTTP RFC compliance security requirements have changed and there are 50 policies that are affected.