Threat mitigation system and method

US12413623B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-12413623-B2
Application numberUS-202117333553-A
CountryUS
Kind codeB2
Filing dateMay 28, 2021
Priority dateMay 28, 2020
Publication dateSep 9, 2025
Grant dateSep 9, 2025

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A computer-implemented method, computer program product and computing system for: establishing connectivity with a plurality of security-relevant subsystems within a computing platform; defining a specific task to be executed on one or more of the plurality of security-relevant subsystems, thus defining one or more target security-relevant subsystems; commissioning a container-based job within which the specific task will be executed; and executing the specific task within the container-based job.

First claim

Opening claim text (preview).

What is claimed is: 1. A computer-implemented method, executed on a computing device, comprising: establishing connectivity with a plurality of security-relevant subsystems within a computing platform; defining a common specific task to be executed on each of the plurality of security-relevant subsystems, thus defining a plurality of target security-relevant subsystems, wherein defining the common specific task includes: defining a unified specific task; and denormalizing the unified specific task to define a subsystem-specific task for each of the plurality of target security-relevant subsystems, thus defining a plurality of subsystem-specific tasks, wherein each subsystem specific task includes one or more bespoke commands or operations to be performed on a respective security-relevant subsystems for accomplishing the unified specific task; commissioning a container-based job within which the common specific task will be executed; and executing the common specific task on each of the plurality of security-relevant subsystems within the container-based job. 2. The computer-implemented method of claim 1 wherein commissioning a container-based job within which the specific task will be executed includes: associating the container-based job with a job-specific IP address. 3. The computer-implemented method of claim 2 wherein communication with the one or more target security-relevant subsystems is effectuated via the job-specific IP address. 4. The computer-implemented method of claim 1 further comprising: decommissioning the container-based job. 5. The computer-implemented method of claim 4 wherein decommissioning the container-based job includes one or more of: automatically decommissioning the container-based job upon completion of the execution of the specific task on the one or more target security-relevant subsystems; and manual decommissioning the container-based job prior to completion of the execution of the specific task on the one or more target security-relevant subsystems. 6. The computer-implemented method of claim 4 wherein decommissioning the container-based job includes: releasing a job-specific IP address associated with the container-based job. 7. The computer-implemented method of claim 1 further comprising: providing the one or more subsystem-specific tasks to the one or more target security-relevant subsystems. 8. The computer-implemented method of claim 1 wherein the plurality of security-relevant subsystems includes one or more of: CDN (i.e., Content Delivery Network) systems; DAM (i.e., Database Activity Monitoring) systems; UBA (i.e., User Behavior Analytics) systems; MDM (i.e., Mobile Device Management) systems; IAM (i.e., Identity and Access Management) systems; DNS (i.e., Domain Name Server) systems; Antivirus systems; operating systems; data lakes; data logs; security-relevant software applications; security-relevant hardware systems; and resources external to the computing platform. 9. A computer program product residing on a non-transitory computer readable medium having a plurality of instructions stored thereon which, when executed by a processor, cause the processor to perform operations comprising: establishing connectivity with a plurality of security-relevant subsystems within a computing platform; defining a common specific task to be executed on of each of the plurality of security-relevant subsystems, thus defining a plurality of target security-relevant subsystems, wherein defining the common specific task includes: defining a unified specific task; and denormalizing the unified specific task to define a subsystem-specific task for each of the plurality of target security-relevant subsystems, thus defining a plurality of subsystem-specific tasks, wherein each subsystem specific task includes one or more bespoke commands or operations to be performed on a respective security-relevant subsystems for accomplishing the unified specific task; commissioning a container-based job within which the common specific task will be executed; and executing the common specific task on each of the plurality of security-relevant subsystems within the container-based job. 10. The computer program product of claim 9 wherein commissioning a container-based job within which the specific task will be executed includes: associating the container-based job with a job-specific IP address. 11. The computer program product of claim 10 wherein communication with the one or more target security-relevant subsystems is effectuated via the job-specific IP address. 12. The computer program product of claim 9 further comprising: decommissioning the container-based job. 13. The computer program product of claim 12 wherein decommissioning the container-based job includes one or more of: automatically decommissioning the container-based job upon completion of the execution of the specific task on the one or more target security-relevant subsystems; and manual decommissioning the container-based job prior to completion of the execution of the specific task on the one or more target security-relevant subsystems. 14. The computer program product of claim 12 wherein decommissioning the container-based job includes: releasing a job-specific IP address associated with the container-based job. 15. The computer program product of claim 9 further comprising: providing the one or more subsystem-specific tasks to the one or more target security-relevant subsystems. 16. The computer program product of claim 9 wherein the plurality of security-relevant subsystems includes one or more of: CDN (i.e., Content Delivery Network) systems; DAM (i.e., Database Activity Monitoring) systems; UBA (i.e., User Behavior Analytics) systems; MDM (i.e., Mobile Device Management) systems; IAM (i.e., Identity and Access Management) systems; DNS (i.e., Domain Name Server) systems; Antivirus systems; operating systems; data lakes; data logs; security-relevant software applications; security-relevant hardware systems; and resources external to the computing platform. 17. A computing system including a processor and memory configured to perform operations comprising: establishing connectivity with a plurality of security-relevant subsystems within a computing platform; defining a common specific task to be executed on each of the plurality of security-relevant subsystems, thus defining a plurality of target security-relevant subsystems, wherein defining the common specific task includes: defining a unified specific task; and denormalizing the unified specific task to define a subsystem-specific task for each of the plurality of target security-relevant subsystems, thus defining a plurality of subsystem-specific tasks, wherein each subsystem specific task includes one or more bespoke commands or operations to be performed on a respective security-relevant subsystems for accomplishing the unified specific task; commissioning a container-based job within which the common specific task will be executed; and executing the common specific task on each of the plurality of security-relevant subsystems within the container-based job. 18. The computing system of claim 17 wherein commissioning a container-based job within which the specific task will be executed includes: associating the container-based job with a job-specific IP address. 19. The computing system of claim 18 wherein communication with the one or more target security-relevant subsystems is effectua

Assignees

Inventors

Classifications

  • Network integration; Enabling network access in virtual machine instances · CPC title

  • Isolation or security of virtual machine instances · CPC title

  • Creating, deleting, cloning virtual machine instances · CPC title

  • Hypervisor-specific management and integration aspects · CPC title

  • involving event detection and direct action · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US12413623B2 cover?
A computer-implemented method, computer program product and computing system for: establishing connectivity with a plurality of security-relevant subsystems within a computing platform; defining a specific task to be executed on one or more of the plurality of security-relevant subsystems, thus defining one or more target security-relevant subsystems; commissioning a container-based job within …
Who is the assignee on this patent?
Reliaquest Holdings Llc
What technology area does this patent fall under?
Primary CPC classification H04L63/20. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Sep 09 2025 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 10 related publications on this page (citations in our corpus or others sharing the same primary CPC).