IP Library Granted Patent US 12,671,997
Granted Patent B2
US 12,671,997 · App. 18/423,838 · Granted Jun 30, 2026

Elevated security execution mode for network-accessible devices

Inventors: Dmitry Samosseiko (Vancouver, CA); Fraser Peter Howard (Oxford, GB); Michael David Wood (Vancouver, CA); Andrew James Thomas (Abingdon, GB); Benjamin James Humphrey (Norfolk, GB); Xiaochuan Zhang (Abingdon, GB); Paul Barrie Ducklin (Oxford, GB); Anand Ajjan (New Westminster, CA)
Assignee: SOPHOS LIMITED
H04W12/37G06F9/44521G06F21/52G06F21/554G06F21/56H04L63/1416H04L63/1441
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,671,997
App. No.
18/423,838
Filed
Jan 26, 2024
Granted
Jun 30, 2026
Kind
B2
Art Unit
2493
USPC
726/24
Abstract

Various aspects related to methods, systems, and computer readable media for detection and blocking of security threats for network-accessible devices. Methods may include monitoring a plurality of processes executing on the user device to identify a pre-execution flag associated with at least one process of the plurality of processes, and, responsive to identifying the pre-execution flag: receiving an indication of a security threat to the user device, the indication of security threat associated with the at least one process and a device threat type, responsive to the receiving the indication of the security threat, elevating security measures associated with the user device for a first time period, and after the elevating, automatically remediating the security threat on the user device within the first time period.

Claims (69)

1 . A computer-implemented method to automatically elevate security measures on a user device, the method comprising:

scanning a plurality of file storage locations on the user device to identify one or more files that include a code segment that is one or more of:

readable and writeable during execution,

marked for simultaneous read, write, and execute access,

has an association with a shared library of an operating system of the user device,

or combinations thereof:

responsive to identifying the one or more files, implementing one or more pre-execution flags in the identified one or more files;

monitoring a plurality of processes executing on the user device to identify a pre-execution flag associated with at least one process of the plurality of processes, wherein the at least one process is associated with a code segment included in the one or more files, and wherein the monitoring the plurality of processes comprises monitoring memory of the user device; and

responsive to identifying the pre-execution flag:

receiving an indication of a security threat to the user device, the indication of the security threat associated with the at least one process and a device threat type;

responsive to the receiving the indication of the security threat, elevating security measures associated with the user device for a first time period; and

after the elevating, automatically remediating the security threat on the user device within the first time period.

2 . The computer-implemented method of claim 1 , wherein the pre-execution flag indicates that the at least one process is associated with a code segment which is vulnerable to a code-injection threat.

3 . The computer-implemented method of claim 1 , further comprising determining that the device threat type associated with the security threat is a code-injection threat to the user device.

4 . The computer-implemented method of claim 3 , wherein the remediating the security threat on the user device comprises identifying injected code, and performing one or more of isolating, deleting, or remediating the injected code.

5 . The computer-implemented method of claim 1 , wherein the shared library is associated with library linking between programs executing on the user device.

6 . The computer-implemented method of claim 1 , wherein the shared library is a dynamic-linked library (DLL) file.

7 . The computer-implemented method of claim 1 , wherein the shared library is associated with memory sharing between programs executing on the operating system.

8 . The computer-implemented method of claim 1 , wherein the receiving the indication of the security threat comprises at least one of:

receiving the indication of the security threat on the user device from security software that executes on the user device; or

receiving the indication of the security threat on the user device from a remote device in operative communication with the user device over a network, the indication of the security threat based upon network activity from the user device detected by the remote device.

9 . The computer-implemented method of claim 1 , wherein the device threat type is automatically monitored by at least one of: security software that executes on the user device, or a remote device in operative communication with the user device over a network.

10 . The computer-implemented method of claim 1 , wherein the device threat type is a computer security threat associated with a plurality of known and unknown security threats to computer networks.

11 . The computer-implemented method of claim 1 , wherein the elevating security measures associated with the user device comprises configuring the user device to prevent at least one of:

network access from the user device during the first time period;

execution of untrusted software on the user device during the first time period;

creation of new user accounts on the user device during the first time period;

creation of a service in a safe mode on the user device; or

reboot of the user device into the safe mode during the first time period.

12 . The computer-implemented method of claim 1 , wherein the automatically remediating the security threat comprises:

configuring security software that executes on the user device to implement a remediation technique on the user device that remediates the security threat.

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

determining, after the elevating, that the device threat type for the user device is remediated; and

responsive to the determining that the device threat type is remediated, updating the device security measures associated with the user device to a normal security level, wherein the normal security level is associated with disabling one or more of the security measures implemented in the first time period.

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

determining, after expiration of the first time period, that the device threat type for the user device has not been remediated; and

responsive to the determining that the device threat type has not been remediated, maintaining the elevated security measures for a second time period.

15 . The computer-implemented method of claim 1 , wherein the receiving the indication of the security threat is based on security software that executes on the user device determining that at least one behavioral rule of a plurality of behavioral rules is satisfied, wherein the plurality of behavioral rules include rules to detect one or more hacking toolsets.

16 . A non-transitory computer-readable medium with instructions stored thereon that, responsive to execution by a processing device, causes the processing device to perform operations comprising:

scanning a plurality of file storage locations on a user device to identify one or more files that include a code segment that is one or more of:

readable and writeable during execution,

marked for simultaneous read, write, and execute access,

has an association with a shared library of an operating system of the user device,

or combinations thereof;

responsive to identifying the one or more files, implementing one or more pre-execution flags in the identified one or more files;

monitoring a plurality of processes executing on the user device to identify a pre-execution flag associated with at least one process, wherein the at least one process is associated with a code segment included in the one or more files, and wherein the monitoring the plurality of processes comprises monitoring memory of the user device; and

responsive to identifying the pre-execution flag:

receiving an indication of a security threat to the user device, the indication of the security threat associated with the at least one process and a device threat type;

responsive to the receiving the indication of the security threat, elevating security measures associated with the user device for a first time period; and

after the elevating, automatically remediating the security threat on the user device within the first time period.

17 . The non-transitory computer-readable medium of claim 16 , wherein the pre-execution flag indicates that:

the at least one process is associated with a code segment which is vulnerable to a code-injection threat.

18 . The non-transitory computer-readable medium of claim 16 , wherein the operations further comprise determining that the device threat type associated with the security threat is a code-injection threat to the user device.

19 . The non-transitory computer-readable medium of claim 18 , wherein the remediating the security threat on the user device comprises identifying injected code, and performing one or more of isolating, deleting, or remediating the injected code.

20 . A threat management computer system to manage active security threats on an enterprise network, comprising:

a memory with instructions stored thereon;

a processing device, coupled to the memory, the processing device configured to access the memory and execute the instructions; and

a network device coupled to the processing device and configured to receive indications of security threats from a plurality of user devices, wherein the instructions cause the processing device or the network device to perform operations including:

scanning a plurality of file storage locations on a user device to identify one or more files that include a code segment that is one or more of:

readable and writeable during execution,

marked for simultaneous read, write, and execute access,

has an association with a shared library of an operating system of the user device,

or combinations thereof;

responsive to identifying the one or more files, implementing one or more pre-execution flags in the identified one or more files;

monitoring a plurality of processes executing on the user device of the plurality of user devices to identify a pre-execution flag associated with at least one process, wherein the at least one process is associated with a code segment included in the one or more files, and wherein the monitoring the plurality of processes comprises monitoring memory of the user device; and

responsive to identifying the pre-execution flag:

receiving an indication of a security threat to the user device, the indication of the security threat associated with the at least one process and a device threat type;

responsive to the receiving the indication of the security threat, elevating security measures associated with the user device for a first time period; and

after the elevating, automatically remediating the security threat on the user device within the first time period.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 26, 2024
From: SAMOSSEIKO, DMITRY; HOWARD, FRASER PETER; WOOD, MICHAEL DAVID; THOMAS, ANDREW JAMES; HUMPHREY, BENJAMIN JAMES; ZHANG, XIAOCHUAN; DUCKLIN, PAUL BARRIE; AJJAN, ANAND
To: SOPHOS LIMITED
Reel/Frame 066265/0153 →
Continuity (2)
Provisional Application 63506503 · Jun 6, 2023
Related Publication 20240411878A1 · Dec 12, 2024
References Cited (64)
US 8806638B1 · Mani · 2014 [cited by applicant]
US 10997284B2 · Bailey · 2021 [cited by applicant]
US 12326936B2 · Zawadowskiy et al. · 2025 [cited by applicant]
US 20090313699A1 · Jang · 2009 [cited by examiner]
US 20120120023A1 · Huang · 2012 [cited by applicant]
US 20120216242A1 · Uner · 2012 [cited by examiner]
US 20140007222A1 · Qureshi · 2014 [cited by examiner]
US 20160042181A1 · Kruglick · 2016 [cited by examiner]
US 20160127367A1 · Jevans · 2016 [cited by examiner]
US 20160212171A1 · Senanayake et al. · 2016 [cited by applicant]
US 20160217029A1 · Yoon · 2016 [cited by examiner]
US 20160218933A1 · Porras et al. · 2016 [cited by applicant]
US 20160219048A1 · Porras et al. · 2016 [cited by applicant]
US 20160219078A1 · Porras et al. · 2016 [cited by applicant]
US 20170061126A1 · Hooks · 2017 [cited by examiner]
US 20170339178A1 · Mahaffey · 2017 [cited by applicant]
US 20180159887A1 · DiGiambattista · 2018 [cited by examiner]
US 20180212998A1 · Ahuja · 2018 [cited by applicant]
US 20190260785A1 · Jenkinson et al. · 2019 [cited by applicant]
US 20190268303A1 · Schiappa · 2019 [cited by applicant]
US 20190273760A1 · Jacobs · 2019 [cited by applicant]
US 20190342311A1 · Muddu et al. · 2019 [cited by applicant]
US 20200065498A1 · Wang et al. · 2020 [cited by applicant]
US 20200067961A1 · Qin et al. · 2020 [cited by applicant]
US 20200210435A1 · Bendel · 2020 [cited by applicant]
US 20200285752A1 · Wyatt · 2020 [cited by applicant]
US 20200327225A1 · Nguyen · 2020 [cited by applicant]
US 20200364345A1 · Hecht · 2020 [cited by examiner]
US 20200404007A1 · Singh · 2020 [cited by applicant]
US 20210014256A1 · Malhotra · 2021 [cited by applicant]
US 20210026969A1 · Hod · 2021 [cited by examiner]
US 20210097186A1 · Mandal · 2021 [cited by examiner]
US 20210120023A1 · Gupta et al. · 2021 [cited by applicant]
US 20210273953A1 · Fellows et al. · 2021 [cited by applicant]
US 20210273958A1 · Mclean · 2021 [cited by applicant]
US 20210273961A1 · Humphrey et al. · 2021 [cited by applicant]
US 20220038486A1 · Baragaba et al. · 2022 [cited by applicant]
US 20220156657A1 · Brannon et al. · 2022 [cited by applicant]
US 20220222338A1 · Gupta · 2022 [cited by examiner]
US 20220329604A1 · Guy et al. · 2022 [cited by applicant]
US 20220360597A1 · Fellows et al. · 2022 [cited by applicant]
US 20230009127A1 · Boyer · 2023 [cited by applicant]
US 20230011004A1 · Fellows et al. · 2023 [cited by applicant]
US 20230090785A1 · Nunn · 2023 [cited by examiner]
US 20230095415A1 · Boyer et al. · 2023 [cited by applicant]
US 20230164567A1 · Fellows et al. · 2023 [cited by applicant]
US 20230239303A1 · Hutelmyer et al. · 2023 [cited by applicant]
US 20230325511A1 · Jaster · 2023 [cited by applicant]
US 20240080323A1 · Balmakhtar et al. · 2024 [cited by applicant]
US 20240089273A1 · Aslaner · 2024 [cited by applicant]
US 20240126873A1 · Philip · 2024 [cited by applicant]
US 20240152618A1 · Cohen · 2024 [cited by examiner]
US 20240275817A1 · Grout · 2024 [cited by applicant]
US 20240291837A1 · Levari · 2024 [cited by applicant]
US 20250030716A1 · Cross et al. · 2025 [cited by applicant]
Arefi, M.N.; Alexander, G.; Rokham, H.; Chen, A.; Faloutsos, M.; Wei, X.; “FAROS: Illuminating In-memory Injection Attacks via Provenance-Based Whole-System Dynamic Information Flow Tracking,” 48th Annual IEEE/IFIP Int'… [cited by examiner]
Liu, T.; Shi, G; Chen, L.; Zhang, F.; Yang, Y.; Zhang, J.; “TMDFI: Tagged Memory Assisted for Fine-Grained Data-Flow Integrity Towards Embedded Systems Against Software Exploitation,” 17th IEEE Int'l Conf On Trust, Secu… [cited by examiner]
“USPTO”, Non-Final office action for U.S. Appl. No. 18/423,801, 22 pages. [cited by applicant]
Kamruzzaman, Abu, “A Comprehensive Review of Endpoint Security: Threats and Defenses”, International Conference on Cyber Warfare and Security (ICCWS), 2022, 1-7 pages. [cited by applicant]
Non-Final Office Action in U.S. Appl. No. 18/243,814, Sep. 10, 2025. [cited by applicant]
Seqrite, Seqrite Endpoint Security 7.6, Feb. 19, 2021, “docs.seqrite.com/docs/seqrite-eps/settings/client-settings/general-settings/”, 2 pages (Year: 2019). [cited by applicant]
Non-Final Office Action in U.S. Appl. No. 18/423,775, Sep. 10, 2025, 21 pages. [cited by applicant]
“Final Office Action in U.S. Appl. No. 18/423,801”, Dec. 17, 2025, 21 pages. [cited by applicant]
1 “Non-Final Office Action in U.S. Appl. No. 18/423,801”, Apr. 2, 2026. [cited by applicant]