import demistomock as demisto import jinja2 from CommonServerPython import * from CommonServerUserPython import * """ GenerateAsBuilt Uses the XSOAR API to query for custom content, configuration, and statistics, then generates a HTML and Markdown output based on this. """ HTML_TABLE_TEMPLATE = """
| {{ header }} | {% endfor %}|
|---|---|
| {{ row[header] }} | {% endfor %}|
| {{ k }} | {{ v }} |
This Document covers all of the custom configuration and content that has been deployed following
the engagement of Palo Alto professional services.
This document specifically covers the implementation of the provided use case/playbook, and collates
the dependencies and artefacts implemented to complete it.
This document only includes the dependencies used by the playbook, which may not include other configurations
such as:
This document has been auto-generated using the XSOAR Automation !GenerateAsBuilt, with a specific playbook ({{ playbook_name }}) provided.
Corporate Headquarters
Palo Alto Networks
3000 Tannery Way
Santa Clara, CA 95054
Playbook dependencies are subplaybooks consumed by the parent use case.
{% if data.integrations %} {{ data.integrations.as_html(["name","pack"]) }}
Integration dependencies are those that implement commands required by this use case.
The above integrations may not all be configured in this environment, but are referenced by the use case.
Incident types are the types of incidents generated or used by this use-case.
{% endif %} {% if data.automations %} {{ data.automations.as_html(["name","pack"]) }}Automations are scripts used to perform tasks. They may be custom, or OOTB.
{% endif %} {% if data.incidentfields %} {{ data.incidentfields.as_html(["name","pack"]) }}Incident fields are the fields that this use case relies on to populate or consume information.
{% endif %}
This Document covers all of the custom configuration and content that has been deployed following
the engagement of Palo Alto professional services.
This document has been auto-generated using the XSOAR Automation !GenerateAsBuilt.
Corporate Headquarters
Palo Alto Networks
3000 Tannery Way
Santa Clara, CA 95054
The playbook statistics represent how many incidents have been ingested and associated with
a given playbook.
This is a good indicator of how each use case is being consumed.
The system configuration above represents the server configuration of XSOAR, including advanced server config parameters such as HTTP proxy. This configuration is accessible via settings->about->troubleshooting.
{% if installed_packs_table %} {{ installed_packs_table }}The installed packs are all the content packs currently installed on the server. Content packs include playbooks, automations, and in some cases, integrations.
{% endif %} {% if playbooks_table %} {{ playbooks_table }}Custom playbooks are written specifically for this deployment, or adapted from existing OOTB playbooks. The tasks in each playbook represent the overall size and complexity of each developed playbook.
{% endif %} {% if automations_table %} {{ automations_table }}Custom automations are used to add additional logic and support to playbooks and use cases.
{% endif %} {% if reports %} {{ reports }}Custom reports can be scheduled or manually initiated reports that report any statistic available through XSOAR.
{% endif %} {% if dashboards %} {{ dashboards }}
Custom dashboards are a dynamic way to visualize statistics within XSOAR.
XSOAR ships with a number of Out Of the Box dashboards, the above respresent only
those that have been created as part of this PS engagement.
The system configuration changes the behavior of the XSOAR server/application itself, including keys and the published hostname.