ASM application security synchronization

Did you verify that the actual ASM Policy content was synced, or was it just the policy name attached to an empty policy?

An ASM policy consists of an entry in the

bigip.conf

, which just tells mcpd that there is an ASM policy of that name, and an ASM database entry.

If mcpd sees ASM policy names in

bigip.conf

without the matching ASM database policy data, the policies will be auto-created as empty (and transparent) ASM policies.

The actual policy configuration settings are stored by ASM in a mysql database - this is what is managed by ASM policy synchronization.

I suspect that you managed to sync the policy names but not the Policy settings.

Of course, it could be a new issue.