Forum Discussion

1 Reply

  • F5 uses the Luhn algorithm to check the CC number, any sequence that is not a valid CC number should not be matched. So unless your GUID matches a valid CC number, or you face some unknown bug, there shouldn't be any violation. If you suspect an abnormal behavior, I suggest you contact F5 support.

     

    From K8638:

     

    Once Data Guard locates a pattern matching a credit card number, the BIG-IP ASM system will apply the Luhn algorithm (MOD 10) to the number. If the number is a valid Luhn number, and the length and prefix matches a valid credit card number, the data is blocked or scrubbed by Data Guard.