- 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
Network Prerequisites for Deploying Incident Responder
Before you deploy Incident Responder, open ports and whitelist URLs.
Open Ports
Note
For IMAP and POP3, only open the ports that match the email server protocol you use.
From | To | Port | Protocol |
---|---|---|---|
User Network | Case Manager Node | 22/TCP | SSH |
Log Sources | Case Manager Node | 9875/TCP and UDP | Syslog |
Incident Responder Appliance | Internal Email Server | 143/TCP | IMAP |
Incident Responder Appliance | Internal Email Server | 993/TCP | IMAPS |
Incident Responder Appliance | Internal Email Server | 25/TCP | SMTP |
Incident Responder Appliance | Internal Email Server | 587/TCP | SMTPS |
Incident Responder Appliance | Internal Email Server | 110/TCP | POP3 |
Incident Responder Appliance | Internal Email Server | 995/TCP | Secure POP3 |
Incident Responder Appliance | External Internet | 43/TPC | WHOIS (HTTP) |
Whitelist URLs
You must whitelist URLs to use some services and actions.
Service | URL | Actions |
---|---|---|
MaxMind |
| Geolocate IP |
VirusTotal | virustotal.com | Get URL Reputation Get IP Reputation |
IP-API | ip-api.com | Geolocate IP |
GoogleSafe Browsing |
| Get URL Reputation Get IP Reputation |
Microsoft Trace |
| Microsoft Outlook Message Track |