- Incident Responder i56 Release Notes
- What's New
- Known Issues
- Issues Fixed in Incident Responder i56.5 (General Availability)
- Issues Fixed in Incident Responder i56.6
- Issues Fixed in Incident Responder i56.7
- Issues Fixed in Incident Responder i56.8
- Issues Fixed in Incident Responder i56.9
- Issues Fixed in Incident Responder i56.10
- Issues Fixed in Incident Responder i56.11
- Issues Fixed in Incident Responder i56.12
- Issues Fixed in Incident Responder i56.13
- Issues Fixed in Incident Responder i56.14
- Get Started with Incident Responder
- Configure Incident Responder Settings
- Core Settings
- Analytics Settings
- Configure Services
- Prerequisites for Configuring Incident Responder Microsoft Services with OAuth2.0 Authentication
- Configure the Amazon Elastic Compute Cloud (EC2) Service
- Configure the Anomali ThreatStream API Service
- Configure the Atlassian Jira Service
- Configure the BMC Remedy Service
- Configure the Check Point Firewall Service
- Configure the Cisco AMP for Endpoints Service
- Configure the Cisco Services Engine (ISE) Service
- Configure the Cisco Threat Grid Service
- Configure the Cisco Umbrella Enforcement Service
- Configure the Cisco Umbrella Investigate Service
- Configure the CrowdStrike Falcon Host API Service Service
- Configure the CyberArk Service
- Configure the Cylance Protect Service
- Configure the Exabeam Advanced Analytics Service
- Configure the Exabeam DL Service
- Configure the FireEye HX Service
- Configure the Fortinet Service
- Configure the Google Gmail Service
- Configure the IntSights Cyber Intelligence Ltd. Service
- Configure the IRNotificationSMTPService Service
- Configure the Microsoft Active Directory (AD) (Latest) Service
- Configure the Microsoft Exchange Service
- Configure the Microsoft Outlook Office 365 Service
- Configure the Microsoft Windows Defender ATP Service
- Configure the Microsoft Windows Management Instrumentation Service
- Configure the Netskope Service
- Configure the Okta Service
- Configure the Palo Alto Networks Firewall Service
- Configure the Palo Alto Networks Wildfire Service
- Configure the Rapid7 insightVM Service
- Configure the SentinelOne Service
- Configure the SentinelOneV2 Service
- Configure the Service Now Service
- Configure the Slack Service
- Configure the SlashNext Service
- Configure the Splunk Service
- Configure the ThreatConnect API Service
- Configure the Urlscan.io API Service
- Configure the VirusTotal Service
- Configure the Zscaler Service
- Test a Service
- Edit a Service
- Disable a Service
- Upload a Custom Service
- Delete a Custom Service
- Create an Email Template for the Notify by Email Action
- Respond to Security Incidents
Configure the Cisco Threat Grid Service
Configure Cisco SecureX malware analytics, formerly known as Threat Grid, as a service to detonate files using actions.
Note the IP address, host name, or URL you use to access the Cisco Secure Malware Analytics API (see the API Access or the Searching for a Sample Submission by API sections.)
Note your Cisco Secure Malware Analytics API key.
Note if your privacy setting for samples you submit to Cisco Secure Malware Analytics is Public or Private.
Note the default virtual machine environment your organization uses for UI and API samples.
If you use a proxy, ensure that you whitelist the IP address or URL you use to access the Cisco Secure Malware Analytics API.
In the navigation bar, click the menu , select Settings, then select Core.
Under SERVICE INTEGRATIONS, select Services.
Select a service:
To configure a specific service, hover over a service, then click CONFIGURE. Use the search by vendor or filter by action to find a service.
To manually provide the relevant information for a service, click Configure a new service.
To view all actions for a service, hover over a service, then click the information icon .
Enter information about the service:
Service Name – Enter a unique name for the service. By default, the service name is ThreatGrid.
(Optional) Description – Describe the service.
(Optional) Owner – Enter the email address of the person or group responsible for the service.
Host – Enter the IP, host name, or URL you use to access the Cisco Secure Malware Analytics API you previously noted; for example, https://panacea.threatgrid.com/api/v2/
API Key – Enter your Cisco Secure Malware Analytics API key you previously noted.
Private Submissions – Select whether your Cisco Secure Malware Analytics API privacy setting makes samples private or public: if your privacy setting is Private, select True; if your privacy setting is Public, select False.
Sandbox VM – Enter the default virtual machine environment your organization uses for UI and API samples; for example, win7-x64.
To validate the source, select TEST CONNECTIVITY.
Select CREATE SERVICE.