IP Library Granted Patent US 9,253,207
Granted Patent B2
US 9,253,207 · App. 13/763,538 · Granted Feb 2, 2016

Collaborative phishing attack detection

Inventors: Aaron Higbee (Leesburg, VA); Rohyt Belani (New York, NY); Scott Greaux (Glenmont, NY)
Assignee: PhishMe, Inc.
H04L63/1475H04L63/1408
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 9,253,207
App. No.
13/763,538
Granted
Feb 2, 2016
Kind
B2
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 (49)

1. A method, comprising:

generating, by a network device, a simulated phishing message, the message comprising a predetermined identifier in the message or in metadata of the message;

electronically storing, by the network device, the predetermined identifier in a computerized data store;

receiving, by the network device from a computing device associated with an individual, a notification triggered by a user action by the individual that a message delivered in an account associated with the individual has been identified by the individual as a possible phishing attack;

determining, by the network device, whether the identified message is a known simulated phishing attack by comparing the predetermined identifier to an identifier from the body of the message or to the metadata of the message;

if the message is identified by the individual as a simulated phishing attack, recording in a database that the individual has correctly identified the message as a possible phishing attack;

if the message is determined not to be a known simulated phishing attack based on the comparison of the identifier, determining, at the network device, whether the identified message may be a threat based on at least whether the individual has correctly identified a previous message as a possible phishing attack;

processing, by the network device, the message based on the determination of whether the identified message may be a threat.

2. The method of claim 1 , wherein processing the message based on a trustworthiness level of the individual further comprises forwarding the message to a computer security technician for analysis to determine if the message is a real phishing attack or not.

3. The method of claim 1 , wherein a trustworthiness level of the individual is based on a rating assigned to the individual within a social network of the individual.

4. The method of claim 1 , wherein if the message is determined not to be a known simulated phishing attack based on the comparison of the identifier, classifying or not classifying the message as a real phishing attack based on a trustworthiness level the individual.

5. The method of claim 4 , wherein if the trustworthiness level of the individual exceeds a threshold, classifying the message as a real phishing attack, otherwise, not classifying the message as a real phishing attack.

6. The method of claim 1 , further comprising calculating a numerical value indicative of a likelihood the message is a real phishing attack based on a trustworthiness level of the individual.

7. The method of claim 1 , further comprising:

calculating an average of trustworthiness level of multiple individuals who have triggered a notification of the message; and

comparing the average with a threshold to classify or not classify the message as a real phishing attack.

8. The method of claim 1 , wherein a trustworthiness level of the individual is based on one or more of a percentage of simulated phishing attacks that the individual correctly identified as a possible phishing attack, a percentage of simulated phishing attacks that the individual ignored, and a percentage of simulated phishing attacks that the individual fell victim to.

9. The method of claim 1 , wherein a trustworthiness level of the individual is based on a sophistication level of a simulated phishing attack received by the individual.

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

11. A system comprising:

a processor;

a storage device connected to the processor;

a network server device; and

a set of instructions on the storage device that, when executed by the processor, cause the processor perform the steps of:

generating, by the processor, a simulated phishing message, the message comprising a predetermined identifier in the message or in metadata of the message;

electronically storing, on the storage device, the predetermined identifier in a computerized data store;

receiving, by the processor from a computing device associated with an individual, a notification triggered by a user action by the individual that a message delivered in an account associated with the individual has been identified by the individual as a possible phishing attack;

determining, by the processor, whether the identified message is a known simulated phishing attack by comparing the predetermined identifier to an identifier from the body of the message or to the metadata of the message;

if the message is identified by the individual as a simulated phishing attack, recording in a database that the individual has correctly identified the message as a possible phishing attack;

if the message is determined not to be a known simulated phishing attack based on the comparison of the identifier, determining, at the processor, whether the identified message may be a threat based on at least whether the individual has correctly identified a previous message as a possible phishing attack; and

processing, by the processor, the message based on the determination of whether the identified message may be a threat.

12. The system of claim 11 , wherein if the message is determined not to be a known simulated phishing attack based on the comparison of the identifier, classifying or not classifying the message as a real phishing attack based on a trustworthiness level the individual.

13. The system of claim 11 , wherein if the trustworthiness level of the individual exceeds a threshold, classifying the message as a real phishing attack, otherwise, not classifying the message as a real phishing attack.

14. The system of claim 11 , further comprising calculating a numerical value indicative of a likelihood the message is a real phishing attack based on the trustworthiness level of the individual.

15. A non-transitory computer-readable recording medium storing a simulated phishing message administration computer program, the simulated phishing message administration computer program causing a processor to perform steps comprising:

generating, by a network device, a simulated phishing message, the message comprising a predetermined identifier in the message or in metadata of the message;

electronically storing, by the network device, the predetermined identifier in a computerized data store;

receiving, by the network device from a computing device associated with an individual, a notification triggered by a user action by the individual that a message delivered in an account associated with the individual has been identified by the individual as a possible phishing attack;

determining, by the network device, whether the identified message is a known simulated phishing attack by comparing the predetermined identifier to an identifier from the body of the message or to the metadata of the message;

if the message is identified by the individual as a simulated phishing attack, recording in a database that the individual has correctly identified the message as a possible phishing attack;

if the message is determined not to be a known simulated phishing attack based on the comparison of the identifier, determining, at the network device, whether the identified message may be a threat based on at least whether the individual has correctly identified a previous message as a possible phishing attack; and

processing, by the network device, the message based on the determination of whether the identified message may be a threat.

16. The non-transitory computer-readable recording medium of claim 15 , wherein if the message is determined not to be a known simulated phishing attack based on the comparison of the identifier, classifying or not classifying the message as a real phishing attack based on a trustworthiness level the individual.

17. The non-transitory computer-readable recording medium of claim 15 , wherein if a trustworthiness level of the individual exceeds a threshold, classifying the message as a real phishing attack, otherwise, not classifying the message as a real phishing attack.

18. The non-transitory computer-readable recording medium of claim 15 , further comprising calculating a numerical value indicative of a likelihood the message is a real phishing attack based on a trustworthiness level of the individual.

19. The non-transitory computer-readable recording medium of claim 15 , further comprising:

calculating an average of trustworthiness level of multiple individuals who have triggered a notification of the message; and

comparing the average with a threshold to classify or not classify the message as a real phishing attack.

20. The non-transitory computer-readable recording medium of claim 15 , wherein a trustworthiness level of the individual is based on one or more of a percentage of simulated phishing attacks that the individual correctly identified as a possible phishing attack, a percentage of simulated phishing attacks that the individual ignored, and a percentage of simulated phishing attacks that the individual fell victim to.

Assignments (10)
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 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 18, 2014
From: HIGBEE, AARON; GREAUX, SCOTT
To: PHISHME, INC.
Reel/Frame 034546/0797 →
SECURITY AGREEMENT Recorded Nov 6, 2013
From: PHISHME INC.
To: SILICON VALLEY BANK
Reel/Frame 031597/0315 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 8, 2013
From: BELANI, ROHYT
To: PHISHME, INC.
Reel/Frame 029785/0015 →
Continuity (1)
Related Publication 20140230050A1 · Aug 14, 2014