Forum Discussion
John_Buchanan
Jan 18, 2016Nimbostratus
I discovered that this was due to parameters defined within my policy with unusual names that were also nearly identical across my two ASM pair. I am once again able to import my policy from pair 1 on pair 2, and vice versa. I'll have to find another way to prevent these unusually named parameters from being flagged as injection attempts.