Set up IoT Security and XSOAR for SCCM Integration
Table of Contents
Expand all | Collapse all
-
- Integrate IoT Security with AIMS
- Set up AIMS for Integration
- Set up IoT Security and XSOAR for AIMS Integration
- Send Work Orders to AIMS
- Integrate IoT Security with Microsoft SCCM
- Set up Microsoft SCCM for Integration
- Set up IoT Security and XSOAR for SCCM Integration
- Integrate IoT Security with Nuvolo
- Set up Nuvolo for Integration
- Set up IoT Security and XSOAR for Nuvolo Integration
- Send Security Alerts to Nuvolo
- Send Vulnerabilities to Nuvolo
- Integrate IoT Security with ServiceNow
- Set up ServiceNow for Integration
- Set up IoT Security and XSOAR for ServiceNow Integration
- Send Security Alerts to ServiceNow
- Send Vulnerabilities to ServiceNow
-
- Integrate IoT Security with Cortex XDR
- Set up Cortex XDR for Integration
- Set up IoT Security and XSOAR for XDR Integration
- Integrate IoT Security with CrowdStrike
- Set up CrowdStrike for Integration
- Set up IoT Security and XSOAR for CrowdStrike Integration
- Integrate IoT Security with Tanium
- Set up Tanium for Integration
- Set up IoT Security and XSOAR for Tanium Integration
-
- Integrate IoT Security with Aruba Central
- Set up Aruba Central for Integration
- Set up IoT Security and XSOAR for Aruba Central Integration
- Integrate IoT Security with Cisco DNA Center
- Set up Cisco DNA Center to Connect with XSOAR Engines
- Set up IoT Security and XSOAR for DNA Center Integration
- Integrate IoT Security with Cisco Meraki Cloud
- Set up Cisco Meraki Cloud for Integration
- Set up IoT Security and XSOAR for Cisco Meraki Cloud
- Integrate IoT Security with Cisco Prime
- Set up Cisco Prime to Accept Connections from IoT Security
- Set up IoT Security and XSOAR for Cisco Prime Integration
- Integrate IoT Security with Network Switches for SNMP Discovery
- Set up IoT Security and Cortex XSOAR for SNMP Discovery
- Integrate IoT Security with Switches for Network Discovery
- Set up IoT Security and Cortex XSOAR for Network Discovery
-
- Integrate IoT Security with Aruba WLAN Controllers
- Set up Aruba WLAN Controllers for Integration
- Set up IoT Security and XSOAR for Aruba WLAN Controllers
- Integrate IoT Security with Cisco WLAN Controllers
- Set up Cisco WLAN Controllers for Integration
- Set up IoT Security and XSOAR for Cisco WLAN Controllers
-
- Integrate IoT Security with Aruba ClearPass
- Set up Aruba ClearPass for Integration
- Set up IoT Security and XSOAR for ClearPass Integration
- Put a Device in Quarantine Using Aruba ClearPass
- Release a Device from Quarantine Using Aruba ClearPass
- Integrate IoT Security with Cisco ISE
- Set up Cisco ISE to Identify IoT Devices
- Set up Cisco ISE to Identify and Quarantine IoT Devices
- Configure ISE Servers as an HA Pair
- Set up IoT Security and XSOAR for Cisco ISE Integration
- Put a Device in Quarantine Using Cisco ISE
- Release a Device from Quarantine Using Cisco ISE
- Apply Access Control Lists through Cisco ISE
- Integrate IoT Security with Cisco ISE pxGrid
- Set up Integration with Cisco ISE pxGrid
- Put a Device in Quarantine Using Cisco ISE pxGrid
- Release a Device from Quarantine Using Cisco ISE pxGrid
- Integrate IoT Security with Forescout
- Set up Forescout for Integration
- Set up IoT Security and XSOAR for Forescout Integration
- Put a Device in Quarantine Using Forescout
- Release a Device from Quarantine Using Forescout
-
- Integrate IoT Security with Qualys
- Set up QualysGuard Express for Integration
- Set up IoT Security and XSOAR for Qualys Integration
- Perform a Vulnerability Scan Using Qualys
- Get Vulnerability Scan Reports from Qualys
- Integrate IoT Security with Rapid7
- Set up Rapid7 InsightVM for Integration
- Set up IoT Security and XSOAR for Rapid7 Integration
- Perform a Vulnerability Scan Using Rapid7
- Get Vulnerability Scan Reports from Rapid7
- Integrate IoT Security with Tenable
- Set up Tenable for Integration
- Set up IoT Security and XSOAR for Tenable Integration
- Perform a Vulnerability Scan Using Tenable
- Get Vulnerability Scan Reports from Tenable
Set up IoT Security and XSOAR for SCCM Integration
IoT Security
and XSOAR for SCCM IntegrationSet up
IoT Security
and Cortex XSOAR
to integrate with
Microsoft SCCM.To set up
IoT Security
to integrate through
Cortex XSOAR
with Microsoft SCCM, you must add a Cortex XSOAR
engine to
your network.You must also configure a Microsoft integration
instance and job in XSOAR for each site from which you want to gather
device data. To do this, you need the IP address and port number
of your Microsoft SCCM SQL server, the username and password of
the user account that the XSOAR engine will use when forming a secure
connection with the SQL server, and the name of the SQL database.
Cortex XSOAR Engine Installation
Cortex XSOAR
Engine InstallationA
Cortex XSOAR
engine initiates connections
to the SCCM SQL server and to the Cortex cloud and provides the
means through which they communicate with each other. Although it's
possible to install an XSOAR engine on machines running Windows,
macOS, and Linux operating systems, only an engine on a Linux machine
supports IoT Security
integrations. For more information about operating
system and hardware requirements, see the Cortex Administrator’s Guide.We
recommend downloading the XSOAR engine using the shell installer
script and installing it on a Linux machine. This simplifies the
deployment by automatically installing all required dependencies
and also enables remote engine upgrades.
When placing
an XSOAR engine on your network, make sure it can form a connection
to your SCCM SQL server on TCP port 1433 (default port) or whatever
custom port has been configured on the SQL server. The XSOAR engine
uses this port when authenticating with the SCCM SQL server and
exporting device attributes.
In addition, the engine must be able to form HTTPS connections on TCP port 443 to the Cortex
cloud at https://<your-domain>.iot.demisto.live/. You can see the URL of your
XSOAR instance when you log in to the . It’s visible in the address bar of the web page displaying the
XSOAR interface.
IoT Security
portal and click Integrations
Launch
Cortex XSOAR
To create an XSOAR engine, access the ). Click . Choose
Cortex XSOAR
interface (from the IoT Security
portal, click Integrations
Launch
Cortex XSOAR
Settings
Engines
+ Create New Engine
Shell
as the type.For installation instructions, see Install .
For
help troubleshooting
Cortex XSOAR
engines, including installations,
upgrades, connectivity, and permissions, see Troubleshoot and Troubleshoot Integrations Running
on Engines.Configure IoT Security and Cortex XSOAR
IoT Security
and Cortex XSOAR
In
Cortex XSOAR
, create an integration instance
that specifies connection, authentication, and SCCM database settings and
create a job that specifies which XSOAR playbook to use to import
device information and how often and when to run it. Add more instances and
jobs to import device data from multiple SCCM SQL databases.- Log in toIoT Securityand from there access Microsoft SCCM settings inCortex XSOAR.
- Log in toIoT Securityand then clickIntegrations.IoT SecurityusesCortex XSOARto integrate with Microsoft SCCM, and the settings you must configure to integrate with it are in the XSOAR interface.
- To access these settings,Launch.Cortex XSOARTheCortex XSOARinterface opens in a new browser window.
- If necessary, clickand search forSettingsIntegrationsServers & Servicessccmin the Settings section to locate it among other instances.
- Configure the Microsoft SCCM integration instance.
- ClickAdd instanceto open the settings panel.
- Enter the following and leave the other settings at their default values:Name: Use the default name of the instance or enter a new one.SQL Server Host/IP: Enter the domain name or IP address of the SCCM SQL server.SQL Server Port: Enter the default TCP port number 1433 or, if a different port number is set on the SQL server, enter that.SQL Database: Enter the name of the database from which you want XSOAR to retrieve device information.Each integration instance can retrieve device information from a single database. If you want to retrieve device information from other databases, you must create additional integration instances for them.Username: Enter the name of the user account you previously configured in the SCCM SQL server.Password: Enter the password associated with the user account.Run on Single engine: Choose the XSOAR engine that you want to communicate with the SCCM SQL server.
- When finished, clickTest.If the test is successful, a Success message appears. If not, check that the settings were entered correctly and then test the configuration again.
- After the test succeeds, clickSave & exitto save your changes.
- To enable the Microsoft SCCM integration instance, clickEnable.
- Create a job for XSOAR to retrieve information about devices in the SCCM database specified in the integration instance and then forward it toIoT Security.
- Copy the name of the integration instance and open a duplicate browser window.
- Navigate to Jobs in the new window, and then clickNew Jobat the top of the page.
- In the New Job panel that appears, enter the following and leave the other settings at their default values:Time triggered: (select)Recurring: Select this because you want to periodically import device information from SCCM.Every: Enter a number and set the interval value (Minutes, Hours, Days, or Weeks) and select the days and times on which to run the job. This determines how often and when XSOAR retrieves data from SCCM. Consider running the job every day or every other day at a time when network activity is light, such as late at night, to help reduce potential latency. As a general guideline, it takes approximately 20 minutes for XSOAR to import data for 10,000 devices intoIoT Security. You can see the run status of a recurring job on the Jobs page and note how long it takes. When in progress, its status isRunning. When done, its status changes toCompleted.Name: Enter a name for the job.Playbook: ChooseImport Microsoft SCCM devices to PANW IoT cloud.Integration Instance Name: Paste the name of the integration instance that you copied earlier.
- (Optional) Create more integration instances and jobs to import device information from other SCCM databases intoIoT Security.To create more integration instances, repeat the previous steps, entering unique names for each one and different settings as appropriate for your SCCM databases.For each additional integration instance, create a job forCortex XSOARto run, with a similar configuration as the one you initially created. However, as you add more jobs, consider staggering their run times so that the data retrievals are spread out.
- Run jobs.Run the job for each integration instance you create. The first time you run a job, it triggers XSOAR to report the integration instance that the job references toIoT Security, which then displays the instance on the Integrations page. The integration instance can be in one of the following four states as shown in the Status column on the Integrations page:The integration instance can be in one of the following four states, whichIoT Securitydisplays in the Status column on the Integrations page:
- Disabledmeans that either the integration was configured but intentionally disabled or it was never configured and a job that references it is enabled and running.
- Errormeans that the integration was configured and enabled but is not functioning properly, possibly due to a configuration error or network condition.
- Inactivemeans that the integration was configured and enabled but no job has run for at least the past 60 minutes.
- Activemeans that the integration was configured and enabled and is functioning properly.
When you see that the status of an integration instance has changed fromDisabledtoActive, its setup is complete.