APPSINTG-406:Enhance i471 Integration - Documentation - #7124
APPSINTG-406:Enhance i471 Integration - Documentation#7124shreyashnaik-sumo wants to merge 3 commits into
Conversation
amee-sumo
left a comment
amee-sumo
left a comment
There was a problem hiding this comment.
Left one inline question below, and a general note about the PR description template. Overall the changelog table and version bump look consistent with the convention already used elsewhere in this repo, and CI is green.
| * April 29, 2026 (v1.2) - Upgraded the `python3_generic` Docker image (Python 3.8) to `python3_12_generic` (Python 3.12) to address Python 3.8 end-of-life and improve security and performance. | ||
| | Version | Date | Description | | ||
| |:--------|:-------------------|:--| | ||
| | v1.3 | September 11, 2026 | Migrated the Intel 471 integration to the new Verity API, updating the Stream Malware Intelligence Indicators, Search IOC, and List Alerts actions to use the latest API endpoints. | |
There was a problem hiding this comment.
This says the integration migrated to a new Verity API and the three actions now use the latest API endpoints, but the ## Actions, ## Intel 471 configuration, and ## Configure Intel 471 in Automation Service and Cloud SOAR sections below are unchanged from before this PR, still showing the same base URL (https://api.intel471.com/) and email + API key setup.
If the migration was purely backend (same URL, same auth, only the underlying API calls changed), this is fine as-is. But if the Verity API changed anything user-facing, e.g. the base URL, required fields, or auth method, those sections need updating too, not just this changelog line. Could you confirm which case this is? I wasn't able to check independently since Intel 471's own API docs are gated to partners/customers.
|
The PR description template wasn't filled in (placeholder text is still there, and no "type of change" checkbox is selected). Could you fill in the purpose section and check the appropriate box before this merges? Helps future readers of the PR history understand the change without digging through the diff. |
2 participants
Purpose of this pull request
This pull request...
Select the type of change
Ticket (if applicable)
https://sumologic.atlassian.net/browse/APPSINTG-406