IP Library Granted Patent US 11,687,569
Granted Patent B2
US 11,687,569 · App. 17/690,304 · Granted Jun 27, 2023

Optimizing role level identification for resource allocation

Inventors: Vasudha Shivamoggi (Arlington, MA); Wah-Kwan Lin (Melrose, MA); Roy Hodgman (Cambridge, MA)
Assignee: Rapid7, Inc.
G06F16/285G06F16/215G06F16/288G06Q10/06313H04L63/102H04L63/104
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 11,687,569
App. No.
17/690,304
Granted
Jun 27, 2023
Kind
B2
Abstract

Disclosed herein are methods, systems, and processes to optimize role level identification for computing resource allocation to perform security operations in networked computing environments. A role level classifier to process a training dataset that corresponds to a clean title is generated from a subset of entities associated with the clean title. An initial effective title determined by the role level classifier based on processing the training dataset is assigned to an entity. A new effective title based on feature differences between the initial effective title and the clean title is re-assigned to the entity. Performance of the generating, the assigning, and the re-assigning is repeated using the new effective title instead of the clean title.

Claims (62)

1. A computer-implemented method, comprising:

accessing a training dataset that comprises an entity that is associated with a clean title;

training a role level classifier to process the entity in the training dataset;

assigning an initial effective title determined by the role level classifier to the entity;

re-assigning a new effective title to the entity based on at least a feature difference between the initial effective title and the clean title;

processing the entity in the training dataset using the new effective title instead of the clean title to generate a final effective title;

determining whether the final effective title is designated higher than the clean title; and

allocating one or more security resources to the entity if the final effective title is designated higher than the clean title or de-allocating the one or more security resources from the entity if the final effective title is designated lower than the clean title.

2. The computer-implemented method of claim 1 , further comprising:

continually processing the entity with the trained role level classifier using the new effective title until a subsequent effective title generated for the entity by the role level classifier stops changing.

3. The computer-implemented method of claim 2 , further comprising:

storing a modified role level identifier for the entity in a catalog.

4. The computer-implemented method of claim 3 , further comprising:

maintaining the catalog of a plurality of modified role identifiers that comprises the modified role level identifier independently from a directory service.

5. The computer-implemented method of claim 4 , further comprising:

determining that the modified role identifier matches the new effective title assigned to the entity; and

the new effective title that is different than the clean title of the entity provided by the directory service.

6. The computer-implemented method of claim 5 , further comprising:

designating the entity and one or more network assets associated with the entity as vulnerable; and

performing one or more security actions applicable to the entity.

7. A non-transitory computer readable storage medium comprising program instructions executable to comprising program instructions executable to:

access a training dataset that comprises an entity that is associated with a clean title;

train a role level classifier to process the entity in the training dataset;

assign an initial effective title determined by the role level classifier to the entity;

re-assign a new effective title to the entity based on at least a feature difference between the initial effective title and the clean title;

process the entity in the training dataset using the new effective title instead of the clean title to generate a final effective title;

determine whether the final effective title is designated higher than the clean title; and

allocate one or more security resources to the entity if the final effective title is designated higher than the clean title or de-allocating the one or more security resources from the entity if the final effective title is designated lower than the clean title.

8. The non-transitory computer readable storage medium of claim 7 , further comprising:

continually processing the entity with the trained role level classifier using the new effective title until a subsequent effective title generated for the entity by the role level classifier stops changing.

9. The non-transitory computer readable storage medium of claim 8 , further comprising:

storing a modified role level identifier for the entity in a catalog.

10. The non-transitory computer readable storage medium of claim 9 , further comprising:

maintaining the catalog of a plurality of modified role identifiers that comprises the modified role level identifier independently from a directory service.

11. The non-transitory computer readable storage medium of claim 10 , further comprising:

determining that the modified role identifier matches the new effective title assigned to the entity; and

the new effective title that is different than the clean title of the entity provided by the directory service.

12. The non-transitory computer readable storage medium of claim 11 , further comprising:

designating the entity and one or more network assets associated with the entity as vulnerable; and

performing one or more security actions applicable to the entity.

13. A system comprising:

one or more processors; and

a memory coupled to the one or more processors, wherein the memory stores program instructions executable by the one or more processors to:

access a training dataset that comprises an entity that is associated with a clean title;

train a role level classifier to process the entity in the training dataset;

assign an initial effective title determined by the role level classifier to the entity;

re-assign a new effective title to the entity based on at least a feature difference between the initial effective title and the clean title;

process the entity in the training dataset using the new effective title instead of the clean title to generate a final effective title;

determine whether the final effective title is designated higher than the clean title; and

allocate one or more security resources to the entity if the final effective title is designated higher than the clean title or de-allocating the one or more security resources from the entity if the final effective title is designated lower than the clean title.

14. The system of claim 13 , further comprising:

continually processing the entity with the trained role level classifier using the new effective title until a subsequent effective title generated for the entity by the role level classifier stops changing.

15. The system of claim 14 , further comprising:

storing a modified role level identifier for the entity in a catalog.

16. The system of claim 15 , further comprising:

maintaining the catalog of a plurality of modified role identifiers that comprises the modified role level identifier independently from a directory service.

17. The system of claim 16 , further comprising:

determining that the modified role identifier matches the new effective title assigned to the entity; and

the new effective title that is different than the clean title of the entity provided by the directory service.

18. The system of claim 17 , further comprising:

designating the entity and one or more network assets associated with the entity as vulnerable; and

performing one or more security actions applicable to the entity.

Assignments (2)
SECURITY INTEREST Recorded Jun 26, 2025
From: RAPID7, INC.; RAPID7 LLC
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 071743/0537 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 9, 2022
From: SHIVAMOGGI, VASUDHA; LIN, WAH-KWAN; HODGMAN, ROY
To: RAPID7, INC.
Reel/Frame 059208/0100 →
Continuity (2)
Continuation 16153929 · Oct 8, 2018
Related Publication 20220197930A1 · Jun 23, 2022