What to do if you’re under a fraud attack!
I have a CSM
If you received an email that you are under a fraud attack, you can expect your CSM to reach out with an analysis outlining:
- Why the alert was triggered
- The leading Indicators behind the fraud attack (e.g. IP fraud ring)
- Contributing Entities
- Entities with shared attributes that contributed to the attack (e.g. these 15 distinct entities shared the same IP address)
- Which shared attributes appeared in conjunction with each other (e.g. these 30 entities had the same IP address and phone number)
- Near-term and short-term recommendations
- Immediate recommendations to stop the bleed e.g. routing applicants through DocV or temporarily tightening IEV on the leading indicator (e.g. in the above example we’d tighten IEV on IP velocity).
- Reroute to your safety Journey/Workflow if you have it set up already!
- Long-term policy recommendations to prevent this type of attack from impacting your FI in the future
- Immediate recommendations to stop the bleed e.g. routing applicants through DocV or temporarily tightening IEV on the leading indicator (e.g. in the above example we’d tighten IEV on IP velocity).
While you wait for your CSM to reach out, you can navigate to the Alloy dashboard > Workflow Analytics tab to:
- View the leading Indicators of the fraud attack
- Filter the Application Queue by the fraud attack timeframe to see which entities came in during that period
- Check to make sure you’re decisioning on IEV! This is the lowest hanging fruit for stopping PII velocity based fraud attacks (most common)
I don’t have a CSM
You can navigate to the Alloy dashboard to:
- Understand why the alert was triggered
- Navigate to the Workflow Analytics tab
- View the leading Indicators of the fraud attack, shown in order from highest to lowest
- Contributing entities
- Filter the Application Queue by the fraud attack timeframe + leading indicators to see which entities came in during that period
- Check to make sure you’re decisioning on IEV! This is the lowest hanging fruit for stopping PII velocity based fraud attacks (most common)
- If you’re not, here’s how we recommend setting up IEV
Comments
0 comments
Please sign in to leave a comment.