on an event’s attributes • Best for detecting potential fraud when historical account/user data is limited • Inspired by models and techniques used to protect Amazon.com/AWS account registration • Use cases: new account, first transaction, guest checkout • Inputs: 3 required data elements and 50+ optional
Variable 2 Variable N EVENT_LABEL 4/10/2019 11:05 … … … Legit / 0 4/10/2019 19:34 … … … Legit / 0 4/10/2019 20:29 … … ... Fraud / 1 … … … … … Required Required At least 2 variables required (max 100) At least 10K total examples At least 500 fraud examples • Data must reside in S3 (same region with AFD) • Data should be in CSV format • First line of CSV file should have headers • 2 required headers: EVENT_TIMESTAMP and EVENT_LABEL (they should not have any NULL or missing values) • Maximum file size of 5GB • Minimum 6 weeks of data • Recommended: 3-6 months of data • AFD can handle NULL and missing values (for variables)
decision threshold for the best separation between fraud and legits • Confusion matrix • Easily control the trade- off between FP and FN Part of Fraud Detector UI