IP Library Granted Patent US 11,720,712
Granted Patent B2
US 11,720,712 · App. 17/736,053 · Granted Aug 8, 2023

Managing registry access on a computer device

Inventors: John Goodridge (Cheshire, GB); Ian James McLean (Cheshire, GB)
Assignee: Avecto Limited
G06F21/6281G06F12/1416G06F12/1466G06F21/604G06F2221/2101G06F2221/2141G06F2221/2149
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,720,712
App. No.
17/736,053
Granted
Aug 8, 2023
Kind
B2
Abstract

A computer device performs operations for managing registry access, including monitoring a user process on the computer device. The computing device can determine a set of registry access rules relevant to the user process. The computing device can perform an evaluation of a registry operation requested by the user process using the set of registry access rules. The computing device can determine an action based on the evaluation. The action can include one of blocking the registry operation in relation to a particular key in a registry of the operating system, and enabling access to a particular key in the registry of the operating system to perform the requested registry operation.

Claims (51)

1. A method, comprising:

monitoring, via a registry filter driver executed on at least one computing device, a user process on the at least one computer device;

determining, via the registry filter driver, a set of registry access rules relevant to the user process by querying a policy service for a policy file associated with the user process based on meta-data in relation to the user process, wherein the policy file comprises the set of registry access rules;

performing, by the registry filter driver, an evaluation of a registry operation requested by the user process based on the set of registry access rules; and

determining an action based on the evaluation, wherein the action comprises at least one of:

blocking the registry operation in relation to a particular key in a registry of an operating system, and

enabling access to a particular key in the registry of the operating system to perform the registry operation requested by the user process.

2. The method of claim 1 , further comprising monitoring for creation of the user process on the computer device and establishing the set of registry access rules relevant to the user process in response to creation of the user process.

3. The method of claim 2 , further comprising registering, by the registry filter driver, a process creation notification with the operating system.

4. The method of claim 1 , wherein the user process relates to a registry editing tool.

5. The method of claim 1 , wherein the user process relates to a remote registry service used to manage the registry from a remote computer device.

6. The method of claim 1 , further comprising:

monitoring a plurality of user processes on the computer device; and

establishing the set of registry access rules uniquely for each of the plurality of user processes, respectively.

7. The method of claim 1 , further comprising messaging a service on the computer device and in response receiving the set of registry access rules relevant to the user process.

8. The method of claim 1 , further comprising gathering meta-information related to the user process comprising at least a process identity or a process name, and determining the set of registry access rules relevant to the user process based on the meta-information.

9. The method of claim 1 , further comprising performing application control to determine whether or not the user process should be allowed to execute on the computing device, and establishing the set of registry access rules relevant to the user process after performing the application control.

10. The method of claim 1 , wherein the set of registry access rules comprises at least one of:

a block type rule which causes access to a particular key to be denied prior to reaching the registry; and

an elevate type rule which enables access in relation to a particular key.

11. The method of claim 1 , wherein each registry access rule in the set has a defined scope relating to any of: a particular key tree, a particular key, or only to particular named values.

12. The method of claim 1 , wherein the registry operation is intended to query or modify a particular key within the registry.

13. The method of claim 1 , further comprising performing custom messaging in relation to the registry operation requested by the user process according to the set of registry access rules relevant to the user process.

14. The method of claim 1 , further comprising:

generating a custom message comprising a challenge-response; and

receiving a validation code to authenticate a user account associated with the user process, wherein performing the evaluation is further based on authenticating the user account.

15. A system, comprising:

a memory;

at least one computing device in communication with the memory; and

a registry driver, wherein the at least one computing device is configured to execute the registry driver to:

monitor a user process on the at least one computer device;

determine a set of registry access rules relevant to the user process;

perform an evaluation of a registry operation requested by the user process based on the set of registry access rules;

generate a custom message comprising a challenge-response;

receive a validation code to authenticate a user account associated with the user process; and

determine an action based on the evaluation and on authenticating the user account, wherein the action comprises at least one of:

blocking the registry operation in relation to a particular key in a registry of an operating system, and

enabling access to a particular key in the registry of the operating system to perform the registry operation requested by the user process.

16. The system of claim 15 , wherein the custom message is presented in a terminal from which the registry operation was invoked.

17. The system of claim 15 , wherein the at least one computing device is further configured to query a policy service for a policy file associated with the user process based on meta-data in relation to the user process, wherein the policy file comprises the set of registry access rules.

18. A non-transitory computer-readable medium embodying a registry driver that, when executed by at least one computing device, causes the at least one computing device to:

monitor a user process on the at least one computer device;

determine a set of registry access rules relevant to the user process by querying a policy service for a policy file associated with the user process based on meta-data in relation to the user process, wherein the policy file comprises the set of registry access rules;

perform an evaluation of a registry operation requested by the user process based on the set of registry access rules; and

determine an action based on the evaluation, wherein the action comprises at least one of:

blocking the registry operation in relation to a particular key in a registry of an operating system, and

enabling access to a particular key in the registry of the operating system to perform the registry operation requested by the user process.

19. The non-transitory computer-readable medium of claim 18 , wherein the registry driver further causes the at least one computing device to determine whether to allow the user process to run prior to monitoring the user process.

20. The non-transitory computer-readable medium of claim 18 , wherein the registry driver further causes the at least one computing device to:

generate a custom message comprising a challenge-response; and

receive a validation code to authenticate a user account associated with the user process, wherein performing the evaluation is further based on authenticating the user account.

Assignments (5)
RELEASE OF FIRST LIEN PATENT SECURITY AGREEMENT Recorded Nov 28, 2023
From: JEFFERIES FINANCE LLC
To: AVECTO LTD
Reel/Frame 065696/0980 →
RELEASE OF SECOND LIEN PATENT SECURITY AGREEMENT Recorded Nov 28, 2023
From: JEFFERIES FINANCE LLC
To: AVECTO LTD
Reel/Frame 065697/0239 →
SECURITY INTEREST Recorded Oct 18, 2022
From: AVECTO LTD
To: JEFFERIES FINANCE LLC, AS THE COLLATERAL AGENT
Reel/Frame 061456/0209 →
SECURITY INTEREST Recorded Oct 18, 2022
From: AVECTO LTD
To: JEFFERIES FINANCE LLC, AS THE COLLATERAL AGENT
Reel/Frame 061456/0980 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 10, 2022
From: GOODRIDGE, JOHN; MCLEAN, IAN JAMES
To: AVECTO LIMITED
Reel/Frame 059883/0816 →