IP Library Granted Patent US 8,719,940
Granted Patent B1
US 8,719,940 · App. 13/785,252 · Granted May 6, 2014

Collaborative phishing attack detection

Inventors: Aaron Higbee (Leesburg, VA); Rohyt Belani (New York, NY); Scott Greaux (Glenmont, NY)
Assignee: Phishme, Inc.
H04L63/145G06F21/56G06Q10/107
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,719,940
App. No.
13/785,252
Granted
May 6, 2014
Kind
B1
Abstract

Described herein are methods, network devices and machine-readable storage media for detecting whether a message is a phishing attack based on the collective responses from one or more individuals who have received that message. The individuals may flag the message as a possible phishing attack, and/or may provide a numerical ranking indicating the likelihood that the message is a possible phishing attack. As responses from different individuals may have a different degree of reliability, each response from an individual may be weighted with a corresponding trustworthiness level of that individual, in an overall determination as to whether a message is a phishing attack. A trustworthiness level of an individual may indicate a degree to which the response of that individual can be trusted and/or relied upon, and may be determined by how well that individual recognized simulated phishing attacks.

Claims (39)

1. A method, comprising:

receiving, at a first computer system, a notification that a message has been identified by one or more individuals as a possible phishing attack, the message having been received on a computing device of each of the one or more individuals;

determining, by the first computer system, whether the message is a known simulated phishing attack; and

if the message is a known simulated phishing attack, recording in a database that each of the one or more individuals has correctly identified the message as a possible phishing attack; otherwise,

if the message is not a known simulated phishing attack,

determining, by the first computer system, a trustworthiness level for each of the one or more individuals; and

processing, by the first computer system, the message based on the trustworthiness level of each of the one or more individuals to classify or not classify the message as a real phishing attack, wherein for a first one of the one or more individuals, the trustworthiness level of the first individual is based on one or more of:

a percentage of simulated phishing attacks that the first individual correctly identified as a possible phishing attack,

a percentage of simulated phishing attacks that the first individual ignored,

a percentage of simulated phishing attacks that the first individual fell victim to, a sophistication level of a simulated phishing attack received by the first individual,

a type of simulated phishing attack received by the first individual, a number of simulated phishing attacks that the first individual correctly identified as a possible phishing attack,

a number of simulated phishing attacks that the first individual ignored, and a number of simulated phishing attacks that the first individual fell victim to,

a number of real phishing attacks that the first individual correctly identified as a possible phishing attack,

a number of real phishing attacks that the first individual ignored,

a number of real phishing attacks that the first individual fell victim to,

a field of employment of the first individual,

an educational degree of the first individual,

a job position of the first individual, and

an employment history of the first individual.

2. The method of claim 1 , wherein a single graphical user interface action performed by a first one of the one or more individuals is sufficient to trigger the notification to be sent from the computing device of the first individual.

3. The method of claim 1 , wherein determining whether the message is a known simulated phishing attack comprises comparing characteristics of the message with a log of transmitted simulated phishing attacks.

4. The method of claim 3 , wherein characteristics of the message include one or more of a sender identifier of the message, a recipient identifier of the message, a subject of the message, a time of transmission of the message, and a header of the message.

5. The method of claim 1 , wherein determining whether the message is a known simulated phishing attack comprises analyzing characteristics of the message at a client-side plug-in.

6. The method of claim 1 , wherein determining whether the message is a known simulated phishing attack comprises comparing the message with simulated phishing attacks.

7. The method of claim 1 , wherein the first individual correctly identifying a more sophisticated simulated phishing attack results in a higher trustworthiness level for the first individual, as compared to the first individual correctly identifying a less sophisticated simulated phishing attack.

8. The method of claim 1 , wherein for a first one of the one or more individuals, the trustworthiness level of the first individual is based on a rating assigned to the first individual by each person within a social network of the first individual.

9. The method of claim 1 , wherein processing the message comprises classifying or not classifying the message as a real phishing attack based on the trustworthiness level of each of the one or more individuals.

10. The method of claim 9 , wherein the one or more individuals consists of a single individual and if the trustworthiness level of the single individual exceeds a threshold, classifying the message as a real phishing attack, otherwise, not classifying the message as a real phishing attack.

11. The method of claim 9 , wherein the one or more individuals comprises more than one individual, and if an average of the trustworthiness levels exceeds a threshold, classifying the message as a real phishing attack, otherwise, not classifying the message as a real phishing attack.

12. The method of claim 9 , wherein the one or more individuals comprises more than one individual, and further determining a maximum value of the trustworthiness levels and wherein, if the maximum value exceeds a threshold, classifying the message as a real phishing attack, otherwise, not classifying the message as a real phishing attack.

13. The method of claim 9 , wherein the one or more individuals comprises more than one individual, and further determining a number of the individuals with a trustworthiness level above a first threshold and wherein, if the number exceeds a second threshold, classifying the message as a real phishing attack, otherwise, not classifying the message as a real phishing attack.

14. The method of claim 1 , wherein processing the message comprises calculating a numerical value indicative of a likelihood the message is a real phishing attack based on the trustworthiness level of each of the one or more individuals.

15. A method, comprising:

receiving, at a first computer system, a notification that a message has been identified by one or more individuals as a possible phishing attack, the message having been received on a computing device of each of the one or more individuals;

determining, by the first computer system, whether the message is a known simulated phishing attack; and

if the message is a known simulated phishing attack, recording in a database that each of the one or more individuals has correctly identified the message as a possible phishing attack; otherwise,

if the message is not a known simulated phishing attack,

determining, by the first computer system, a trustworthiness level for each of the one or more individuals; and

processing, by the first computer system, the message based on the trustworthiness level of each of the one or more individuals to classify or not classify the message as a real phishing attack, wherein the one or more individuals comprises more than one individual, and if an average of the trustworthiness levels exceeds a threshold, classifying the message as a real phishing attack, otherwise, not classifying the message as a real phishing attack.

Assignments (9)
CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNEE BLUE TORCH FINANCE LLC PREVIOUSLY RECORDED ON REEL 059800 FRAME 0834. ASSIGNOR(S) HEREBY CONFIRMS THE SECURITY INTEREST. Recorded May 5, 2023
From: COFENSE INC.
To: BLUE TORCH FINANCE LLC
Reel/Frame 064381/0245 →
RELEASE OF SECURITY INTEREST Recorded May 6, 2022
From: ORIX GROWTH CAPITAL, LLC
To: COFENSE INC.; COFENSE BIDCO CORPORATION
Reel/Frame 059864/0955 →
SECURITY INTEREST Recorded May 3, 2022
From: COFENSE INC.
To: BLUE TORCH CAPITAL LP
Reel/Frame 059800/0834 →
SECURITY INTEREST Recorded Oct 4, 2021
From: COFENSE BIDCO CORPORATION; COFENSE INC.
To: ORIX GROWTH CAPITAL, LLC, AS ADMINSTRATIVE AGENT
Reel/Frame 057692/0722 →
RELEASE OF SECURITY INTEREST Recorded Oct 3, 2019
From: SILICON VALLEY BANK
To: COFENSE, INC.
Reel/Frame 050616/0262 →
SECURITY INTEREST Recorded Sep 24, 2019
From: COFENSE INC.
To: ORIX GROWTH CAPITAL, LLC
Reel/Frame 050478/0889 →
MERGER AND CHANGE OF NAME Recorded Jan 15, 2019
From: PHISHME INC; POSEIDON MERGER SUB 2 INC; COFENSE INC
To: COFENSE INC
Reel/Frame 048014/0092 →
SECURITY AGREEMENT Recorded Nov 6, 2013
From: PHISHME INC.
To: SILICON VALLEY BANK
Reel/Frame 031597/0315 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 5, 2013
From: HIGBEE, AARON; BELANI, ROHYT; GREAUX, SCOTT
To: PHISHME, INC.
Reel/Frame 029923/0388 →
Continuity (1)
Continuation 13763538 · Feb 8, 2013