Skip to main content

NetskopeIndicatorSync

This Script is part of the Netskope - Direct to Zero Trust Pack.#

Supported versions

Available on Cortex XSOAR (versions 6.10.0 and later) and Cortex XSIAM.

Pulls bounded Domain, URL, IP, and CIDR indicators from Cortex XSOAR's Threat Intel Management and formats CIDR values with the "CIDR:" prefix that Netskope's destination profile Definition field expects. It skips values already present in the target profile. When profile_id is given, it appends the new values in batches of at most chunk_size and deploys only when deploy is explicitly enabled. Without profile_id, it only prepares the new-value list for a separate create-profile step.

Script Data#


NameDescription
Script Typepython3
Cortex XSOAR Version6.10.0

Inputs#


Argument NameDescription
tagsThe optional comma-separated indicator tags to further restrict the search (e.g. "netskope-block"). If omitted, all indicators of the given indicator_types are considered.
skip_tagsThe optional comma-separated indicator tags to exclude - any indicator carrying one of these tags is skipped even if it matches tags/indicator_types.
indicator_queryAn additional Cortex XSOAR indicator query used to bound the sync. The default selects active indicators with a Bad reputation.
indicator_typesThe comma-separated indicator types to pull from Cortex XSOAR's Threat Intel. Must be one or more of Domain, URL, IP, CIDR.
profile_idThe ID of an existing Netskope Destination Profile to append the new values to (and deploy). If omitted, no append/deploy happens - the script only searches, formats, and returns the new values (for a separate create-profile step to consume).
existing_valuesThe comma-separated list of values already in the target destination profile (from netskopev2-list-destination-profiles) - used to skip values that are already blocked. Ignored if profile_id is omitted.
max_indicatorsThe maximum number of indicators to pull from Cortex XSOAR per run.
chunk_sizeThe maximum number of values per append call, matching netskopev2-update-destination-profile-values' 1-10-per-call limit.
deployWhether the deploy option is enabled. If profile_id is set and any new values were appended, deploy the profile afterward so the change takes effect immediately.
change_noteThe optional change note recorded on the deploy call.

Outputs#


PathDescriptionType
Netskope.Sync.ProfileIdThe destination profile ID that was updated (null if this was a create-prep run).String
Netskope.Sync.QueryThe indicator search query that was run.String
Netskope.Sync.TotalFoundThe total indicators returned by the query (before dedup).Number
Netskope.Sync.SkippedExistingThe number of values skipped because they were already present in the profile or duplicated within this run.Number
Netskope.Sync.SkippedNoValueThe number of indicators skipped because they did not contain a value.Number
Netskope.Sync.NewCountThe number of new values found.Number
Netskope.Sync.AddedCountThe number of new values actually appended to profile_id (0 if profile_id was omitted).Number
Netskope.Sync.BatchesThe number of append batches used.Number
Netskope.Sync.DeployedThe value indicating whether the profile was deployed after appending.Boolean
Netskope.Sync.AllNewValuesThe flat list of all new, formatted values - for creating a brand-new profile in one call when profile_id was omitted.List