Automated policies make it easy for Anypoint Platform administrators to satisfy compliance in common security and logging requirements by automatically applying the same set of policies to all of your APIs.
This allows API owners to deploy with confidence knowing that the environment in which they are deploying will have critical policies enforced automatically which ensures consistency and reduce possible errors because an administrator no longer needs to remember to insert a policy to enforce common standards manually
API owners can continue to design, build and deploy APIs quickly without compromising security because your best practices are built into the application network.
Automated policies are only available for Mule 4 APIs using a MuleSoft-hosted control plane.
Automated policies support all runtime deployment targets (CloudHub, Runtime Fabric, and Hybrid).
Automated policies have priority over the same type of policy applied to a specific API proxy.
For example, if an API proxy running Mule 4.1.2 has an IP whitelist policy to allow only the IP range 192.168.100.0/22 (from 192.168.100.0 to 192.168.103.255), and a new IP Whitelist automated policy is created to only allow the IP range 192.168.100.14/24 (from 192.168.100.0 to 192.168.100.255) and is applied to all supported runtime versions (4.1.1 and above), then this latter automated policy will prevail over the former provided policy.
Note that in the above example, the IP range changed when the automated policy was applied.
Additionally, if there is an automated policy already applied, you cannot apply that specific type of policy as a provided policy in a specific API proxy.