IP Library Granted Patent US 12,381,904
Granted Patent B2
US 12,381,904 · App. 17/721,589 · Granted Aug 5, 2025

Prioritization of reported messages

Inventor: Greg Kras (Dunedin, FL)
Assignee: KnowBe4, Inc.
H04L63/1441H04L51/08H04L51/21H04L63/1433H04L63/20
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 12,381,904
App. No.
17/721,589
Granted
Aug 5, 2025
Kind
B2
Abstract

Systems and methods for prioritization of reported messages and rewarding reporting users are disclosed. The systems and methods leverage knowledge and security awareness of the most informed users in an organization to protect an organization from serious harm from new malicious messages, give credit to the most informed users, and optimize threat triage and analysis. The system converts a reported malicious message to a defanged message. The system communicates the defanged message to a plurality of users. The system determines an impact score for the user based on interactions with the defanged message by the plurality of users, and with the impact score gives credit to the reporter and optimizes threat triage and analysis.

Claims (31)

1. A method comprising:

identifying, by one or more servers, that a message reported by a user as suspicious is a malicious message;

converting, by the one or more servers, the malicious message to a defanged message that has benign elements;

communicating, by the one or more servers, the defanged message to a plurality of users other than the user who received the message;

determining, by the one or more servers, an impact score for the user based at least on one or more interactions with at least the benign elements of the defanged message by the plurality of users; and

providing, by the one or more servers, a status to the user who reported the suspicious message based at least on the impact score.

2. The method of claim 1 , further comprising stripping, by the one or more servers, the malicious message.

3. The method of claim 2 , further comprising stripping the malicious message by one or more of the following: removing a harmful uniform resource locator (URL), removing an attachment, and disabling a macro.

4. The method of claim 1 , further comprising converting, by the one or more servers, the malicious message to the defanged message by one or more of the following: replacing a detonated uniform resource locator (URL) with a benign URL, replacing an attachment with a benign attachment, and replacing a disabled macro with a benign macro.

5. The method of claim 1 , further comprising communicating, by the one or more servers, the defanged message by replacing the malicious message with the defanged message in each mailbox of the plurality of users.

6. The method of claim 1 , further comprising tracking, by the one or more servers, one or more interactions with the defanged message by the plurality of users.

7. The method of claim 1 , further comprising determining, by the one or more servers, a difficulty score for the malicious message.

8. The method of claim 1 , further comprising determining, by the one or more servers, a dangerousness score for the malicious message.

9. The method of claim 7 , further comprising determining, by the one or more servers, the impact score using one of a difficulty score or dangerousness score for the malicious message.

10. The method of claim 1 , further comprising prioritizing, by the one or more servers, a subsequent reporting of a message as suspicious from the user in accordance with the impact score of the user.

11. A system comprising:

one or more processors, coupled to memory and configured to:

identify that a message reported by a user as suspicious is a malicious message;

convert the malicious message to a defanged message that has benign elements;

communicate the defanged message to a plurality of users other than the user who received the message;

determine an impact score for the user based at least on one or more interactions with at least the benign elements of the defanged message by the plurality of users; and

provide a status to the user who reported the suspicious message based at least on the impact score.

12. The system of claim 11 , wherein the one or more processors are further configured to strip the malicious message.

13. The system of claim 12 , wherein the one or more processors are further configured to strip the malicious message by one or more of the following: removing a harmful uniform resource locator (URL), removing an attachment, and disabling a macro.

14. The system of claim 11 , wherein the one or more processors are further configured to convert the malicious message to the defanged message by one or more of the following: replacing a detonated uniform resource locator (URL) with a benign URL, replacing an attachment with a benign attachment, and replacing a disabled macro with a benign macro.

15. The system of claim 11 , wherein the one or more processors are further configured to communicate the defanged message by replacing the malicious message with the defanged message in each mailbox of the plurality of users.

16. The system of claim 11 , wherein the one or more processors are further configured to track one or more interactions with the defanged message by the plurality of users.

17. The system of claim 11 , wherein the one or more processors are further configured to determine a difficulty score for the malicious message.

18. The system of claim 11 , wherein the one or more processors are further configured to determine a dangerousness score for the malicious message.

19. The system of claim 17 , wherein the one or more processors are further configured to determine the impact score using one of a difficulty score or dangerousness score for the malicious message.

20. The system of claim 11 , wherein the one or more processors are further configured to prioritize a subsequent reporting of a message as suspicious from the user in accordance with the impact score of the user.

Assignments (5)
PATENT SECURITY AGREEMENT Recorded Aug 8, 2025
From: KNOWBE4, INC.
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 072337/0277 →
RELEASE OF SECURITY INTEREST IN PATENT COLLATERAL RECORDED AT REEL/FRAME: 062627/0001 Recorded Jul 28, 2025
From: BLUE OWL CREDIT INCOME CORP. (FORMERLY KNOWN AS OWL ROCK CORE INCOME CORP.)
To: KNOWBE4, INC.
Reel/Frame 072108/0205 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 24, 2023
From: KRAS, GREG
To: KNOWBE4, INC.
Reel/Frame 062800/0822 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 24, 2023
From: KRAS, GREG
To: KNOWBE4, INC.
Reel/Frame 062801/0965 →
PATENT SECURITY AGREEMENT Recorded Feb 2, 2023
From: KNOWBE4, INC.
To: OWL ROCK CORE INCOME CORP., AS COLLATERAL AGENT
Reel/Frame 062627/0001 →