Tell us your source SOAR platform and the decision you need to make. An initial discussion can define the right assessment scope.
Service tabs · swipe to explore →
Incident Source Record Manifest
The race log must be accounted for before it can be moved. This manifest identifies the selected incident source records and the metadata needed to plan a separate historical conversion effort.
Which incident records are in scope, and what is missing or excluded?
Discuss this service
What this inspection covers
A source-side count and classification of historical incidents proposed for conversion.
- Agree on source system, time range, record filters, ownership, and retention rules.
- Record source IDs, counts, record types, timestamps, links, and evidence or attachment indicators where available.
- List gaps, exclusions, and records requiring manual review.
A scoped manifest of source incident records proposed for conversion, with counts and exceptions.
This inventory is not a completed extraction, archive, target transfer, or replay. Raw incident content requires separate handling and approval.
Connect this work to the major service
Define the supporting scope alongside a migration or governance engagement before implementation begins.
How to take this further
Attach this deliverable to the selected migration or governance service and agree on the source data, format, review owner, and acceptance criteria in the statement of work.
View XSOAR to TinesView Splunk to TinesAll servicesFor technical teams · API / Delivery Hooks
The selected primary service provides the report API and downloads for this supporting work.
Tell us your source SOAR platform and the decision you need to make. An initial discussion can define the right assessment scope.