EU CISE Maritime Message Integration

Overview#

A national coast guard centre needs the same recognised maritime picture as the navy, the customs service, and the fisheries inspectorate next door, without building a separate bridge to each one. EU CISE (Common Information Sharing Environment) is the shared exchange that makes that possible, and Argus speaks it natively so a member-state authority can connect a CISE node and start receiving cross-border surveillance messages straight away.

The CISE Maritime Message Integration module lets coast guard agencies, naval operations centres, and EU member-state maritime authorities ingest and query CISE surveillance messages exchanged with allied authorities. Structured messages carrying a message type, service type, standard CISE XML payload, priority, and secrecy level are stored per organisation with clearance-filtered reads, audit-logged on arrival, and promoted into the shared operational picture as coalition mission-context entities. The result is a unified common recognised maritime picture that draws on partner authorities' feeds without bespoke integration work against the CISE XML gateway.

Last Reviewed: 2026-05-26 Last Updated: 2026-05-26

Key Features#

• CISE Message Ingestion: Inbound CISE surveillance messages are accepted with their message type, service type, sender, recipient, standard CISE XML payload, priority, and secrecy level, then persisted as structured records scoped to the receiving organisation.

• Standard CISE XML Payloads: Each record carries the original CISE XML message in a dedicated payload field, preserving the source schema intact so nothing is lost in translation and the message remains re-exportable to partner nodes.

• Cross-Border Message Queries: Operators retrieve stored messages by organisation, page through results, and filter by message type, giving a fast read path over surveillance traffic received from allied authorities.

• Message Type Statistics: A grouped count by message type summarises the mix of surveillance traffic an authority is receiving, supporting situational awareness and reporting at a glance.

• Clearance-Filtered Reads: Every message carries a secrecy level, and reads are filtered against the requesting operator's clearance so analysts only ever see traffic at or below their authorisation, supporting multi-classification working from a single store.

• Operational Picture Promotion: On ingest, each message is emitted as a coalition mission-context operational entity through the shared interop bridge, so CISE traffic flows directly into the common recognised maritime picture rather than sitting in an isolated inbox.

• External CISE Node Connectivity: An asynchronous HTTP client connects to external CISE gateway nodes to fetch and submit messages, with configurable base URL, bearer-token authentication, and request timeout per connected node.

• End-to-End Audit Trail: Every ingest is written to an interop audit record capturing the originating user, organisation, standard, record reference, secrecy level, and key message attributes, providing complete data lineage from inbound node to operational entity.

Use Cases#

Coast Guard Operations Centres#

A coast guard watch centre connects Argus to its national CISE node and receives vessel-position, incident, and surveillance messages from neighbouring member-state authorities. Incoming traffic appears on the common recognised maritime picture alongside the centre's own sensor feeds, giving watch-standers cross-border awareness without leaving their console.

Naval Operations Centres#

A naval operations centre ingests CISE messages from allied coast guard and customs authorities and treats them as coalition mission-context entities. Clearance filtering keeps classified traffic visible only to cleared operators, so a single deployment serves analysts working at different classification levels.

EU Member-State Maritime Authorities#

Customs, fisheries, border, and maritime safety authorities exchange surveillance information through their shared CISE environment. Argus consumes that exchange directly, letting each authority enrich its own picture with partners' reports under existing data-sharing arrangements rather than commissioning point-to-point links.

Cross-Border Incident Response#

When a search-and-rescue or pollution incident spans a maritime boundary, the relevant CISE messages from each side land in a single operational view with priority preserved, so responders coordinate against a shared, current picture of who is reporting what.

Integration#

• CISE Node Connector: An asynchronous HTTP client fetches messages from, and submits messages to, an external CISE gateway node using a configurable base URL, optional bearer token, and request timeout, so an authority plugs in its existing node endpoint without custom transport code.

• Operational Entity Bridge: Ingested messages are emitted as coalition mission-context entities through the shared interop bridge, feeding the common recognised maritime picture and reusing the same normalised operational model as every other connected source.

• Clearance Model: Reads are filtered against the requesting operator's clearance using the platform-wide secrecy model, so CISE traffic obeys the same data-sovereignty rules as all other classified content.

• Interop Audit: Each ingest is recorded through the shared interop audit path, giving security and compliance teams one consistent place to trace inbound standards traffic and its lineage.

• GraphQL API: Programmatic access is provided through ciseMessages and ciseStats for reading, and ingestCiseMessage for inbound writes, all requiring authentication and organisation scoping. This lets a customer's own systems push CISE records in and pull the recognised picture out over a single typed endpoint.

Open Standards#

• EU CISE (Common Information Sharing Environment): The EMSA maritime surveillance message-exchange framework for sharing information across EU member-state authorities such as coast guards, navies, and customs; Argus ingests and queries messages exchanged through a CISE node (reference: https://emsa.europa.eu/cise.html).

• CISE XML Message Schema: The standard CISE XML message format is carried intact in each record's payload field, so messages retain their native schema and remain consumable by any CISE-compliant node.

• HTTP / REST: Connectivity to external CISE gateway nodes uses standard HTTP request and response semantics over a REST-style /messages path for both retrieval and submission.

• OAuth 2.0 Bearer Tokens (RFC 6750): Authentication to a connected CISE node uses bearer-token credentials carried in the standard Authorization header.

Security & Compliance#

Every read and write requires an authenticated session and is scoped to the operator's organisation, so authorities never see one another's stored traffic unless it was explicitly exchanged. Secrecy levels on each message drive clearance-filtered reads, keeping classified surveillance information visible only to cleared operators and supporting multi-classification working from a unified store. Every ingest produces an immutable interop audit record capturing the user, organisation, standard, record reference, secrecy level, and message attributes, giving full lineage from the inbound CISE node through to the operational entity placed on the recognised maritime picture.