Method and system to remediate a security issue
AssigneeBull SAS
InventorsMadalina Balazs, Amarjit Matharu
Life of this patent
Estimating the term…
Abstract
A method performed by a security engine system to remediate a security issue of a computing resource. A transformation module may determine a security event from a description of the security issue, and a main message broker may send the security event to a decision server to obtain a sequence of recommended remediation actions based on the security event. A remediation server may then execute remediation scripts, each remediation script implementing at least a remediation action from the sequence of recommended remediation actions, each remediation action being applied to the computing resource.
Claims8
A method to remediate a security issue of a computing resource, the method being carried out by a security engine system comprising a transformation module, a main message broker, and a remediation server, the computing resource comprising an anomaly detection service, the security engine system being configured to communicate with the anomaly detection service of the computing resource and a decision server, the method comprising:
- determining, using the transformation module, a security event from a description of the security issue,
- wherein the security issue is detected by the anomaly detection service,
- wherein the description of the security issue is compiled by the anomaly detection service,
- wherein said security event is an abstraction layer to the description of the security issue and the security event, wherein the security event comprises a plurality of fields that provide information on a type of the security issue, and wherein the security event is determined by
- embedding the description of the security issue in the security event in its original form,
- converting the description of the security issue into a format that is processable by the decision server by parsing the security issue to fill in the plurality of fields of the security event,
- wherein said abstraction layer exchanges information between the computing resource and the decision server, wherein the computing resource is public, private, or hybrid,
- such that remediation of said security issue is extended and is not limited to public computing resources;
- sending, to the decision server by the main message broker, the security event to obtain a sequence of recommended remediation actions based on the security event,
- wherein said sequence of recommended remediation actions is determined based on context information associated with the security issue provided to the security event to provide said sequence of recommended remediation actions that fit a needed remediation of the security issue,
- wherein said sequence of recommended remediation actions is generated from a security playbook that comprises use cases or workflows to be executed to investigate the security event and remediate the security issue,
- wherein said security playbook is integrated into a security orchestration automation and response system (SOAR), and
- wherein said sequence of recommended remediation actions comprise at least one or more of
- a disk snapshot to copy an evidence of a threat,
- shutting down a virtual machine;
- receiving, from the decision server by the main message broker, the sequence of recommended remediation actions;
- and,
- executing, using the remediation server, remediation scripts,
- wherein the remediation server comprises a script library that the remediation server queries, and wherein the script library comprises at least one script defining at least one script action,
- wherein the remediation server is triggered when the remediation server receives said sequence of recommended remediation actions;
- applying said sequence of recommended remediation actions as a whole applied to said computing resource to remediate the security issue,
- wherein said remediation scripts from said script library implement all recommended remediation actions of said sequence of recommended remediation actions from said security playbook,
- wherein each remediation script of said remediation scripts implements at least a remediation action from the sequence of recommended remediation actions, such that each remediation script of said remediation scripts comprises said at least one script action from said script library to apply to the computing resource,
- wherein when the remediation scripts are executed following said sequence of recommended remediation actions as a whole to remediate the security issue,
- the security issue is remediated, and
- the security event indicating remediation is sent to the main message broker,
- wherein if no remediation script is able to produce a recommended remediation action to remediate the security issue,
- the security event indicating no remediation is sent to the main message broker;
- wherein the main message broker also receives an investigation result from the decision server based on the security event, the investigation result indicating if the security issue is considered as a true positive or a false positive,
- wherein the remediation scripts are only executed by the remediation server when the investigation result indicates a true positive, and
- if the investigation result indicates a false positive, the sequence of the recommended remediation actions is empty;
- wherein instead of sending one or more of the sequence of recommended remediation actions and the investigation result independently, the decision server enriches the security event as an enriched security event with one or more of the investigation result and the sequence of recommended remediation actions,
- such that the enriched security event is sent back by the decision server, received by the security engine system, and routed by the main message broker to the remediation server.
A security engine system to remediate a security issue of a computing resource, the security engine system being configured to carry out a method to remediate the security issue of the computing resource, said security engine system comprising:
- a computer that executes specific instructions to implement
- a transformation module;
- a main message broker;
- a remediation server;
- a notification server configured to send a notification by electronic messaging;
- and
- a database;
- wherein the computing resource comprises an anomaly detection service,
- wherein the security engine system is configured to communicate with the anomaly detection service of the computing resource and a decision server;
- wherein said transformation module is configured to determine a security event from a description of the security issue,
- wherein the security event comprises metadata, wherein the metadata comprises one or more of security marks, an investigation result or a sequence of recommended remediation actions, wherein the metadata is stored in the database,
- wherein the security issue is detected by the anomaly detection service,
- wherein the description of the security issue is compiled by the anomaly detection service,
- wherein said security event is an abstraction layer to the description of the security issue and the security event, wherein the security event comprises a plurality of fields that provide information on a type of the security issue, and wherein the security event is determined by
- embedding the description of the security issue in the security event in its original form,
- converting the description of the security issue into a format that is processable by the decision server by parsing the security issue to fill in the plurality of fields of the security event,
- wherein said abstraction layer is configured to exchange information between the computing resource and the decision server, wherein the computing resource is public, private, or hybrid,
- such that remediation of said security issue is extended and is not limited to public computing resources;
- wherein the main message broker is configured to send, to the decision server, the security event to obtain a sequence of recommended remediation actions based on the security event,
- wherein said sequence of recommended remediation actions is determined based on context information associated with the security issue provided to the security event to provide said sequence of recommended remediation actions that fit a needed remediation of the security issue,
- wherein said sequence of recommended remediation actions is generated from a security playbook that comprises use cases or workflows to be executed to investigate the security event and remediate the security issue,
- wherein said security playbook is integrated into a security orchestration automation and response system (SOAR), and
- wherein said sequence of recommended remediation actions comprise at least one or more of
- a disk snapshot to copy an evidence of a threat,
- shutting down a virtual machine;
- wherein the main message broker is configured to receive, from the decision server, the sequence of recommended remediation actions;
- and,
- wherein the remediation server is configured to execute remediation scripts,
- wherein the remediation server comprises a script library that the remediation server queries, and wherein the script library comprises at least one script defining at least one script action,
- wherein the remediation server is triggered when the remediation server receives said sequence of recommended remediation actions,
- wherein said sequence of recommended remediation actions as a whole is applied to said computing resource to remediate the security issue,
- wherein said remediation scripts from said script library implement all recommended remediation actions of said sequence of recommended remediation actions from said security playbook,
- wherein each remediation script of said remediation scripts implements at least a remediation action from the sequence of recommended remediation actions, such that each remediation script of said remediation scripts comprises said at least one script action from said script library to apply to the computing resource;
- wherein when the remediation scripts are executed following said sequence of recommended remediation actions as a whole to remediate the security issue,
- the security issue is remediated, and
- the security event indicating remediation is sent to the main message broker,
- wherein if no remediation script is able to produce a recommended remediation action to remediate the security issue,
- the security event indicating no remediation is sent to the main message broker;
- wherein the main message broker also receives the investigation result from the decision server based on the security event, the investigation result indicating if the security issue is considered as a true positive or a false positive,
- wherein the remediation scripts are only executed by the remediation server when the investigation result indicates a true positive, and
- if the investigation result indicates a false positive, the sequence of the recommended remediation actions is empty;
- wherein instead of sending one or more of the sequence of recommended remediation actions and the investigation result independently, the decision server enriches the security event as an enriched security event with one or more of the investigation result and the sequence of recommended remediation actions,
- such that the enriched security event is sent back by the decision server, received by the security engine system, and routed by the main message broker to the remediation server.
A non-transitory computer-readable medium comprising instructions which, when executed by a computer, causes the computer to carry out a method to remediate a security issue of a computing resource, the method being carried out by a security engine system comprising a transformation module, a main message broker, and a remediation server, the computing resource comprising an anomaly detection service, the security engine system being configured to communicate with the anomaly detection service of the computing resource and a decision server, the method comprising:
- determining, using the transformation module, a security event from a description of the security issue,
- wherein the security issue is detected by the anomaly detection service,
- wherein the description of the security issue is compiled by the anomaly detection service,
- wherein said security event is an abstraction layer to the description of the security issue and the security event, wherein the security event comprises a plurality of fields that provide information on a type of the security issue, and wherein the security event is determined by
- embedding the description of the security issue in the security event in its original form,
- converting the description of the security issue into a format that is processable by the decision server by parsing the security issue to fill in the plurality of fields of the security event,
- wherein said abstraction layer exchanges information between the computing resource and the decision server, wherein the computing resource is public, private, or hybrid,
- such that remediation of said security issue is extended and is not limited to public computing resources;
- sending, to the decision server by the main message broker, the security event to obtain a sequence of recommended remediation actions based on the security event,
- wherein said sequence of recommended remediation actions is determined based on context information associated with the security issue provided to the security event to provide said sequence of recommended remediation actions that fit a needed remediation of the security issue,
- wherein said sequence of recommended remediation actions is generated from a security playbook that comprises use cases or workflows to be executed to investigate the security event and remediate the security issue,
- wherein said security playbook is integrated into a security orchestration automation and response system (SOAR), and
- wherein said sequence of recommended remediation actions comprise at least one or more of
- a disk snapshot to copy an evidence of a threat,
- shutting down a virtual machine;
- receiving, from the decision server by the main message broker, the sequence of recommended remediation actions;
- and,
- executing, using the remediation server, remediation scripts,
- wherein the remediation server comprises a script library that the remediation server queries, and wherein the script library comprises at least one script defining at least one script action,
- wherein the remediation server is triggered when the remediation server receives said sequence of recommended remediation actions;
- applying said sequence of recommended remediation actions as a whole applied to said computing resource to remediate the security issue,
- wherein said remediation scripts from said script library implement all recommended remediation actions of said sequence of recommended remediation actions from said security playbook,
- wherein each remediation script of said remediation scripts implements at least a remediation action from the sequence of recommended remediation actions, such that each remediation script of said remediation scripts comprises said at least one script action from said script library to apply to the computing resource,
- wherein when the remediation scripts are executed following said sequence of recommended remediation actions as a whole to remediate the security issue,
- the security issue is remediated, and
- the security event indicating remediation is sent to the main message broker,
- wherein if no remediation script is able to produce a recommended remediation action to remediate the security issue,
- the security event indicating no remediation is sent to the main message broker;
- wherein the main message broker also receives an investigation result from the decision server based on the security event, the investigation result indicating if the security issue is considered as a true positive or a false positive,
- wherein the remediation scripts are only executed by the remediation server when the investigation result indicates a true positive, and
- if the investigation result indicates a false positive, the sequence of the recommended remediation actions is empty;
- wherein instead of sending one or more of the sequence of recommended remediation actions and the investigation result independently, the decision server enriches the security event as an enriched security event with one or more of the investigation result and the sequence of recommended remediation actions,
- such that the enriched security event is sent back by the decision server, received by the security engine system, and routed by the main message broker to the remediation server.
Dependencies are inferred from the claim text.