- 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
- Respond to Security Incidents
PrevNext
Issues Fixed in Incident Responder i56.11
ACTN-3831 | Because of a limitation with the ThreatConnect API, the ThreatConnect service could only get an indicator's reputation from one owner; to get an indicator's reputation from multiple owners, you configured multiple instances of the ThreatConnect service. To resolve this issue, the ThreatConnect service now makes an additional API call that returns all owners at once. Now, you only need to configure one ThreatConnect service to get an indicator's reputation from all owners. |