Selecting a custom function from available custom functions to be added into a playbook
Techniques are described for enabling users of an information technology (IT) and security operations application to create highly reusable custom functions for playbooks. The creation and execution of playbooks using an IT and security operations application generally enables users to automate operations related to an IT environment responsive to the identification of various types of incidents or other triggering conditions. Users can create playbooks to automate operations such as, for example, modifying firewall settings, quarantining devices, restarting servers, etc., to improve users' ability to efficiently respond to various types of incidents operational issues that arise from time to time in IT environments.
1. A method, comprising:
storing a user-provided code in a repository, wherein the user-provided code defines a custom function available for use in user-configurable playbooks;
causing, by an information technology (IT) and security operations application, a visual playbook editor interface to be presented, the visual playbook editor interface allowing for user-configuration of a playbook for use in responding to a security or operational issue in an IT environment, wherein the visual playbook editor interface displays identifiers of multiple custom functions from the repository, including the custom function, that are available for inclusion in the playbook;
receiving, by the IT and security operations application via the visual playbook editor interface, an input from a first user indicating a request to insert a custom function block associated with the custom function into the playbook;
detecting the security or operational issue in the IT environment; and
executing the playbook, comprising obtaining and executing the user-provided code from the repository.
2. The method of claim 1 , wherein the user-provided code defining the custom function is generated by a second user, the second user being a different user from the first user indicating the request to insert the custom function block associated with the custom function into the playbook.
3. The method of claim 1 , further comprising:
receiving, by the IT and security operations application via the visual playbook editor interface, another input from the first user indicating one or more input parameters associated with the custom function.
4. The method of claim 3 , wherein the one or more input parameters associated with the custom function include:
one or more data elements associated with one or more upstream function blocks of the playbook;
one or more data elements associated with an incident container;
one or more globally accessible data elements.
5. The method of claim 1 , further comprising:
receiving, by the IT and security operations application via the visual playbook editor interface, another input from the first user indicating one or more output values associated with the custom function, wherein the one or more output values are used as inputs into a downstream function block of the playbook.
6. The method of claim 1 , further comprising:
receiving, by the IT and security operations application via the visual playbook editor interface, another input from the first user modifying the user-provided code defining the custom function; and
storing the modified user-provided code as a separate copy of the custom function in the repository.
7. The method of claim 6 , further comprising:
causing, by the IT and security operations application via the visual playbook editor interface, an option to be presented to store the modified user-provided code as the separate copy of the custom function in the repository.
8. A non-transitory computer-readable storage medium storing instructions which, when executed by one or more processors of a computing device, cause the computing device to implement an information technology (IT) and security operations application to perform operations comprising:
storing a user-provided code in a repository, wherein the user-provided code defines a custom function available for use in user-configurable playbooks;
causing a visual playbook editor interface to be presented, the visual playbook editor interface allowing for user-configuration of a playbook for use in responding to a security or operational issue in an IT environment, wherein the visual playbook editor interface displays identifiers of multiple custom functions from the repository, including the custom function, that are available for inclusion in the playbook;
receiving, via the visual playbook editor interface, an input from a first user indicating a request to insert a custom function block associated with the custom function into the playbook;
detecting the security or operational issue in the IT environment; and
executing the playbook, comprising obtaining and executing the user-provided code from the repository.
9. The non-transitory computer-readable storage medium of claim 8 , wherein the user-provided code defining the custom function is generated by a second user, the second user being a different user from the first user indicating the request to insert the custom function block associated with the custom function into the playbook.
10. The non-transitory computer-readable storage medium of claim 8 , wherein the instructions, when executed by the one or more processors of the computing device, further cause operations comprising:
receiving, by the IT and security operations application via the visual playbook editor interface, another input from the first user indicating one or more input parameters associated with the custom function.
11. The non-transitory computer-readable storage medium of claim 10 , wherein the one or more input parameters associated with the custom function include:
one or more data elements associated with one or more upstream function blocks of the playbook;
one or more data elements associated with an incident container;
one or more globally accessible data elements.
12. The non-transitory computer-readable storage medium of claim 8 , wherein the instructions, when executed by the one or more processors of the computing device, further cause operations comprising:
receiving, by the IT and security operations application via the visual playbook editor interface, another input from the first user indicating one or more output values associated with the custom function, wherein the one or more output values are used as inputs into a downstream function block of the playbook.
13. The non-transitory computer-readable storage medium of claim 8 , wherein the instructions, when executed by the one or more processors of the computing device, further cause operations comprising:
receiving, by the IT and security operations application via the visual playbook editor interface, another input from the first user modifying the user-provided code defining the custom function; and
storing the modified user-provided code as a separate copy of the custom function in the repository.
14. The non-transitory computer-readable storage medium of claim 13 , wherein the instructions, when executed by the one or more processors of the computing device, further cause operations comprising:
causing, by the IT and security operations application via the visual playbook editor interface, an option to be presented to store the modified user-provided code as the separate copy of the custom function in the repository.
15. A computing device, comprising:
a processor;
a non-transitory computer-readable medium having stored thereon instructions that, when executed by the processor, cause the computing device to perform operations including:
storing a user-provided code in a repository, wherein the user-provided code defines a custom function available for use in user-configurable playbooks;
causing, by an information technology (IT) and security operations application, a visual playbook editor interface to be presented, the visual playbook editor interface allowing for user-configuration of a playbook for use in responding to a security or operational issue in an IT environment, wherein the visual playbook editor interface displays identifiers of multiple custom functions from the repository, including the custom function, that are available for inclusion in the playbook;
receiving, by the IT and security operations application via the visual playbook editor interface, an input from a first user_indicating a request to insert a custom function block associated with the custom function into the playbook;
detecting the security or operational issue in the IT environment; and
executing the playbook, comprising obtaining and executing the user-provided code from the repository.
16. The computing device of claim 15 , wherein the user-provided code defining the custom function is generated by a second user, the second user being a different user from the first user indicating the request to insert the custom function block associated with the custom function into the playbook.
17. The computing device of claim 15 , wherein the instructions, when executed by the computing device, further cause the computing device to perform operations including:
receiving, by the IT and security operations application via the visual playbook editor interface, another input from the first user indicating one or more input parameters associated with the custom function.
18. The computing device of claim 15 , wherein the instructions, when executed by the computing device, further cause the computing device to perform operations including:
receiving, by the IT and security operations application via the visual playbook editor interface, another input from the first user indicating one or more output values associated with the custom function, wherein the one or more output values are used as inputs into a downstream function block of the playbook.
19. The computing device of claim 15 , wherein the instructions, when executed by the computing device, further cause the computing device to perform operations including:
receiving, by the IT and security operations application via the visual playbook editor interface, another input from the first user modifying the user-provided code defining the custom function; and
storing the modified user-provided code as a separate copy of the custom function in the repository.
20. The computing device of claim 19 , wherein the instructions, when executed by the processor, further cause the processor to perform operations including:
causing, by the IT and security operations application via the visual playbook editor interface, an option to be presented to store the modified user-provided code as the separate copy of the custom function in the repository.