XSOAR File Management
This integration uses the XSOAR API to perform basic but essentials actions on files.
Utilities · XSOAR File Management
Details
| ID | XSOAR File Management |
|---|---|
| Provider | Palo Alto Networks |
| Category | Utilities |
| From Version | 6.0.0 |
| Docker Image | demisto/python3:3.12.8.3296088 |
| Supported Modules | Agentix XSIAM |
README
This integration uses the XSOAR API to perform basic but essentials actions on files.
Configure XSOAR File Management in Cortex
| Parameter | Description | Required |
|---|---|---|
| Server URL (e.g. https://example.net) | Make sure XSOAR config ‘External Host Name’ is set and let this field empty otherwise set the external ip of XSOAR. Using https://127.0.0.1 don’t work. | False |
| XSOAR Server API Key | False | |
| Trust any certificate (not secure) | False | |
| Use system proxy settings | False |
Commands
You can execute these commands from the CLI, as part of an automation, or in a playbook.
After you successfully execute a command, a DBot message appears in the War Room with the command details.
file-management-upload-file-to-incident
Copies a file from this incident to the specified incident. Usefull if you want to manipule file in the preprocessing
Base Command
file-management-upload-file-to-incident
Input
| Argument Name | Description | Required |
|---|---|---|
| incidentID | Incident ID to upload the file. If empty, the current incident ID is taken. | Optional |
| fileContent | Non binary content of the file (if set let filePath and filePath empty). | Optional |
| entryID | Entry ID of the file to read (if set let filePath and fileContent empty). | Optional |
| filePath | Path of the file to read ex: incident.attachment.path (if set let entryID and fileContent empty). | Optional |
| fileName | Name of the file. Mandatory if used with filePath and fileContent otherwise the name of the file will not change. | Optional |
| target | Where to upload the file - Available options are: - ‘war room entry’: the file will be uploaded as war room entry. - ‘incident attachment’: the file will be uploaded as incident attachment. - default are ‘war room entry’. Possible values are: war room entry, incident attachment. Default is war room entry. | Optional |
Context Output
There is no context output for this command.
file-management-delete-file
Delete the file from the incident and from the XSOAR server
Base Command
file-management-delete-file
Input
| Argument Name | Description | Required |
|---|---|---|
| entryID | Entry ID of the file. | Required |
Context Output
There is no context output for this command.
file-management-check-file
Check if entry ID exist
Base Command
file-management-check-file
Input
| Argument Name | Description | Required |
|---|---|---|
| entryID | Entry ID of the file. | Required |
Context Output
| Path | Type | Description |
|---|---|---|
| IsFileExists | unknown | Dictionary with EntryID as key and boolean if the file exists as value |
file-management-delete-attachment
Delete the attachment from the incident and from the XSOAR server.
Base Command
file-management-delete-attachment
Input
| Argument Name | Description | Required |
|---|---|---|
| filePath | File path of the file. | Required |
| incidentID | ID of the incident to delete attachment. | Optional |
| fieldName | Name of the field (type attachment) you want to remove the attachment by default it’s the incident attachment (incident.attachment) field. | Optional |
Context Output
There is no context output for this command.
file-management-delete-custom-attachment
Delete the custom field attachment from the incident and from the XSOAR server.
Base Command
file-management-delete-custom-attachment
Input
| Argument Name | Description | Required |
|---|---|---|
| filePath | File path of the file. | Required |
| incidentID | ID of the incident to delete attachment. | Optional |
| fieldName | Name of the custom field (type attachment) you want to remove the attachment. | Required |
Context Output
There is no context output for this command.
file-management-rename-file
Rename a file. Warning: use this only if necessary, it’s HEAVY to run, this will delete and recreate the file with another name !
Base Command
file-management-rename-file
Input
| Argument Name | Description | Required |
|---|---|---|
| entryID | Entry ID of the file to rename. | Required |
| newFileName | New name for the file. | Required |
Context Output
There is no context output for this command.
file-management-download-file
Download files from server.
Base Command
file-management-download-file
Input
| Argument Name | Description | Required |
|---|---|---|
| fileURI | File URI ex:’/markdown/image/123_60cad1a9-6f90-42c5-8b1b-514d66d74fc0.jpg’. | Required |
| fileName | Name of the new downloaded file. | Required |
| incidentID | Incident ID to upload the file. If empty, the current incident ID is taken. | Optional |
| target | Where to upload the file - Available options are: - ‘war room entry’: the file will be uploaded as war room entry. - ‘incident attachment’: the file will be uploaded as incident attachment. - default are ‘war room entry’. Possible values are: war room entry, incident attachment. Default is war room entry. | Optional |
Context Output
There is no context output for this command.
Command Example
!file-management-download-file file_uri="/markdown/image/12142_60cad1a9-6f90-42c5-8b1b-514d66d74fc0.jpg"
!file-management-download-file file_uri="/markdown/image/12142_60cad1a9-6f90-42c5-8b1b-514d66d74fc0.jpg" fileName="my_image.jpg"
!file-management-download-file file_uri="/markdown/image/12142_60cad1a9-6f90-42c5-8b1b-514d66d74fc0.jpg" fileName="my_image.jpg" incidentID="1234"
Human Readable Output
File my_image.jpg uploaded successfully to incident 1234. Entry ID is 1@1234
file-management-get-file-hash
Get file hash from URI.
Base Command
file-management-get-file-hash
Input
| Argument Name | Description | Required |
|---|---|---|
| fileURI | File URI ex:’/markdown/image/123_60cad1a9-6f90-42c5-8b1b-514d66d74fc0.jpg’. | Required |
Context Output
| Path | Type | Description |
|---|---|---|
| File_Hash.Extension | String | Extension of the file. |
| File_Hash.MD5 | String | MD5 of the file. |
| File_Hash.Name | String | Name of the file. |
| File_Hash.SHA1 | String | SHA1 of the file. |
| File_Hash.SHA256 | String | SHA256 of the file. |
| File_Hash.SHA512 | String | SHA512 of the file. |
| File_Hash.Size | String | Size of the file. |
Command Example
!file-management-get-file-hash fileURI="/markdown/image/12142_60cad1a9-6f90-42c5-8b1b-514d66d74fc0.jpg"
Context Example
{
"File_Hash": {
"Extension": "jpg",
"MD5": "e2f28a722de24003257ded589ac10eee",
"Name": "12142_60cad1a9-6f90-42c5-8b1b-514d66d74fc0.jpg",
"SHA1": "0e5e761a2e6794a4d1c445667d4944db34f78d22",
"SHA256": "877383f34532683580b53d2f5a36e68155de58175524a99d4c25d0da96202e5c",
"SHA512": "5ba5455f0ff3e545f8212b4811d22c66451e1a96a0d886b4550bb287c310f52b4ac37559e90546ef2eae69c1a7942223fb0d2660b9fe273562a96376bc0fdd03",
"Size": "1569787"
}
}
Human Readable Output
Hash save under the key ‘File_Hash’.
Configuration parameters
url— Server URL (e.g. https://example.net)creds_apikey_id—creds_apikey—insecure— Trust any certificate (not secure)proxy— Use system proxy settings
Commands (8)
-
file-management-check-fileCheck if entry ID exist.
-
file-management-delete-attachmentDelete the attachment from the incident and from the XSOAR server.
-
file-management-delete-custom-attachmentDelete the custom field attachment from the incident and from the XSOAR server.
-
file-management-delete-fileDelete the file from the incident and from the XSOAR server.
-
file-management-download-fileDownload files from server.
-
file-management-get-file-hashGet file hash from URI.
-
file-management-rename-fileRename a file. Warning: use this only if necessary, it's HEAVY to run, this will delete and recreate the file with another name.
-
file-management-upload-file-to-incidentCopies a file from this incident to the specified incident. Usefull if you want to manipule file in the preprocessing.
category: Utilities provider: Palo Alto Networks sectionorder: - Connect commonfields: id: XSOAR File Management version: -1 configuration: - additionalinfo: Make sure XSOAR config 'External Host Name' is set and let this field empty otherwise set the external ip of XSOAR. Using https://127.0.0.1 don't work. display: Server URL (e.g. https://example.net) name: url type: 0 section: Connect required: false - display: '' displaypassword: XSOAR Server API Key ID hiddenusername: true name: creds_apikey_id section: Connect required: false type: 9 - display: "" displaypassword: XSOAR Server API Key hiddenusername: true name: creds_apikey type: 9 section: Connect required: false - display: Trust any certificate (not secure) name: insecure type: 8 section: Connect required: false - display: Use system proxy settings name: proxy type: 8 section: Connect required: false description: This integration uses the XSOAR API to perform basic but essentials actions on files. display: XSOAR File Management name: XSOAR File Management script: commands: - name: file-management-upload-file-to-incident arguments: - name: incidentID description: Incident ID to upload the file. If empty, the current incident ID is taken. - name: fileContentB64 description: Content of the file encoded in Base64 (if set let filePath, entrID and fileContent empty). - name: fileContent description: Non binary content of the file (if set let filePath, entryID and fileContentB64 empty). - name: entryID description: Entry ID of the file to read (if set let filePath, fileContent and fileContentB64 empty). - name: filePath description: 'Path of the file to read ex: incident.attachment.path (if set let entryID, fileContent and fileContentB64 empty).' - name: fileName description: Name of the file. Mandatory if used with filePath and fileContent otherwise the name of the file will not change. - name: target auto: PREDEFINED predefined: - war room entry - incident attachment description: 'Where to upload the file - Available options are: - ''war room entry'': the file will be uploaded as war room entry. - ''incident attachment'': the file will be uploaded as incident attachment. - default are ''war room entry''.' defaultValue: war room entry description: Copies a file from this incident to the specified incident. Usefull if you want to manipule file in the preprocessing. - name: file-management-delete-file arguments: - name: entryID required: true description: Entry ID of the file. description: Delete the file from the incident and from the XSOAR server. execution: true - name: file-management-check-file arguments: - name: entryID required: true description: Entry ID of the file. outputs: - contextPath: IsFileExists description: Dictionary with EntryID as key and boolean if the file exists as value. description: Check if entry ID exist. - name: file-management-delete-attachment arguments: - name: filePath required: true description: File path of the file. - name: incidentID description: ID of the incident to delete attachment. - name: fieldName description: Name of the field (type attachment) you want to remove the attachment by default it's the incident attachment (incident.attachment) field. description: Delete the attachment from the incident and from the XSOAR server. execution: true - name: file-management-delete-custom-attachment arguments: - name: filePath required: true description: File path of the file. - name: incidentID description: ID of the incident to delete attachment. - name: fieldName required: true description: Name of the custom field (type attachment) you want to remove the attachment. description: Delete the custom field attachment from the incident and from the XSOAR server. - name: file-management-rename-file arguments: - name: entryID required: true description: Entry ID of the file to rename. - name: newFileName required: true description: New name for the file. description: 'Rename a file. Warning: use this only if necessary, it''s HEAVY to run, this will delete and recreate the file with another name.' - name: file-management-download-file arguments: - name: fileName description: Name of the new downloaded file. - name: fileURI required: true description: 'File URI ex:''/markdown/image/123_60cad1a9-6f90-42c5-8b1b-514d66d74fc0.jpg''.' - name: incidentID description: Incident ID to upload the file. If empty, the current incident ID is taken. - name: target description: 'Where to upload the file - Available options are: - ''war room entry'': the file will be uploaded as war room entry. - ''incident attachment'': the file will be uploaded as incident attachment. - default are ''war room entry''.' description: Download files from server. - name: file-management-get-file-hash arguments: - name: fileURI required: true description: 'File URI ex:''/markdown/image/123_60cad1a9-6f90-42c5-8b1b-514d66d74fc0.jpg''.' outputs: - contextPath: File_Hash.Extension description: Extension of the file. type: string - contextPath: File_Hash.MD5 description: MD5 of the file. type: string - contextPath: File_Hash.SHA1 description: SHA1of the file. type: string - contextPath: File_Hash.SHA256 description: SHA256of the file. type: string - contextPath: File_Hash.SHA512 description: SHA512of the file. type: string - contextPath: File_Hash.Name description: Name of the file. type: string - contextPath: File_Hash.Size description: Size of the file. type: string description: Get file hash from URI. dockerimage: demisto/python3:3.12.8.3296088 runonce: false script: '' subtype: python3 type: python fromversion: 6.0.0 tests: - No tests (auto formatted)