IP Library › Granted Patent US 12,602,474
Granted Patent B2
US 12,602,474 · App. 18/906,646 · Granted Apr 14, 2026

Use of an application controller to monitor and control software file and application environments

Inventor: Andrew J. Thomas (Oxfordshire, GB)
Assignee: Sophos Limited
G06F21/56G06F21/62H04L63/107H04L63/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 12,602,474
App. No.
18/906,646
Granted
Apr 14, 2026
Kind
B2
Abstract

In embodiments, a framework for an extensible, file-based security system is described for determining an appropriate application, application environment, and/or access or security control measure based at least in part on a file's reputation.

Claims (41)

1 . A method for operating an application controller on an endpoint in an enterprise network, the method comprising:

in response to a selection of a file, determining at least one access and security parameter for the file;

selecting a secure software application from a number of software applications on the endpoint suitable for opening the file based on a security configuration according to the at least one access and security parameter, wherein the secure software application includes a secure application for opening the file when the file has a poor or unknown reputation because the file was received from the Internet, and wherein the secure software application limits access by the file to resources of an environment of the endpoint more than one or more other files with a good reputation;

launching the selected software application to open the file and access the file in accordance with the security configuration;

controlling a use of the file by the secure software application in a test mode to require that the use of the file is in accord with the at least one access and security parameter for the file;

receiving an update to a reputation of the file; and

in response to the update, permitting a user to escalate the use of the file by the secure software application from the test mode to an insecure mode by providing the secure software application with access to additional resources of the endpoint based on the reputation of the file.

2 . The method of claim 1 , wherein permitting the user to escalate the use of the file includes increasing access to files on the endpoint when the reputation is updated to the good reputation.

3 . The method of claim 1 , wherein permitting the user to escalate the use of the file includes increasing access to network resources of the endpoint.

4 . The method of claim 1 , wherein permitting the user to escalate the use of the file includes increasing access to memory resources of the endpoint.

5 . The method of claim 1 , wherein permitting the user to escalate the use of the file includes increasing access to processes executing on the endpoint.

6 . The method of claim 1 , further comprising decreasing access to resources of the endpoint by the secure software application using the file when the reputation of the file is updated to a poor reputation.

7 . A computer program product for operating an application controller on an endpoint in an enterprise network, the computer program product embodied in a non-transitory computer readable medium that, when executing on one or more computers, performs the steps of:

receiving a file at an endpoint from a network;

determining that a reputation of the file is untrusted based on metadata for the file indicating that a source of the file is the network;

selecting a software application to open the file based on the metadata for the file;

opening the file with the software application, wherein the software application uses an application controller to open the file with limited access to one or more resources based on the reputation of the file being untrusted due to the source of the file in the metadata;

managing use of the file by the software application;

receiving a reputation update to the reputation of the file; and

escalating the software application to an insecure configuration by granting the software application access to additional resources based on the reputation update.

8 . The computer program product of claim 7 , wherein the application controller stores the reputation that is associated with the file.

9 . The computer program product of claim 7 , wherein the application controller is configured to adjust the one or more resources available to the selected software application by managing communications related to the selected software application.

10 . The computer program product of claim 9 , wherein the one or more resources include a network.

11 . The computer program product of claim 9 , wherein the one or more resources include a local file system on the endpoint.

12 . The computer program product of claim 9 , wherein the one or more resources include a process executing on the endpoint.

13 . The computer program product of claim 9 , wherein the one or more resources include a memory.

14 . The computer program product of claim 7 , wherein the one or more resources include a registry of the endpoint.

15 . The computer program product of claim 7 , wherein the metadata for determining the reputation includes data relating to a file format.

16 . The computer program product of claim 7 , wherein the source of the file includes data relating to an originating location of the file.

17 . The computer program product of claim 16 , wherein the originating location is an Internet URL.

18 . The computer program product of claim 16 , wherein the originating location is an IP address.

19 . An endpoint comprising:

a memory storing computer executable instructions that, when executed, provide an application controller for managing applications executing on the endpoint; and

one or more processors configured by the computer executable instructions to operate the application controller by performing the steps of:

in response to a selection of a file, determining at least one access and security parameter for the file;

selecting a software application on the endpoint suitable for opening the file based on a security configuration according to the at least one access and security parameter, wherein the software application limits access by the file to resources of the endpoint when the file has an untrusted reputation due to a source of the file more than the software application limits access to resources for one or more other files with a good reputation;

launching the selected software application to open the file and access the file in accordance with the security configuration;

controlling a use of the file by the software application in a test mode to require that the use of the file is in accord with the at least one access and security parameter for the file;

receiving an update to a reputation of the file; and

in response to the update, permitting a user to escalate the use of the file by the software application from the test mode to an insecure mode by providing the software application with access to additional resources of the endpoint based on the reputation of the file.

20 . The endpoint of claim 19 , wherein the reputation of the file is untrusted because the source of the file is the Internet.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 15, 2024
From: THOMAS, ANDREW J.
To: SOPHOS LIMITED
Reel/Frame 068896/0131 →
Continuity (7)
Continuation 18359283 · Jul 26, 2023
Continuation 17592996 · Feb 4, 2022
Continuation 16692599 · Nov 22, 2019
Continuation 15729306 · Oct 10, 2017
Continuation 15194847 · Jun 28, 2016
Continuation 12751087 · Mar 31, 2010
Related Publication 20250181717A1 · Jun 5, 2025
References Cited (79)
US 7137034B2 · Largman et al. · 2006 [cited by applicant]
US 7392541B2 · Largman et al. · 2008 [cited by applicant]
US 7536598B2 · Largman et al. · 2009 [cited by applicant]
US 7571353B2 · Largman et al. · 2009 [cited by applicant]
US 7577871B2 · Largman et al. · 2009 [cited by applicant]
US 7788699B2 · Largman et al. · 2010 [cited by applicant]
US 7849360B2 · Largman et al. · 2010 [cited by applicant]
US 8181244B2 · Boney · 2012 [cited by applicant]
US 8201243B2 · Boney · 2012 [cited by applicant]
US 8214490B1 · Vos et al. · 2012 [cited by applicant]
US 8225406B1 · Nachenberg et al. · 2012 [cited by applicant]
US 8418250B2 · Morris et al. · 2013 [cited by applicant]
US 8719932B2 · Boney · 2014 [cited by applicant]
US 8726389B2 · Morris et al. · 2014 [cited by applicant]
US 8763123B2 · Morris et al. · 2014 [cited by applicant]
US 8775369B2 · Largman et al. · 2014 [cited by applicant]
US 8819225B2 · Wang et al. · 2014 [cited by applicant]
US 8839422B2 · Ghosh et al. · 2014 [cited by applicant]
US 8856505B2 · Schneider · 2014 [cited by applicant]
US 8856782B2 · Ghosh et al. · 2014 [cited by applicant]
US 8935733B2 · Igoe · 2015 [cited by applicant]
US 9081959B2 · Ghosh et al. · 2015 [cited by applicant]
US 9098698B2 · Ghosh et al. · 2015 [cited by applicant]
US 9270697B2 · Ghosh et al. · 2016 [cited by applicant]
US 9390263B2 · Thomas · 2016 [cited by applicant]
US 9413721B2 · Morris et al. · 2016 [cited by applicant]
US 9436822B2 · Ghosh et al. · 2016 [cited by applicant]
US 9519779B2 · Ghosh et al. · 2016 [cited by applicant]
US 9531747B2 · Stavrou et al. · 2016 [cited by applicant]
US 9578045B2 · Jaroch et al. · 2017 [cited by applicant]
US 9602524B2 · Ghosh et al. · 2017 [cited by applicant]
US 9846588B2 · Ghosh et al. · 2017 [cited by applicant]
US 9871812B2 · Ghosh et al. · 2018 [cited by applicant]
US 10043001B2 · Ghosh et al. · 2018 [cited by applicant]
US 10257224B2 · Jaroch et al. · 2019 [cited by applicant]
US 10515211B2 · Thomas · 2019 [cited by applicant]
US 11714902B2 · Thomas · 2023 [cited by applicant]
US 12111927B2 · Thomas · 2024 [cited by examiner]
US 20050071632A1 · Pauker et al. · 2005 [cited by applicant]
US 20060253458A1 · Dixon et al. · 2006 [cited by applicant]
US 20060282887A1 · Trumper et al. · 2006 [cited by applicant]
US 20080005223A1 · Flake et al. · 2008 [cited by applicant]
US 20080109473A1 · Dixon et al. · 2008 [cited by applicant]
US 20090044024A1 · Oberheide et al. · 2009 [cited by applicant]
US 20100005291A1 · Hulten et al. · 2010 [cited by applicant]
US 20100037324A1 · Calum et al. · 2010 [cited by applicant]
US 20100058468A1 · Green et al. · 2010 [cited by applicant]
US 20100077445A1 · Schneider et al. · 2010 [cited by applicant]
US 20110067101A1 · Seshadri et al. · 2011 [cited by applicant]
US 20110145923A1 · Largman et al. · 2011 [cited by applicant]
US 20110145926A1 · Dalcher et al. · 2011 [cited by applicant]
US 20110191851A1 · Largman et al. · 2011 [cited by applicant]
US 20110225655A1 · Niemelä et al. · 2011 [cited by applicant]
US 20110246753A1 · Thomas · 2011 [cited by applicant]
US 20130247129A1 · Heron et al. · 2013 [cited by applicant]
US 20160337382A1 · Thomas · 2016 [cited by applicant]
US 20180032727A1 · Thomas · 2018 [cited by applicant]
US 20200117801A1 · Thomas · 2020 [cited by applicant]
US 20220156373A1 · Thomas · 2022 [cited by applicant]
US 20240143754A1 · Thomas · 2024 [cited by applicant]
WO WO2003067435A2 · 2003 [cited by applicant]
WO WO2013082437 · 2013 [cited by applicant]
USPTO, , “U.S. Appl. No. 15/729,306 Final Office Action mailed Feb. 14, 2019”, NPL-542 , 21 pages. [cited by applicant]
USPTO, , “U.S. Appl. No. 15/729,306 Non-Final Office Action mailed Sep. 10, 2018”, NPL-543 , 19 pages. [cited by applicant]
USPTO, , “U.S. Appl. No. 15/729,306 Notice of Allowance mailed Aug. 30, 2019”, NPL-544 , 9 pages. [cited by applicant]
USPTO, , “U.S. Appl. No. 16/692,599 Final Office Action mailed Jun. 17, 2021”, NPL-816 , 24 pages. [cited by applicant]
USPTO, , “U.S. Appl. No. 16/692,599 Non-Final Office Action mailed Mar. 9, 2021”, NPL-817 , 21 pages. [cited by applicant]
USPTO, , “U.S. Appl. No. 16/692,599 Notice of Allowance mailed Sep. 29, 2021”, NPL-818 , 10 pages. [cited by applicant]
USPTO, , “U.S. Appl. No. 17/592,996 Notice of Allowance mailed Mar. 15, 2023”, , 11 pages. [cited by applicant]
USPTO, , “U.S. Appl. No. 18/359,283 Notice of Allowance mailed Jun. 11, 2024”, , 9 pages. [cited by applicant]
USPTO, , “U.S. Appl. No. 12/751,087, Final Office Action mailed Jan. 11, 2013”, NPL-107 , 9 pages. [cited by applicant]
USPTO, , “U.S. Appl. No. 12/751,087, Final Office Action mailed Oct. 15, 2014”, NPL-105 , 10 pages. [cited by applicant]
USPTO, , “U.S. Appl. No. 12/751,087, Final Office Action mailed Oct. 22, 2015”, NPL-110 , 11 pages. [cited by applicant]
USPTO, , “U.S. Appl. No. 12/751,087, Non-Final Office Action mailed May 7, 2014”, NPL-106 , 10 pages. [cited by applicant]
USPTO, , “U.S. Appl. No. 12/751,087, Non- Final Office Action mailed Jun. 11, 2015”, NPL-111 , 11 pages. [cited by applicant]
USPTO, , “U.S. Appl. No. 12/751,087, Non- Final Office Action mailed Jul. 17, 2012”, NPL-108 , 9 pages. [cited by applicant]
USPTO, , “U.S. Appl. No. 12/751,087, Notice of Allowance mailed Apr. 26, 2016”, NPL-109 , 8 pages. [cited by applicant]
USPTO, , “U.S. Appl. No. 15/194,847, Non- Final Office Action mailed Apr. 5, 2017”, NPL-196 , 16 pages. [cited by applicant]
USPTO, , “U.S. Appl. No. 15/194,847 Notice of Allowance mailed Sep. 15, 2017”, NPL_197 , 8 pages. [cited by applicant]