DORA Article 45 Information Sharing

The DORA information-sharing surface prepares operator-controlled outbound cyber-threat and incident information-sharing batches. Stella supplies minimisation, STIX/TAXII-aligned batch construction, DSSE signing, dedicated Notify channel purpose routing, and audit evidence. The operator owns the sharing arrangement, subscriber authorization, transfer basis, and decision to deliver each batch.

This is a surface of the DORA Operational Resilience Pack.

Claim boundary: operator-support.

Source Docs

• DORA Info Sharing Event v1
• DORA Article 45 information-sharing runbook
• Notify architecture
• Operator Compliance Config v1
• EU Signing Payload Registry v1

Runtime Boundary

General Notify channels must not be reused for DORA peer sharing. Use a Notify channel whose purpose is dora-info-sharing so minimisation, signing, and audit evidence stay separated from ordinary notifications.

The Notifier worker has a purpose-specific path for enabled DORA information sharing channels. It bypasses generic webhook/template dispatch, builds the connector request from channel collection/subscriber settings plus frozen source events, verifies the DSSE envelope before delivery, and persists delivery plus receipt metadata through the durable delivery ledger.

Handoff And Delivery Modes

Supported modes:

• produce-and-sign filesystem or EvidenceLocker handoff for operator-controlled transfer;
• purpose-specific Notifier worker delivery to an enabled dora-info-sharing channel after operator approval and trust material are configured.

The target Assurance export profile id is dora.info-sharing. Current compatibility routes are stella export dora-info-sharing, stella verify dora-info-sharing, and the purpose-specific Notify channel runtime. The generic ExportCenter registry does not currently publish this profile as a built-in export.

Required Operator Setup

Before enabling a subscriber channel, the operator must configure:

• tenant compliance profile and sharing arrangement owner;
• subscriber name, collection id, endpoint, jurisdiction or transfer notes, and subscriber id hash policy;
• endpoint allowlist in deployments that restrict egress;
• Authority secretRef for TAXII or peer upload credentials;
• signing key and verification material;
• operator approval for subscriber, redaction profile, key id, destination, and export scope.

Notify stores only references and public metadata. It must not store raw credentials, private keys, or broad PII allowlists in channel JSON.

Minimisation

Default profile: dora-info-sharing-strict-v1.

Strict mode removes source-event PII fields and free-text descriptions before canonicalization. Explicit-authorisation mode requires an approval reference and a concrete PII field allowlist. Operators should treat explicit authorization as exceptional and time-bounded.

Blocking Conditions

Do not deliver a batch when:

• the channel purpose is not dora-info-sharing;
• the channel is disabled or missing an endpoint;
• subscriber approval is missing or expired;
• the DSSE envelope does not verify locally;
• endpoint egress is not allowlisted where sealed mode requires it;
• redaction would include non-allowlisted PII;
• the subscriber rejects the batch and no approved correction has been made.