Integration Hub

Overview#

An enterprise IT team managing a large Argus deployment needs to know, at any moment, which of their 153 third-party integrations are healthy, which are degraded, and which have gone silent. When an integration fails silently, data stops flowing into investigations without any visible error in the platform itself. The Integration Hub prevents that situation by maintaining a live registry of every external service connection, monitoring health status continuously, and surfacing configuration and connectivity issues before they affect operational workflows.

Platform architects and government systems integrators use the Hub as their central reference for integration state: what is connected, how it is configured, how much traffic it is handling, and whether anything needs attention.

Open Standards#

• GraphQL (June 2018 specification): the Integration Hub exposes all connector registry management, health queries, and data source integration operations through a GraphQL API, enabling type-safe, schema-driven interactions for operators and external tooling.
• OAuth 2.0 (RFC 6749): connectors authenticate to external services using OAuth 2.0 client-credentials and bearer-token flows, including Azure AD service-principal authentication for SIEM and cloud data-source integrations.
• HMAC-SHA256 (RFC 2104): outbound webhooks are signed with a per-subscription HMAC-SHA256 secret, allowing receiving systems to verify payload integrity and authenticity before acting on platform events.
• OpenAPI Specification (OAS 3.x): the data-source integration layer auto-discovers remote API schemas by fetching openapi.json or swagger.json endpoints, enabling automatic field mapping without manual configuration.
• STIX 2.1 (OASIS CTI TC): every registered connector must declare its primary output contract; STIX 2.1 is the supported standard for threat-intelligence connectors, with Phase 1 validation performed against the published OASIS schema before Argus type mapping.
• NIEM (National Information Exchange Model): connectors producing law-enforcement or justice-domain data can declare NIEM as their output standard, with the registry enforcing schema conformance during connector validation.
• CAP 1.2 (OASIS Emergency Management): the Common Alerting Protocol is a supported connector output standard, enabling integration with public-warning systems and emergency-management platforms that consume structured CAP alerts.
• AIS (ITU-R M.1371): the Automatic Identification System vessel-tracking standard is a declared connector output type, supporting maritime-domain integrations that feed vessel position and identity data into the platform.

Last Reviewed: 2026-02-05 Last Updated: 2026-04-14

Key Features#

• Central Registry: Single registry for all platform integrations and external service connections across the full catalogue of 153 third-party integrations
• Integration Health Monitoring: Status tracking and alerting for connectivity, response times, and error rates across every connected service
• API Configuration Management: Centralised management of credentials, endpoints, authentication parameters, and integration-specific configuration for connected services
• Living Documentation: Integration state stays synchronised with actual connection status, replacing static documentation that quickly becomes inaccurate
• Integration Lifecycle Management: Full lifecycle tracking from initial configuration through active operation to decommission
• Connection Testing and Validation: Test and validate integrations before enabling in production, with diagnostic tooling to investigate connectivity issues
• Usage Metrics: Activity volume, request rates, error rates, and latency tracking per integration for operational visibility and capacity planning

Use Cases#

• Managing and monitoring all external service integrations from a central dashboard, replacing scattered per-team configuration records
• Configuring and testing new integrations before enabling them in production environments
• Tracking integration health proactively to address connectivity issues before they affect investigation workflows or data pipelines
• Documenting active integrations for operational handover, security audits, and compliance evidence

Integration#

The Integration Hub connects with all external service integrations across the platform, providing centralised management, monitoring, and documentation. Configuration changes flow to connected services through the Hub's API management layer.