- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Enhanced Security Measures in Place: To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.
12-07-2022 11:34 AM
This relates to lifecycle management and removing old unused playbooks/subplaybooks.
We can use the XSOAR Metrics widget to see when a playbook last executed, however this isn't always a good indicator as we have playbooks for rare events which have never triggered but are still required. This isn't such an issue with our parent playbooks as we know which ones are valid, however as the number of subplaybooks has increased we can't easily tell if they are being called by a parent and therefore still required.
If we can map a subplaybook back to all calling parent playbooks we can identify if it's still required.
12-07-2022 04:44 PM
Hi @DHodd1, I don't think there is an easy way to get this information. You could create an automation that checks this information for you. You can also check the contribution section, but we only show content the playbook depends on.
There is an API call to /playbook/search
that returns a playbook list with every task inside.
12-07-2022 04:44 PM
Hi @DHodd1, I don't think there is an easy way to get this information. You could create an automation that checks this information for you. You can also check the contribution section, but we only show content the playbook depends on.
There is an API call to /playbook/search
that returns a playbook list with every task inside.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!