Where this offering fits
The ThreatConnect platform enquiry is retained for customers using that portfolio name. Current product confirmation should use the official Dataminr cyber-defence material and the proposed entitlement. The practical requirement is turning intelligence into accountable investigation and action, not preserving an old product label without checking its present scope.
Architecture and rollout decisions
Inventory feeds, internal context and the analyst workflows to retain or replace. Confirm supported imports, integrations and migration options for the offered product. Pilot a reviewed intelligence item through enrichment and distribution, checking provenance and handling restrictions. Record changes to roles, data location and licence terms before a migration. Existing customers should supply their non-secret product and renewal details for accurate mapping.
An evaluation scenario for this offering
Use a small synthetic intelligence collection with two reports about the same indicator, distinct confidence levels and a handling restriction. Ask an analyst to preserve source context while reviewing the combined information in the currently confirmed ThreatConnect offering. Publish an approved result to one supported test consumer, then issue a correction and verify the intended downstream treatment. Record current product and support ownership alongside the configuration, particularly where procurement documentation uses retained branding. The evidence should explain what changed a real investigation or detection decision, rather than treating aggregation or a large feed count as proof of useful intelligence.
Evidence to request for this scope
- Obtain the current product-to-entitlement mapping.
- Validate retained intelligence context during migration.
- Test an operational consumer and correction workflow.