Forum Discussion
F5Team
Cirrus
CirrusASM - Attack Signature - Miss Match on Active and Standby
ASM is on HA. Both are in Sync. We observe on multiple policies, that the number of signatures ready to be enforced and the suggestions available on Active and Standby are different. Is t...
Thanks for updating in regards to the screenshot which you had shared is of the same policy on Active and Standby
Do the config sync for ASM policies only on one of the devices in Cluster
Security -> Options -> Aplication Security -> Synchronization ->Application Security Synchronization
F5TeamI see it's configured on both Active and Standby devices.
So should the device groups be removed on the standby and when we sync again from active, do we see the numbers for signatures ready to be enforced and the suggestions matching.
What if the device failover and standby becomes active and it does not have the device group configured under below option so we cant sync the changes
Security -> Options -> Aplication Security -> Synchronization ->Application Security Synchronization
Would it have any other impact removing the device groups on one of the device.
- F5Team
Appreciate an update to this thread.