Contextual mapping of web-pages, and generation of fraud-relatedness score-values
Devices, systems, and methods of contextual mapping of web-page elements and other User Interface elements, for the purpose of differentiating between fraudulent transactions and legitimate transactions, or for the purpose of distinguishing between a fraudulent user and a legitimate user. User Interface elements of a website or webpage or application or other computerized service, are contextually analyzed. A first User Interface element is assigned a low fraud-relatedness score-value, since user engagement with the first User Interface element does not create a security risk or a monetary exposure. A second, different, User Interface element is assigned a high fraud-relatedness score-value, since user engagement with the second User Interface element creates a security risk or a monetary exposure. The fraud-relatedness score-values are taken into account, together with user-specific behavioral characteristics, in order to determine whether to generate a possible-fraud notification, or as part of generating a possible-fraud score for a particular set-of-operations.
1. A method comprising:
(a) automatically analyzing content of a banking or retailer website, by performing:
analyzing a log of historical transactions that are known to be fraudulent;
(b) constructing a lookup table that indicates (I) that a first GUI element is typically engaged by cyber-attackers as part of cyber-attacks, and (II) that a second GUI element is typically not engaged by cyber-attackers as part of cyber-attacks;
(c) generating a security-exposure map of on-screen GUI elements of said banking or retailer website,
by generating a first indication that user-engagement with a first particular on-screen GUI element on a particular web-page of said banking or retailer website creates a potential security risk for said banking or retailer website,
and by generating a second indication that user-engagement with a second particular on-screen GUI element on said particular web-page of said banking or retailer website does not create a potential security risk for said banking or retailer website.
2. The method of claim 1 ,
wherein web-pages of said banking or retailer website are HTML-based pages that are accessible through a web browser.
3. The method of claim 1 ,
wherein web-pages of said banking or retailer website are components of a native mobile application.
4. The method of claim 1 ,
wherein user-engagement with the first particular on-screen GUI element comprises engagement with said first particular on-screen GUI element via an input unit selected from the group consisting of: a mouse, a touchpad, a touch-screen;
wherein user-engagement with the second particular on-screen GUI element comprises engagement with said second particular on-screen GUI element via an input unit selected from the group consisting of: a mouse, a touchpad, a touch-screen.
5. The method of claim 1 ,
wherein said user-engagement with the first particular on-screen GUI element comprises engagement with said first particular on-screen GUI element via an input unit of a device selected from the group consisting of: a laptop computer, a desktop computer, a tablet, a smartphone;
wherein said user-engagement with the second particular on-screen GUI element comprises engagement with said second particular on-screen GUI element via an input unit of a device selected from the group consisting of: a laptop computer, a desktop computer, a tablet, a smartphone.
6. A non-transitory storage medium having stored thereon instructions that, when performed by a process, cause the processor to perform a method comprising:
(a) automatically analyzing content of a banking or retailer website, by performing:
analyzing a log of historical transactions that are known to be fraudulent;
(b) constructing a lookup table that indicates (I) that a first GUI element is typically engaged by cyber-attackers as part of cyber-attacks, and (II) that a second GUI element is typically not engaged by cyber-attackers as part of cyber-attacks;
(c) generating a security-exposure map of on-screen GUI elements of said banking or retailer website,
by generating a first indication that user-engagement with a first particular on-screen GUI element on a particular web-page of said banking or retailer website creates a potential security risk for said banking or retailer website,
and by generating a second indication that user-engagement with a second particular on-screen GUI element on said particular web-page of said banking or retailer website does not create a potential security risk for said banking or retailer website.
7. The non-transitory storage medium of claim 6 ,
wherein web-pages of said banking or retailer website are HTML-based pages that are accessible through a web browser.
8. The non-transitory storage medium of claim 6 ,
wherein web-pages of said banking or retailer website are components of a native mobile application.
9. The non-transitory storage medium of claim 6 ,
wherein user-engagement with the first particular on-screen GUI element comprises engagement with said first particular on-screen GUI element via an input unit selected from the group consisting of: a mouse, a touchpad, a touch-screen;
wherein user-engagement with the second particular on-screen GUI element comprises engagement with said second particular on-screen GUI element via an input unit selected from the group consisting of: a mouse, a touchpad, a touch-screen.
10. The non-transitory storage medium of claim 6 ,
wherein said user-engagement with the first particular on-screen GUI element comprises engagement with said first particular on-screen GUI element via an input unit of a device selected from the group consisting of: a laptop computer, a desktop computer, a tablet, a smartphone;
wherein said user-engagement with the second particular on-screen GUI element comprises engagement with said second particular on-screen GUI element via an input unit of a device selected from the group consisting of: a laptop computer, a desktop computer, a tablet, a smartphone.
11. A system comprising:
a fraud detection and mitigation unit,
implemented by at least a processor to execute code and a memory unit to store code,
wherein the fraud detection and mitigation unit is configured to perform:
(a) automatically analyzing content of a banking or retailer website, by performing:
analyzing a log of historical transactions that are known to be fraudulent;
(b) constructing a lookup table that indicates (I) that a first GUI element is typically engaged by cyber-attackers as part of cyber-attacks, and (II) that a second GUI element is typically not engaged by cyber-attackers as part of cyber-attacks;
(c) generating a security-exposure map of on-screen GUI elements of said banking or retailer website,
by generating a first indication that user-engagement with a first particular on-screen GUI element on a particular web-page of said banking or retailer website creates a potential security risk for said banking or retailer website,
and by generating a second indication that user-engagement with a second particular on-screen GUI element on said particular web-page of said banking or retailer website does not create a potential security risk for said banking or retailer website.
12. The system of claim 11 ,
wherein web-pages of said banking or retailer website are HTML-based pages that are accessible through a web browser.
13. The system of claim 11 ,
wherein web-pages of said banking or retailer website are components of a native mobile application.
14. The system of claim 11 ,
wherein user-engagement with the first particular on-screen GUI element comprises engagement with said first particular on-screen GUI element via an input unit selected from the group consisting of: a mouse, a touchpad, a touch-screen;
wherein user-engagement with the second particular on-screen GUI element comprises engagement with said second particular on-screen GUI element via an input unit selected from the group consisting of: a mouse, a touchpad, a touch-screen.
15. The system of claim 11 ,
wherein said user-engagement with the first particular on-screen GUI element comprises engagement with said first particular on-screen GUI element via an input unit of a device selected from the group consisting of: a laptop computer, a desktop computer, a tablet, a smartphone;
wherein said user-engagement with the second particular on-screen GUI element comprises engagement with said second particular on-screen GUI element via an input unit of a device selected from the group consisting of: a laptop computer, a desktop computer, a tablet, a smartphone.