SaaS Security
SaaS Security by Palo Alto Networks Pack.#
This Integration is part of theSupported versions
Supported Cortex XSOAR versions: 6.0.0 and later.
Use the SaaS Security integration to protect against cloud‑based threats by:
- Scanning and analyzing all your assets.
- Applying Security policy to identify exposures, external collaborators, risky user behavior, and sensitive documents.
- Identifying the potential risks associated with each asset.
#
Configure SaaS Security on Cortex XSOARNavigate to Settings > Integrations > Servers & Services.
Search for SaaS Security.
Click Add instance to create and configure a new integration instance.
Parameter Description Required Server URL The instance configuration URL based on the server location: https://api.aperture.paloaltonetworks.com (US)
https://api.aperture-eu.paloaltonetworks.com (EU)
https://api.aperture-apac.paloaltonetworks.com (APAC)True Client ID The SaaS Security Client ID. See instructions below. True Client Secret The SaaS Security Client Secret. See instructions below. True Fetch incidents If selected, fetches incidents from SaaS Security. False Incidents Fetch Interval Frequency (in hours and minutes) by which Cortex XSOAR fetches incidents from SaaS Security when Fetch Incidents is selected. False Incident type Incident type is set by this field if a classifier does not exist. If a classifier is selected, it takes precedence. False Incident Mirroring Direction Selects which direction you want the incidents mirrored. You can mirror Incoming only (from SaaS Security to Cortex XSOAR), Outgoing only (from Cortex XSOAR to SaaS Security), or both Incoming And Outgoing. False Number of incidents per fetch Minimum is 10. Maximum is 1000. True First fetch timestamp (<number> <time unit>. For example, 12 hours, 7 days) False Fetch only incidents with matching state Fetches only incidents with matching All, Closed, or Open state. If nothing is selected, All states will be used. False Fetch only incidents with matching severity If nothing is selected, All severities will be used. False Fetch only incidents with matching status If nothing is selected, All statuses will be used. False Fetch only incidents with matching Application IDs A comma-separated list of Application IDs. Run the saas-security-get-apps command to return the Application ID, Name, and Type for all applications. False Close Mirrored XSOAR Incident If selected, when the incident closes on SaaS Security, the incident closes in Cortex XSOAR. False Trust any certificate (not secure) By default, SSL verification is enabled. If selected, the connection isn’t secure and all requests return an SSL error because the certificate cannot be verified. False Use system proxy settings Uses the system proxy server to communicate with the integration. If not selected, the integration will not use the system proxy server. False Click Test to validate the URLs, token, and connection.
#
Configure SaaS Security Incident MirroringYou can enable incident mirroring between Cortex XSOAR incidents and SaaS Security notables (available from Cortex XSOAR version 6.0.0).
To set up mirroring.
To configure mirroring:
- Navigate to Settings > Integrations > Servers & Services.
- Search for SaaS Security and select your integration instance.
- Enable Fetches incidents.
- In the Incident Mirroring Direction integration parameter, select which direction you want the incidents to be mirrored:
- Incoming — Any changes in the following SaaS Security incidents fields (state, category, status, assigned_to, resolved_by, asset_sha256) will be reflected in Cortex XSOAR incidents.
- Outgoing — Any changes in the following Cortex XSOAR incidents fields (state, category) will be reflected in SaaS Security incidents.
- Incoming And Outgoing (Recommended) — Changes in Cortex XSOAR incidents and SaaS Security incidents will be reflected in both directions.
- None — Turns off incident mirroring.
- (Recommended) Select the Close Mirrored XSOAR Incident integration parameter to close the Cortex XSOAR incident when the corresponding incident is closed on SaaS Security.Newly fetched incidents will be mirrored in the direction you select. However, this selection does not affect existing incidents.
Important Notes
- For mirroring to work, the Incident Mirroring Direction parameter needs to be set before the incident is fetched.
- To ensure mirroring works as expected, mappers are required for both Incoming and Outgoing to map the expected fields in Cortex XSOAR and SaaS Security.
- The only fields that can be mirrored in from SaaS Security to Cortex XSOAR are:
- state
- category
- status
- assigned_to
- resolved_by
- asset_sha256
- The only fields that can be mirrored out from XSOAR to SaaS Security are:
- state
- category The supported categories for closing incidents are: "misidentified", "no_reason", and "business_justified". Note: Mirroring out works only for closed incidents due to an API limitation.
#
Create the Client ID and Client Secret on SaaS SecurityIn the SaaS Security UI, do the following:
- Navigate to Settings > External Service.
- Click Add API Client.
- Specify a unique name for the API client.
- Authorize the API client for the required scopes. You use these scopes in the POST request to the /oauth/token endpoint. The Required Scopes are:
- Log access — Access log files. You can either provide the client log access API or add a syslog receiver.
- Incident management — Retrieve and change the incident status.
- Quarantine management — Quarantine assets and restore quarantined assets.
- Copy the client ID and client secret.
Tip: Record your API client secret somewhere safe. For security purposes, it’s only shown when you create or reset the API client. If you lose your secret you must reset it, which removes access for any integrations that still use the previous secret. - Add the Client ID and Client Secret to Cortex XSOAR.
Note: For more information see the SaaS Security Administrator's Guide
#
CommandsYou can execute these commands from the Cortex XSOAR 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.
#
saas-security-incidents-getRetrieves incidents from the SaaS Security platform.
#
Base Commandsaas-security-incidents-get
#
InputArgument Name | Description | Required |
---|---|---|
limit | The number of incidents to pull. Maximum is 200, minimum is 10. Default is 50. Default is 50. | Optional |
from | The start time of the query, filtered by the date the incident was updated,\ \ For example, 2021-08-23T09:26:25.872Z . | Optional |
to | The end time of the query, filtered by the date the incident was updated. For example, 2021-08-23T09:26:25.872Z . | Optional |
app_ids | Comma-separated list of application IDs. Run the 'saas-security-get-apps' command to return the Application ID, Name, and Type for all applications. | Optional |
state | The state of the incidents. If empty, retrieves all states. Possible values: "All", "Open", and "Closed". Possible values are: All, Open, Closed. Default is open. | Optional |
severity | The severity of the incidents. In none is selected, all severities will be pulled. Possible values: "1", "2", "3", "4", and "5". Possible values are: 1, 2, 3, 4, 5. | Optional |
status | The status of the incidents. Possible values: "New", "Assigned", "In Progress", "Pending", "No Reason", "Business Justified", "Misidentified", "In The Cloud", and "Dismiss". Possible values are: New, Assigned, In Progress, Pending, No Reason, Business Justified, Misidentified, In The Cloud, Dismiss. | Optional |
next_page | Get the next batch of incidents. No other argument is needed when providing this. | Optional |
#
Context OutputPath | Type | Description |
---|---|---|
SaasSecurity.Incident.incident_id | Number | The incident ID. |
SaasSecurity.Incident.tenant | String | The tenant associated with the incident. |
SaasSecurity.Incident.app_id | String | The application ID. |
SaasSecurity.Incident.app_name | String | The application name. |
SaasSecurity.Incident.app_type | String | The application type. |
SaasSecurity.Incident.cloud_id | String | The cloud ID. |
SaasSecurity.Incident.asset_name | String | The asset name. |
SaasSecurity.Incident.asset_sha256 | String | The SHA256 hash value of the asset. |
SaasSecurity.Incident.asset_id | String | The asset ID. |
SaasSecurity.Incident.asset_page_uri | String | The asset page URI. |
SaasSecurity.Incident.asset_cloud_uri | String | The asset cloud URI. |
SaasSecurity.Incident.exposure_type | Number | The exposure type (Internal/External). |
SaasSecurity.Incident.exposure_level | String | The exposure level. |
SaasSecurity.Incident.policy_id | String | The policy ID. |
SaasSecurity.Incident.policy_name | String | The policy name. |
SaasSecurity.Incident.policy_version | Number | The policy version. |
SaasSecurity.Incident.policy_page_uri | String | The policy page URI. |
SaasSecurity.Incident.severity | String | The severity of the incident. |
SaasSecurity.Incident.status | String | The incident status. |
SaasSecurity.Incident.state | String | The incident state. |
SaasSecurity.Incident.category | String | The incident category. |
SaasSecurity.Incident.resolved_by | String | The name of the user who resolved the incident. |
SaasSecurity.Incident.resolution_date | Date | The date the incident was resolved. |
SaasSecurity.Incident.created_at | Date | The date the incident was created, e.g., `2021-08-23T09:26:25.872Z`. |
SaasSecurity.Incident.updated_at | Date | The Date the incident was last updated. e.g., `2021-08-24T09:26:25.872Z`. |
SaasSecurity.Incident.asset_owner_id | String | The ID of the asset owner. |
SaasSecurity.Incident.asset_owner_name | String | The name of the asset owner. |
SaasSecurity.Incident.asset_owner_email | String | The email address of the asset owner. |
SaasSecurity.NextResultsPage | String | The URI for the next batch of incidents. |
#
Command Example!saas-security-incidents-get limit=11 app_ids=acf49b2389c09f26ad0ccd2b1a603328 from=2021-08-23T20:25:17.495Z state=open
#
Context Example#
Human Readable Output#
Incidents
Incident Id App Id App Name Asset Name Exposure Level Severity Category Created At Updated At 4 acf49b2389c09f26ad0ccd2b1a603328 Box 1 SP0605 copy 6.java internal Low business_justified 2021-08-03T20:25:15.417Z 2021-08-24T07:44:21.608Z 1 acf49b2389c09f26ad0ccd2b1a603328 Box 1 SP0605 copy 2.java internal Low business_justified 2021-08-03T20:25:12.000Z 2021-08-24T08:19:57.429Z 5 acf49b2389c09f26ad0ccd2b1a603328 Box 1 SP0605 copy 7.java internal Low aperture 2021-08-03T20:25:16.842Z 2021-08-24T17:08:51.022Z 8 acf49b2389c09f26ad0ccd2b1a603328 Box 1 ml_file.java internal Low aperture 2021-08-03T20:25:17.043Z 2021-08-24T17:10:37.433Z 3 acf49b2389c09f26ad0ccd2b1a603328 Box 1 SP0605 copy 5.java internal Low misidentified 2021-08-03T20:25:13.770Z 2021-08-25T14:29:42.288Z
#
saas-security-incident-get-by-idGets an incident by its ID.
#
Base Commandsaas-security-incident-get-by-id
#
InputArgument Name | Description | Required |
---|---|---|
id | The incident ID. | Required |
#
Context OutputPath | Type | Description |
---|---|---|
SaasSecurity.Incident.incident_id | Number | The Incident ID. |
SaasSecurity.Incident.tenant | String | The tenant associated with the incident. |
SaasSecurity.Incident.app_id | String | The application ID. |
SaasSecurity.Incident.app_name | String | The application name. |
SaasSecurity.Incident.app_type | String | The application type. |
SaasSecurity.Incident.cloud_id | String | The cloud ID. |
SaasSecurity.Incident.asset_name | String | The asset name. |
SaasSecurity.Incident.asset_sha256 | String | The SHA256 hash value of the asset. |
SaasSecurity.Incident.asset_id | String | The asset ID. |
SaasSecurity.Incident.asset_page_uri | String | The asset page URI. |
SaasSecurity.Incident.asset_cloud_uri | String | The asset cloud URI. |
SaasSecurity.Incident.exposure_type | Number | The exposure type (Internal/External). |
SaasSecurity.Incident.exposure_level | String | The exposure level. |
SaasSecurity.Incident.policy_id | String | The policy ID. |
SaasSecurity.Incident.policy_name | String | The policy name. |
SaasSecurity.Incident.policy_version | Number | The policy version. |
SaasSecurity.Incident.policy_page_uri | String | The policy page URI. |
SaasSecurity.Incident.severity | String | The severity of the incident. |
SaasSecurity.Incident.status | String | The incident status. |
SaasSecurity.Incident.state | String | The incident state. |
SaasSecurity.Incident.category | String | The incident category. |
SaasSecurity.Incident.resolved_by | String | The name of the user who resolved the incident. |
SaasSecurity.Incident.resolution_date | Date | The date the incident was resolved. |
SaasSecurity.Incident.created_at | Date | The date the incident was created, e.g., `2021-08-23T09:26:25.872Z`. |
SaasSecurity.Incident.updated_at | Date | The date the incident was last updated, e.g., `2021-08-24T09:26:25.872Z`. |
SaasSecurity.Incident.asset_owner_id | String | The ID of the asset owner. |
SaasSecurity.Incident.asset_owner_name | String | The name of the asset owner. |
SaasSecurity.Incident.asset_owner_email | String | The email address of the asset owner. |
#
Command Example!saas-security-incident-get-by-id id=4
#
Context Example#
Human Readable Output#
Incident 4 details
Incident Id App Id App Name Asset Name Exposure Level Severity State Category Created At Updated At 4 acf49b2389c09f26ad0ccd2b1a603328 Box 1 SP0605 copy 6.java internal 1.0 closed business_justified 2021-08-03T20:25:15.417Z 2021-08-26T07:04:14.598Z
#
saas-security-incident-state-updateCloses an incident and updates its category.
#
Base Commandsaas-security-incident-state-update
#
InputArgument Name | Description | Required |
---|---|---|
id | The incident ID. | Required |
category | The reason for closing the incident. Possible values: "Misidentified", "No Reason", and "Business Justified". Possible values are: Misidentified, No Reason, Business Justified. Default is Reason for state update.. | Required |
#
Context OutputPath | Type | Description |
---|---|---|
SaasSecurity.IncidentState.incident_id | String | The incident ID. |
SaasSecurity.IncidentState.state | String | The incident state (open/closed). |
SaasSecurity.IncidentState.category | String | The incident category. |
SaasSecurity.IncidentState.resolved_by | String | The name of the user who resolved the incident. |
SaasSecurity.IncidentState.resolution_date | Date | The date when the incident was resolved. |
#
Command Example!saas-security-incident-state-update category="Business Justified" id=4
#
Context Example#
Human Readable Output#
Incident 4 status details
Category Incident Id Resolution Date Resolved By State business_justified 4 2021-08-26T07:04:14.598Z api closed
#
saas-security-get-appsReturns the Application ID, Name, and Type for all applications.
#
Base Commandsaas-security-get-apps
#
InputNo inputs.
#
Context OutputPath | Type | Description |
---|---|---|
SaasSecurity.App.app_name | String | The application name. |
SaasSecurity.App.app_id | String | The application ID. |
SaasSecurity.App.app_type | String | The application type. |
#
Command Example!saas-security-get-apps
#
Context Example#
Human Readable Output#
Apps Info
App Id App Name App Type acf49b2389c09f26ad0ccd2b1a603328 Box 1 box 2642aaa03dc6fc44496bdfffe5e1bc74 Office 365 1 office365
#
saas-security-asset-remediateRemediates an asset.
#
Base Commandsaas-security-asset-remediate
#
InputArgument Name | Description | Required |
---|---|---|
asset_id | The ID of the asset to remediate. | Required |
remediation_type | The remediation action to take. Possible values: "Remove public sharing"(only for Office365, Dropbox, Box, Google Drive apps), "Quarantine", and "Restore". Possible values are: Remove public sharing, Quarantine, Restore. | Required |
remove_inherited_sharing | Used when the remediation type is “Remove public sharing”. When set to true, all the parent folders with a shared URL will be removed. Possible values are: true, false. Default is false. | Optional |
#
Context OutputPath | Type | Description |
---|---|---|
SaasSecurity.Remediation.asset_id | String | The asset ID. |
SaasSecurity.Remediation.remediation_type | String | The remediation type. |
SaasSecurity.Remediation.status | String | The remediation action status. |
#
Command Example!saas-security-asset-remediate asset_id=61099dc46b544e38fa3ce89a remediation_type=Quarantine
#
Context Example#
Human Readable Output#
Remediation details for asset: 61099dc46b544e38fa3ce89a
Asset Id Remediation Type Status 61099dc46b544e38fa3ce89a system_quarantine pending
#
saas-security-remediation-status-getGets the remediation status for a given asset ID.
#
Base Commandsaas-security-remediation-status-get
#
InputArgument Name | Description | Required |
---|---|---|
asset_id | The asset ID. | Required |
remediation_type | The remediation action that was taken. Possible values: "Remove public sharing"(only for Office365, Dropbox, Box, Google Drive apps), "Quarantine", and "Restore". Possible values are: Remove public sharing, Quarantine, Restore. | Required |
#
Context OutputPath | Type | Description |
---|---|---|
SaasSecurity.Remediation.asset_id | String | The asset ID. |
SaasSecurity.Remediation.asset_name | String | The asset name. |
SaasSecurity.Remediation.remediation_type | String | The remediation type. |
SaasSecurity.Remediation.action_taker | String | The source of the remediation action. For example, 'api'. |
SaasSecurity.Remediation.action_date | Date | The date when the remediation action was taken. |
SaasSecurity.Remediation.status | String | The remediation action status. |
#
Command Example!saas-security-remediation-status-get asset_id=61099dc46b544e38fa3ce89a remediation_type=Quarantine
#
Context Example#
Human Readable Output#
Asset 61099dc46b544e38fa3ce89a remediation details
Action Date Action Taker Asset Id Asset Name Remediation Type Status 2021-08-25T21:18:37.148+0000 api 61099dc46b544e38fa3ce89a SP0605 copy.java system_quarantine success