playbook palo alto xsiam use case documentation#2461
Merged
CharlesLR-sekoia merged 3 commits intomainfrom Nov 4, 2025
Merged
Conversation
|
Pull request was merged, preview was removed. |
CharlesLR-sekoia
changed the title
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR adds documentation for integrating Sekoia.io IOCs with Palo Alto XSIAM. The PR includes:
- A new navigation entry in
mkdocs.ymlfor the XSIAM integration page - Documentation file explaining how to push Sekoia.io IOCs to XSIAM Collection via playbooks
- Supporting PNG images showing the workflow and configuration screens
Reviewed Changes
Copilot reviewed 2 out of 10 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| mkdocs.yml | Adds navigation entry for PaloAlto Cortex XSIAM integration documentation |
| _shared_content/intelligence_center/integrations/paloalto_xsiam.md | Complete integration guide with setup instructions, playbook configuration, and examples |
| docs/assets/intelligence_center/XSIAM/xsiam_playbook_workflow.png | Workflow diagram image (binary file) |
| docs/assets/intelligence_center/XSIAM/xsiam_override_reliability.png | Configuration screenshot image (binary file) |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| - **Configuration**: | ||
| - **Batch Size Limit**: `200` | ||
| - **Feed ID**: Paste the Feed ID from step 1 (e.g. `feed--xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx`). | ||
| - **Modified After**: an RFC-3339 timestamp (e.g. `2025-06-12T23:20:50.52Z`). We recommend to start with a week of history to avoid disruption of SOC Analysts processes. |
There was a problem hiding this comment.
Corrected spelling of 'Analysts' to 'Analyst' in 'SOC Analyst processes'.
Suggested change
| - **Modified After**: an RFC-3339 timestamp (e.g. `2025-06-12T23:20:50.52Z`). We recommend to start with a week of history to avoid disruption of SOC Analysts processes. | |
| - **Modified After**: an RFC-3339 timestamp (e.g. `2025-06-12T23:20:50.52Z`). We recommend to start with a week of history to avoid disruption of SOC Analyst processes. |
| | class_override | `{id}` | Open string, ≤36 characters | | ||
| | comment | `Valid from {valid_from} AND STIX Pattern: {pattern}` | Free text | | ||
| | severity_mapping | this field is *empty* but is applying the mapping explained in section **3.2.2.Severity mapping** | Use any of: LOW, MEDIUM, HIGH, CRITICAL, INFO | | ||
| | reliability_mapping | this field is *empty* but is applying the mapping explained in section **3.2.4.Reliabilit** | Use any of: A, B, C, D, E, F, G | |
There was a problem hiding this comment.
Corrected incomplete word 'Reliabilit' to 'Reliability' in section reference.
Suggested change
| | reliability_mapping | this field is *empty* but is applying the mapping explained in section **3.2.4.Reliabilit** | Use any of: A, B, C, D, E, F, G | | |
| | reliability_mapping | this field is *empty* but is applying the mapping explained in section **3.2.4.Reliability** | Use any of: A, B, C, D, E, F, G | |
|
|
||
| **Examples** | ||
|
|
||
| - Force all severities to LOW (i.e. all Confidence values highier than 0 will be traduced in "LOW"): |
There was a problem hiding this comment.
Corrected spelling of 'highier' to 'higher' and 'traduced' to 'translated'.
Suggested change
| - Force all severities to LOW (i.e. all Confidence values highier than 0 will be traduced in "LOW"): | |
| - Force all severities to LOW (i.e. all Confidence values higher than 0 will be translated into "LOW"): |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.