See fraud control gaps by attack

Tick the controls in place to see which fraud attacks they cover, partly cover or miss.

Fraud controls in place

The controls shown in this demo are made up.

Attack types covered

4 out of 11
Covered4
Partly covered6
Gap1

Adding Consortium data would cover 5 more attack types.

Attacks to cover

    Attack types and controls

    Stops this attack Helps against this attack Control not in place

    This map is a general rule of thumb. A control in place may still need tuning to stop an attack.

    Get the result by email

    Run fraud controls as one decision flow so each check runs where it is needed and every result feeds the same decision. Start your trial

    How the map sets coverage

    Each attack has controls marked as stopping it by design and controls marked as helping against it. The status follows the controls selected.

    Covered: An attack is covered when at least one control that stops it is in place.
    Partly covered: An attack is partly covered when only controls that help against it are in place.
    Gap: An attack is a gap when no control that stops it or helps against it is in place.

    The example below shows the first attack that is not covered and the controls in place that apply to it.

    Forged documents
      –
    = Gap

    The map is a general rule of thumb and does not test the controls selected. A control may be tuned too loosely to stop an attack, even when the map marks it as stopping that attack.

    Fraud control gaps by attack

    The coverage map lays out fraud attack types against the controls in place. It marks each attack covered when a control stops it, partly covered when a control only helps, or a gap when no listed control applies.

    This gives a lender a view of where its fraud controls may leave attacks unaddressed. Use the result to see which unticked control would cover the most attacks, keeping in mind that the map is a general rule of thumb.

    Common questions

    How do I find fraud control gaps?

    Mark the fraud controls in place and compare them with the attacks in the coverage map. It shows which attacks are covered, partly covered or gaps.

    What is a fraud controls matrix?

    It lays out fraud attacks against controls and shows where each control stops an attack or only helps. This map also marks attacks with no relevant control in place as gaps.

    Which fraud controls cover account takeover?

    Device fingerprinting and behavioural checks stop account takeover by design in this map. Email risk checks, IP and proxy checks, velocity rules and consortium data help against it.

    What does partly covered mean?

    It means only controls that help against the attack are in place. The map distinguishes those controls from ones that stop the attack by design.

    How do I choose which fraud control to add?

    The result names the unticked control that would cover the most attacks not covered by the controls in place. Use it as a starting point, since the map is a general rule of thumb.