Skip to main content

iZOOlogic

This Integration is part of the iZOOlogic Pack.#

Supported versions

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

Fetches and manages incidents from iZOOlogic, enabling automated ingestion, incident creation, and advanced filtering for brand protection and threat management.

Configure iZOOlogic in Cortex#

ParameterDescriptionRequired
Server URLThe iZOOlogic API server URL.True
API KeyThe API key provided by iZOOlogic for authentication.True
Secret KeyThe secret key corresponding to the API key.True
Trust any certificate (not secure)Whether to trust any certificate (not secure).False
Use system proxy settingsWhether to use the system proxy settings.False
Fetch incidentsWhether to fetch incidents from iZOOlogic.False
Fetch incident typesA comma-separated list of incident types to fetch from iZOOlogic.True
Maximum incidents per fetch per typeThe maximum number of incidents to fetch per type per fetch cycle.True

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.

izoologic-get-events#


Gets events from iZOOlogic. Use this command for development and debugging only, as it may produce duplicate events, exceed API rate limits, or disrupt the fetch mechanism.

Base Command#

izoologic-get-events

Input#

Argument NameDescriptionRequired
limitThe maximum number of events to return per type. Default is 50.Optional
start_timeThe time to filter events detected at or after. Supports ISO 8601 format or relative time expressions (e.g., "3 days ago", "2024-01-01T00:00:00Z").Optional
end_timeThe time to filter events detected at or before. Supports ISO 8601 format or relative time expressions (e.g., "now", "2024-01-01T00:00:00Z").Optional
event_typeThe event types to filter by, as a comma-separated list. If not specified, the command uses the types configured in the integration parameters. Possible values are: brand abuse, phishing, malware, pharming, smishing, vishing, mobile apps, social media, other, email.Optional
should_push_eventsThe flag that indicates whether to push events to Cortex XSIAM. Pushing events is supported on Cortex XSIAM only. When set to false, or on non-Cortex XSIAM platforms, events are displayed without being pushed. Possible values are: true, false. Default is false.Optional

Context Output#

PathTypeDescription
iZOOlogic.Incident.incidentIDStringThe unique identifier of the incident.
iZOOlogic.Incident.incidentTypeStringThe type and subtype of the incident.
iZOOlogic.Incident.subIncidentTypeStringThe subtype of the incident.
iZOOlogic.Incident.detectionDateStringThe detection date of the incident as a Unix timestamp.
iZOOlogic.Incident.urlStringThe URL associated with the incident.
iZOOlogic.Incident.statusStringThe current status of the incident.
iZOOlogic.Incident.statusCodeNumberThe numeric status code of the incident.
iZOOlogic.Incident.brandStringThe brand associated with the incident.
iZOOlogic.Incident.threatTypeStringThe threat level of the incident.
iZOOlogic.Incident.createdOnStringThe creation date of the incident as a Unix timestamp.
iZOOlogic.Incident.closedOnStringThe closing date of the incident as a Unix timestamp.
iZOOlogic.Incident.detectedByStringThe entity that detected the incident.

Command example#

!izoologic-get-events limit=3

Human Readable Output#

iZOOlogic Events#

Incident IDIncident TypeSub Incident TypeBrandUrlStatusStatus CodeThreat TypeDetection DateCreated OnClosed OnDetected By
uVJxla1s1Brand Abuse - Fake WebsiteFake WebsiteTVS Motorhttps://tvsmotor.com.mtWaiting17Substantial Threat17609418011769509374Reported By iZOOLogic
1JrJzZBipPhishingTVS Credithttps://tvs-credit.dev.veefin.inClosed16High Threat176979226017697922601770180062Reported By iZOOLogic
KIks8sE3USocial Media - FacebookFacebookTVS Kinghttps://www.facebook.com/ads/library/?id=917334661007536Waiting17Substantial Threat17696260141769626014Reported By iZOOLogic

izoologic-incident-create#


Creates a new security incident in iZOOlogic.

Base Command#

izoologic-incident-create

Input#

Argument NameDescriptionRequired
incident_urlThe URL, email, or target of the security incident (max 1000 characters).Required
incident_typeThe type of incident. Possible values are: brand abuse, phishing, malware, pharming, smishing, vishing, mobile apps, social media, other, email, executive.Required
brand_codeThe brand identifier associated with the incident.Required
threat_typeThe threat level. Possible values are: low threat, moderate threat, substantial threat, high threat, critical threat, redirect to whitelist. Default is moderate threat.Optional
case_typeThe preferred case type for processing. All new incidents are initially created as "Reported Incident" and may be reclassified during review. Possible values are: incident, brand abuse monitoring, domain monitoring, social media monitoring, mobile app monitoring, executive monitoring. Default is incident.Optional
commentThe comments about the incident (max 2500 characters).Optional
executive_nameThe executive name. Required for executive-related incidents (max 2500 characters).Optional
client_codeThe client identifier for validation and access control.Optional

Context Output#

PathTypeDescription
iZOOlogic.Incident.reportedIncidentIdStringThe unique identifier for the created incident case.
iZOOlogic.Incident.statusCodeNumberThe numeric status code (1 = under review).
iZOOlogic.Incident.statusDescriptionStringThe human-readable status description.
iZOOlogic.Incident.caseTypeNumberThe case type code (9 = reported incident).
iZOOlogic.Incident.caseTypeDescriptionStringThe human-readable case type description.

Command example#

!izoologic-incident-create incident_url="https://test-malicious-site.example.com" incident_type="phishing" brand_code="QnjggfvwlW"

Human Readable Output#

iZOOlogic - New Incident Created#

Reported Incident IdStatus CodeStatus DescriptionCase TypeCase Type Description
ycB2E7gPQ1Under Review9Reported Incident

izoologic-incident-fetch#


Fetches incidents from iZOOlogic based on specified filters including date range, brand, incident type, and other criteria.

Base Command#

izoologic-incident-fetch

Input#

Argument NameDescriptionRequired
from_dateThe start date for filtering incidents. Supports ISO 8601 format or relative time expressions (e.g., "1 day ago", "2024-01-01T00:00:00Z"). Maximum date range is 31 days. Default is 1 day ago.Optional
to_dateThe end date for filtering incidents. Supports ISO 8601 format or relative time expressions (e.g., "now", "2024-01-01T00:00:00Z"). Maximum date range is 31 days. Default is now.Optional
incident_typeThe type of incident to filter by. Possible values are: brand abuse, phishing, malware, pharming, smishing, vishing, mobile apps, social media, other, email, executive.Optional
threat_typeThe threat level to filter by. Possible values are: low threat, moderate threat, substantial threat, high threat, critical threat, redirect to whitelist.Optional
brand_codeThe brand identifier to filter incidents by.Optional
executive_nameThe executive name for filtering executive-related incidents (max 100 characters).Optional
client_ref_idThe client reference ID for specific incident lookup.Optional
client_codeThe client identifier for filtering incidents.Optional

Context Output#

PathTypeDescription
iZOOlogic.Incident.incidentIDStringThe unique identifier of the incident.
iZOOlogic.Incident.incidentTypeStringThe type and subtype of the incident.
iZOOlogic.Incident.subIncidentTypeStringThe subtype of the incident.
iZOOlogic.Incident.detectionDateStringThe detection date of the incident as a Unix timestamp (e.g., 1704067200).
iZOOlogic.Incident.urlStringThe URL associated with the incident.
iZOOlogic.Incident.statusStringThe current status of the incident.
iZOOlogic.Incident.statusCodeNumberThe numeric status code of the incident.
iZOOlogic.Incident.brandStringThe brand associated with the incident.
iZOOlogic.Incident.threatTypeStringThe threat level of the incident.
iZOOlogic.Incident.createdOnStringThe creation date of the incident as a Unix timestamp (e.g., 1704067200).
iZOOlogic.Incident.closedOnStringThe closing date of the incident as a Unix timestamp (e.g., 1704067200).
iZOOlogic.Incident.detectedByStringThe entity that detected the incident.

Command example#

!izoologic-incident-fetch from_date="1 day ago" incident_type="phishing"

Human Readable Output#

iZOOlogic Incidents#

Incident IDIncident TypeBrandUrlStatusStatus CodeThreat TypeDetection DateCreated OnDetected By
abc123PhishingExampleBrandhttps://example.comActive1High Threat17000000001700000200Reported By iZOOLogic