IP Library Granted Patent US 11,140,190
Granted Patent B2
US 11,140,190 · App. 16/168,299 · Granted Oct 5, 2021

Automated user module assessment

Inventors: Richard A. Ford (Austin, TX); Roman Kleiner (San Diego, CA)
Assignee: Forcepoint, LLC
H04L63/1433H04L63/0236H04L63/0485H04L63/1425H04L63/20H04L67/142H04L67/146H04L67/2814
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,140,190
App. No.
16/168,299
Granted
Oct 5, 2021
Kind
B2
Abstract

A method, system and computer-usable medium for automating the assessment of security vulnerabilities associated with a user module via a user module assessment operation. The user assessment operation includes receiving a request from a user module via an edge device; determining whether the request includes a persistent session cookie; determining whether the user module should be assessed to detect security vulnerabilities; resetting information contained in the persistent session cookie when the user module should be accessed to detect security vulnerabilities; redirecting the user module for assessment; and, performing an assessment of the user module to detect possible security vulnerabilities.

Claims (59)

1. A computer-implementable method for performing a user module assessment operation, comprising:

receiving a request from a user module via an edge device, the user module executing on a protected endpoint, the protect endpoint comprising an endpoint device and an endpoint agent, the endpoint agent executing on a hardware processor of the endpoint device;

determining whether the user module should be assessed to detect security vulnerabilities, the security vulnerabilities comprising a weakness which can be exploited to perform unauthorized actions within the endpoint device;

setting user module information when the user module should be assessed to detect security vulnerabilities;

redirecting the user module for assessment;

performing, via a user module assessment system, an assessment of the user module to detect possible security vulnerabilities, the user module assessment system executing on the edge device; and,

storing the user module information within a persistent session cookie, the persistent session cookie being stored on the protected endpoint, the persistent session cookie comprising a persistent cookie aspect and a session cookie aspect to persistently store information associated with a user and the user module assessment system, the persistent cookie aspect of the persistent session cookie not expiring and the session cookie aspect of the persistent session cookie containing information related to a session between the user module and the user module assessment system.

2. The method of claim 1 , further comprising:

determining whether the request has a related persistent session cookie; and,

generating the persistent session cookie when the request does not have a related persistent session cookie.

3. The method of claim 1 , further comprising:

processing the persistent session cookie to determine when a session last occurred prior to determining whether the user module should be assessed for security vulnerabilities.

4. The method of claim 1 , wherein:

redirecting the user module comprises a transparent traffic routing approach, the transparent traffic routing approach comprising at least one of a Generic Routing Encapsulation (GRE) traffic routing approach, an Internet Protocol Security (IPSec) traffic routing approach, a Layer 3 (L3) traffic interception traffic routing approach, and a proxy auto-config (PAC) file traffic routing approach.

5. The method of claim 1 , further comprising:

updating the persistent session cookie to reflect that no security vulnerabilities were detected when the assessment of the user module to detect possible security vulnerabilities does not detect any possible security vulnerabilities.

6. The method of claim 1 , wherein:

the persistent session cookie is implemented to contain certain session information, the session information including at least one of information related to the user module, an associated user module endpoint device, a user associated with the user module, temporal information related to the user module, user behavior information associated with a session, and contextual information associated with the session.

7. A system comprising:

a processor;

a data bus coupled to the processor; and

a non-transitory, computer-readable storage medium embodying computer program code, the non-transitory, computer-readable storage medium being coupled to the data bus, the computer program code interacting with a plurality of computer operations and comprising instructions executable by the processor and configured for:

receiving a request from a user module via an edge device, the user module executing on a protected endpoint, the protect endpoint comprising an endpoint device and an endpoint agent, the endpoint agent executing on a hardware processor of the endpoint device;

determining whether the user module should be assessed to detect security vulnerabilities, the security vulnerabilities comprising a weakness which can be exploited to perform unauthorized actions within the endpoint device;

setting user module information when the user module should be assessed to detect security vulnerabilities;

redirecting the user module for assessment;

performing, via a user module assessment system, an assessment of the user module to detect possible security vulnerabilities, the user module assessment system executing on the edge device; and,

storing the user module information within a persistent session cookie, the persistent session cookie being stored on the protected endpoint, the persistent session cookie comprising a persistent cookie aspect and a session cookie aspect to persistently store information associated with a user and the user module assessment system, the persistent cookie aspect of the persistent session cookie not expiring and the session cookie aspect of the persistent session cookie containing information related to a session between the user module and the user module assessment system.

8. The system of claim 7 , wherein the instructions executable by the processor are further configured for:

determining whether the request has a related persistent session cookie; and,

generating the persistent session cookie when the request does not have a related persistent session cookie.

9. The system of claim 7 , wherein the instructions executable by the processor are further configured for:

processing the persistent session cookie to determine when a session last occurred prior to determining whether the user module should be assessed for security vulnerabilities.

10. The system of claim 7 , wherein:

redirecting the user module comprises a transparent traffic routing approach, the transparent traffic routing approach comprising at least one of a Generic Routing Encapsulation (GRE) traffic routing approach, an Internet Protocol Security (IPSec) traffic routing approach, a Layer 3 (L3) traffic interception traffic routing approach, and a proxy auto-config (PAC) file traffic routing approach.

11. The system of claim 7 , wherein the instructions executable by the processor are further configured for:

updating the persistent session cookie to reflect that no security vulnerabilities were detected when the assessment of the user module to detect possible security vulnerabilities does not detect any possible security vulnerabilities.

12. The system of claim 7 , wherein:

the persistent session cookie is implemented to contain certain session information, the session information including at least one of information related to the user module, an associated user module endpoint device, a user associated with the user module, temporal information related to the user module, user behavior information associated with a session, and contextual information associated with the session.

13. A non-transitory, computer-readable storage medium embodying computer program code, the computer program code comprising computer executable instructions configured for:

receiving a request from a user module via an edge device, the user module executing on a protected endpoint, the protect endpoint comprising an endpoint device and an endpoint agent, the endpoint agent executing on a hardware processor of the endpoint device;

determining whether the user module should be assessed to detect security vulnerabilities, the security vulnerabilities comprising a weakness which can be exploited to perform unauthorized actions within the endpoint device;

setting user module information when the user module should be accessed to detect security vulnerabilities;

redirecting the user module for assessment;

performing, via a user module assessment system, an assessment of the user module to detect possible security vulnerabilities, the user module assessment system executing on the edge device; and,

storing the user module information within a persistent session cookie, the persistent session cookie being stored on the protected endpoint, the persistent session cookie comprising a persistent cookie aspect and a session cookie aspect to persistently store information associated with a user and the user module assessment system, the persistent cookie aspect of the persistent session cookie not expiring and the session cookie aspect of the persistent session cookie containing information related to a session between the user module and the user module assessment system.

14. The non-transitory, computer-readable storage medium of claim 13 , wherein the computer executable instructions are further configured for:

determining whether the request has a related persistent session cookie;

generating the persistent session cookie when the request does not have a related persistent session cookie.

15. The non-transitory, computer-readable storage medium of claim 13 , wherein the computer executable instructions are further configured for:

processing the persistent session cookie to determine when a session last occurred prior to determining whether the user module should be assessed for security vulnerabilities.

16. The non-transitory, computer-readable storage medium of claim 13 , wherein:

redirecting the user module comprises a transparent traffic routing approach, the transparent traffic routing approach comprising at least one of a Generic Routing Encapsulation (GRE) traffic routing approach, an Internet Protocol Security (IPSec) traffic routing approach, a Layer 3 (L3) traffic interception traffic routing approach, and a proxy auto-config (PAC) file traffic routing approach.

17. The non-transitory, computer-readable storage medium of claim 13 , wherein the computer executable instructions are further configured for:

updating the persistent session cookie to reflect that no security vulnerabilities were detected when the assessment of the user module to detect possible security vulnerabilities does not detect any possible security vulnerabilities.

18. The non-transitory, computer-readable storage medium of claim 13 , wherein:

the persistent session cookie is implemented to contain certain session information, the session information including at least one of information related to the user module, an associated user module endpoint device, a user associated with the user module, temporal information related to the user module, user behavior information associated with a session, and contextual information associated with the session.

19. The non-transitory, computer-readable storage medium of claim 13 , wherein the computer executable instructions are deployable to a client system from a server system at a remote location.

20. The non-transitory, computer-readable storage medium of claim 13 , wherein the computer executable instructions are provided by a service provider to a user on an on-demand basis.

Assignments (8)
RELEASE OF SECURITY INTEREST Recorded Apr 2, 2025
From: UBS AG, STAMFORD BRANCH
To: FORCEPOINT, LLC; BITGLASS, LLC
Reel/Frame 070706/0263 →
SECURITY INTEREST Recorded Apr 1, 2025
From: FORCEPOINT LLC; BITGLASS, LLC
To: SOCIÉTÉ GÉNÉRALE
Reel/Frame 070703/0887 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 16, 2021
From: FORD, RICHARD A.
To: FORCEPOINT, LLC
Reel/Frame 057496/0210 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 19, 2021
From: FORCEPOINT FEDERAL HOLDINGS LLC
To: FORCEPOINT LLC
Reel/Frame 057001/0057 →
CHANGE OF NAME Recorded May 12, 2021
From: FORCEPOINT LLC
To: FORCEPOINT FEDERAL HOLDINGS LLC
Reel/Frame 056214/0798 →
PATENT SECURITY AGREEMENT Recorded Jan 20, 2021
From: REDOWL ANALYTICS, INC.; FORCEPOINT LLC
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 055052/0302 →
RELEASE OF SECURITY INTEREST IN PATENTS Recorded Jan 8, 2021
From: RAYTHEON COMPANY
To: FORCEPOINT LLC
Reel/Frame 055479/0676 →
PATENT SECURITY AGREEMENT SUPPLEMENT Recorded Mar 15, 2019
From: FORCEPOINT LLC
To: RAYTHEON COMPANY
Reel/Frame 048613/0636 →