Macro-script execution control
AssigneeCylance Inc.
InventorDerek A. Soeder
Life of this patent
Estimating the term…
Abstract
An agent inserts one or more hooks into a sub-execution runtime environment that is configured to include a script and/or targeted to include the script. The agent including the one or more hooks monitors a behavior of the sub-execution runtime environment and/or the script. The agent subsequently obtains context information regarding the sub-execution runtime environment and/or the script so that it can control the runtime of at least the sub-execution runtime environment. Related systems, methods, and articles of manufacture are also disclosed.
Claims20
A method, implemented by one or more computers, comprising:
- inserting, by an agent, two or more hooks of different types into a sub-execution runtime environment, wherein the sub-execution runtime environment is configured to include a script and/or targeted to include the script, and wherein the sub-execution runtime environment is an execution environment implemented within a context of another execution environment;
- monitoring, by the agent including the two or more hooks, a behavior of the sub- execution runtime environment and/or the script;
- obtaining, by the agent including the two or more hooks, context information regarding the sub-execution runtime environment and/or the script;
- and
- controlling, by the agent, a runtime of at least the sub-execution runtime environment including the script, wherein the controlling is based on the monitored behavior of the sub-execution runtime environment and/or the script and the obtained context information regarding the sub-execution runtime environment and/or the script, and wherein the agent installs at least one of the two or more hooks as events occur including an additional operating system module and/or a script execution environment-related module being loaded into the script execution environment including a memory.
A method, implemented by one or more computers, comprising:
- inserting, by an agent, two or more hooks of different types into a sub-execution runtime environment, wherein the sub-execution runtime environment is configured to include a script and/or targeted to include the script, and wherein the sub-execution runtime environment is an execution environment implemented within a context of another execution environment;
- monitoring, by a first hook of the two or more hooks, a behavior of the sub-execution runtime environment;
- obtaining, by a second hook of the two or more hooks, context information regarding the sub-execution runtime environment;
- and
- controlling, by the agent, a runtime of at least the sub-execution runtime environment including the script, wherein the controlling is based on the monitored behavior of the sub-execution runtime environment and the obtained context information regarding the sub-execution runtime environment, and wherein the agent installs at least one of the two or more hooks as events occur including an additional operating system module and/or a script execution environment-related module being loaded into the script execution environment including a memory.
A method, implemented by one or more computers, comprising:
- inserting, by an agent, two or more hooks of different types into a sub-execution runtime environment, wherein the sub-execution runtime environment is configured to include a script and/or targeted to include the script, and wherein the sub-execution runtime environment is an execution environment implemented within a context of another execution environment;
- monitoring, by a first hook of the two or more hooks, a behavior of the script;
- obtaining, by a second hook of the two or more hooks, context information regarding the script;
- and
- controlling, by the agent, a runtime of at least the sub-execution runtime environment including the script, wherein the controlling is based on the monitored behavior of the script and the obtained context information regarding the script, and wherein the agent installs at least one of the two or more hooks as events occur including an additional operating system module and/or a script execution environment-related module being loaded into the script execution environment including a memory.
Dependencies are inferred from the claim text.