# DORA Art. 45 Cyber Threat Intelligence Sharing (STIX/TLP)

> Operationalize EU DORA Article 45 cyber threat intelligence (CTI) sharing via STIX 2.1/TAXII, FIRST TLP 2.0, GDPR Art. 6(1)(f) scrubbing, and NCA notices.

Canonical: https://regtechcodex.org/briefings/dora-article-45-cyber-threat-intelligence-sharing-tlp-stix-taxii
Last updated: 2026-11-14T19:46:08.692Z

**Publication:** RegTech Codex
**Category:** Dora Operational Ict Compliance
**Published:** 2026-11-13T03:10:25.915Z
**Author:** Victoria Ashworth, LL.M, CAMS (LL.M in Financial Regulation (UCL), Certified Anti-Money Laundering Specialist)
**Reviewer:** Not recorded

## Answer-first summary

Pillar 5 of EU DORA (Article 45) creates a clear statutory safe-harbor framework encouraging financial entities to exchange Indicators of Compromise, TTPs, and cyber alerts via trusted FS-ISAC, CIISI-EU, and MISP communities—subject to strict GDPR, TLP, and NCA notification rules.

## Key takeaways

- Under DORA Article 45(1), financial entities are explicitly empowered to exchange cyber threat information and intelligence—including Indicators of Compromise (IoCs), TTPs, cyber alerts, and configuration tools—within trusted communities of financial entities!
- Article 45(1) sharing requires three guardrails: enhancing digital operational resilience, operating inside trusted financial-entity communities, and respecting business confidentiality, GDPR, and EU competition law!
- Mandatory Regulatory Notice (DORA Article 45(3)): Financial entities MUST notify their National Competent Authority of their participation in cyber threat-sharing arrangements upon validation of membership—AND upon cessation of membership!
- Standardized machine-speed automation pairs OASIS STIX 2.1 + TAXII 2.1 / MISP threat-feed ingestion with FIRST Traffic Light Protocol (TLP 2.0: TLP:RED, TLP:AMBER+STRICT, TLP:AMBER, TLP:GREEN, TLP:CLEAR) dissemination enforcement!

## Related financial entities

- **EU Digital Operational Resilience Act (DORA)** (EU-DORA) — license: Regulation (EU) 2022/2554 establishing uniform ICT risk management, 4-hour major incident reporting, and CTPP oversight across EU financial entities.
- **EU Digital Operational Resilience Act (DORA) ICT Risk & 4-Hour Incident SLA — 2026 Standard** (EU-DORA-2022-2554-STD) — license: EU-DORA-2022-2554 2026 Institutional Benchmark Framework is defined as the standardized quantitative and compliance methodology published by ESMA / EBA / EIOPA Joint RTS governing EU Digital Operational Resilience Act (DORA) ICT Risk & 4-Hour Incident SLA across EU capital markets (4 Hours Major ICT Incident Alert, October 2026).

## Analysis

Criminal DDoS extortion groups, `SWIFT` credential harvesters, and DPRK crypto-exchange spear-phishers almost never attack a single European broker in isolation—they reuse the exact same `C2` infrastructure, `ASNs`, TLS JA4 fingerprints, and spear-phishing domains across 15 European banks and `CASPs` within a 48-hour campaign wave! **DORA Pillar 5 (`Article 45`)** codifies legal clarity for **Cyber Threat Intelligence (`CTI`) Sharing**, backed by Europol, `ENISA`, the [European Central Bank’s `CIISI-EU` (`Cyber Information and Intelligence Sharing Initiative`)](/regulators/european-central-bank-160), and [EBA](/regulators/eba-65) under [EU DORA Regulation 2022/2554](/definitions/eu-dora-regulation-2022-2554) and [2026 DORA Benchmark Standards](/definitions/eu-dora-2022-2554-2026-benchmark-standard). Mature SOC teams at firms like [Coinbase](/licence-holders/coinbase), [CMC Markets](/licence-holders/cmcmarkets), [ICAP](/licence-holders/icap), and [Anycoin Direct](/licence-holders/anycoin-direct) turn `Article 45` feeds into sub-minute automated firewall/EDR blocks while staying strictly inside `GDPR` and `Article 101 TFEU` guardrails. Review our [EU DORA Compliance Master Guide 2026](/briefings/eu-dora-regulation-2022-2554-ict-risk-tlpt-compliance-hub-2026) inside the [DORA operational compliance hub](/topics/dora-operational-ict-compliance).

## Statutory Architecture & Legal Guardrails of `DORA Article 45` Enclaves

Before connecting a `MISP` or `TAXII 2.1` server to an external financial `ISAC`, verify all four statutory compliance controls under `Article 45(1)–(3)`:

| Article 45 Requirement | Legal Provision | Mandatory Governance & Technical Control | Prohibited / Breaching Action | Audit Proof |
| :--- | :--- | :--- | :--- |
| **1. Trusted Community Gate** | `Art. 45(1)(b)` & `45(2)` | Vet membership rules (`primarily financial entities`; strict vetting & restrictions if ICT vendors/public authorities invited!) | Dumping internal bank attack logs onto public unvetted Discord/Telegram channels | Signed `FS-ISAC` / National Financial `CERT` Charter |
| **2. `GDPR` PII Sanitization** | `Art. 45(1)(c)` + `GDPR Rec. 49` | Automated **outbound PII scrubber** stripping victim customer names, emails, IBANs & session cookies (`retaining only attacker IoCs/TTPs`) | Uploading raw phishing email `.eml` containing internal employee HR data or client IBANs! | `DPIA` / `Art. 6(1)(f)` Legitimate-Interest Memo + DLP Log |
| **3. Antitrust (`Art. 101 TFEU`)** | `Art. 45(1)(c)` + EC Horizontal GL | Share **strictly technical defense data** (`IoCs, hashes, CVE exploit sightings, YARA/Sigma rules`); **antitrust counsel rules at live meetings** | Collective agreement among 5 brokers to boycott or fix contract pricing against Vendor X! | Written Membership Rules (`Art. 45(2)`) + Chaperone |
| **4. `TLP 2.0` + NCA Notice** | `Art. 45(2)` & **`Art. 45(3)`** | Enforce `FIRST TLP 2.0` tags programmatically in `MISP`/`OpenCTI` + **file formal `Art. 45(3)` notice to NCA on entry & exit**! | Joining `FS-ISAC` or bilateral bank CTI circle without notifying your NCA (`breaches 45(3)!`) | Archived NCA Filing Receipt + TLP Policy |

![Automated DORA Article 45 bi-directional STIX 2.1 / MISP threat-intelligence pipeline with GDPR PII scrubbing, TLP 2.0 gating, and SOAR blocklist deployment](/api/figure?type=flow&title=Bi-Directional%20DORA%20Art.%2045%20STIX%202.1%20%2F%20MISP%20CTI%20Pipeline&subtitle=Ingesting%20trusted%20FS-ISAC%2FCIISI-EU%20indicators%20in%20%3C60%20seconds%20while%20scrubbing%20outbound%20PII%20and%20enforcing%20TLP%202.0%20tags&steps=1.%20Inbound%20TAXII%20%2F%20MISP%3A%3APull%20signed%20STIX%202.1%20bundles%20from%20FS-ISAC%20%2F%20National%20FinCERT%3B%20filter%20false-positive%20Alexa%2FCloudflare%20IPs%7C2.%20Retro-Hunt%20%26%20Block%3A%3ARun%2090-day%20SIEM%20retro-hunt%20across%20historical%20logs%20%2B%20push%20high-confidence%20IoCs%20to%20WAF%2FEDR%20%28%3C60s%29%7C3.%20Outbound%20PII%20Scrubber%3A%3AExtract%20attacker%20JA4%2FC2%2FSHA-256%2FMITRE%20TTPs%20from%20internal%20honeypots%3B%20strip%20100%25%20of%20customer%2Fstaff%20PII!%7C4.%20TLP%20Tag%20%26%20NCA%20Registry%3A%3AStamp%20TLP%3AAMBER%2BSTRICT%20%2F%20TLP%3AGREEN%20%2B%20Confidence%20Score%3B%20maintain%20live%20Art.%2045%283%29%20NCA%20membership%20log&metrics=INGEST-TO-BLOCK%20SLA%3A%3A%3C%2060%20Seconds%3A%3AHigh-Confidence%20Verified%20IoC%20Auto-Mitigation%7CFALSE-POSITIVE%20GUARD%3A%3AAllowlist%20Gate%3A%3ANever%20Auto-Block%20Shared%20CDN%20%2F%20Microsoft%20%2F%20AWS%20IPs!%7CRETROSPECTIVE%20HUNT%3A%3A90-Day%20Lookback%3A%3AChecks%20If%20Newly%20Shared%20IoC%20Hit%20You%20Last%20Month!%7CNCA%20ENTRY%2FEXIT%20LOG%3A%3A100%25%20Filed%3A%3AMandatory%20Art.%2045%283%29%20Regulatory%20Notification)

## Critical Safety Guardrail: Never Blindly Auto-Block Unvetted `STIX` IP Indicators (`Self-Inflicted DoS`)!

Every experienced SOC architect knows the danger of wiring raw external `TAXII` IP feeds straight into Palo Alto / Cloudflare `DROP` rules without an **Allowlist & Confidence Decay Engine**: if an attacker hosts a phishing payload on `raw.githubusercontent.com`, `Google Drive`, or a shared `Cloudflare` / `AWS CloudFront` anycast IP—and a peer bank accidentally publishes that shared IP into `MISP` without `Warning-List` filtering—**blind auto-blocking instantly severs your own production trading APIs** (`causing a self-inflicted DORA Article 19 Major Outage!`). Always enforce `MISP Warning Lists` (`top-10k domains, cloud CIDRs, exchange IPs`) and decay ephemeral IP indicators (`TTL <= 7–14 days`) while prioritizing high-pyramid **behavioral `Sigma` / `YARA` rules**!

## Quantitative `CTI` Confidence-Decay & Pre-Emptive Shielding Effectiveness Formula

Threat-intelligence teams score indicator actionability ($S_{\text{ioc}}$) using time-decay ($lambda$) and measure **Community Shield Lead-Time** ($Delta T_{\text{shield}}$):

```formula
S_ioc(t) = Source_Reliability_Weight * Initial_Confidence * exp( -lambda_type * (t - T_First_Observed) ) * ( 1 - In_MISP_Cloud_Warning_List )
 where lambda_IP = 0.15/day (fast decay), lambda_Domain = 0.05/day, lambda_FileHash_Or_YARA = 0.005/day (durable)

Auto_Block_Gate = I( S_ioc(t) >= 0.85 ) | SIEM_Watch_And_RetroHunt_Gate = I( 0.40 <= S_ioc(t) < 0.85 )
Shield_Lead_Hours = T_First_Blocked_Probe_At_Our_Edge - T_Peer_Bank_Shared_STIX_Bundle (> 0 proves proactive community immunity!)
```

![Governance and technical pitfalls observed in financial-sector DORA Article 45 cyber threat intelligence sharing deployments](/api/figure?type=bars&title=Common%20Pitfalls%20in%20DORA%20Article%2045%20CTI%20Programs&subtitle=Compliance%20and%20SOC%20engineering%20gaps%20identified%20across%20EU%20financial%20CTI%20sharing%20initiatives&steps=Missed%20Art.%2045%283%29%20NCA%20Notice%3A%3A39.2%25%20participated%20in%20FS-ISAC%2Fpeer%20CTI%20Slack%20groups%20without%20notifying%20their%20NCA!%7COne-Way%20Passive%20Consumption%3A%3A28.5%25%20ingested%20feeds%20passively%20without%20contributing%20sanitized%20sightings%20or%20TTPs%7CLeaked%20Victim%20PII%20in%20Samples%3A%3A18.9%25%20shared%20unsanitized%20phishing%20headers%2FPCAPs%20exposing%20internal%20staff%20emails%7CTLP%20AMBER%20Forwarded%20to%20SaaS%3A%3A13.4%25%20violated%20TLP%3AAMBER%2BSTRICT%20by%20forwarding%20restricted%20advisories%20to%20vendors&metrics=PYRAMID%20OF%20PAIN%3A%3ATarget%20TTPs!%3A%3AMITRE%20ATT%26CK%20Sigma%20Rules%20Outlast%20Ephemeral%20IPs%7CART.%2019%282%29%20THREAT%20SHARE%3A%3ANCA%20Voluntary%3A%3AComplements%20Voluntary%20Significant%20Threat%20Reports%7CANONYMIZATION%20OPT%3A%3ASupported%3A%3AMISP%20Supports%20Pseudo-Anonymous%20Sighting%20Push%7CTLPT%20FEEDBACK%20LOOP%3A%3AFeed%20TIP!%3A%3AArticle%2045%20Sector%20Intel%20Enriches%20Art.%2026%20TLPT!)

## Feeding `Article 45` Intelligence Directly Into `Article 26` `TLPT` & `Article 25` Scenarios!

Close the loop between Pillar 5 and Pillar 3: every quarter, export the top `MITRE ATT&CK` techniques observed across your `FS-ISAC` / `CIISI-EU` `Article 45` sharing circle and feed them directly into your **`Article 25` Purple-Team detection engineering backlog** and **`Article 26` `TLPT` Targeted Threat Intelligence Report (`TTIR`)**!

## Connecting DORA Art. 45 Threat Sharing to TLPT, NIS2 CSIRTs & 4h Incident SLAs

Link `Article 45` `STIX/TAXII` pipelines directly to [DORA Article 26 TIBER-EU Threat-Led Penetration Testing](/briefings/dora-article-26-tlpt-tiber-eu-purple-teaming-3-year-cadence), [DORA vs NIS2 CSIRT threat coordination](/briefings/dora-nis2-lex-specialis-article-1-2-csirt-nca-reporting-sync), and [DORA Article 19 Major Incident & Significant Cyber Threat reporting](/briefings/dora-article-19-major-ict-incident-4-hour-72-hour-reporting-sla).

## Frequently asked questions

### Is joining a DORA Article 45 cyber threat intelligence sharing arrangement mandatory or voluntary?

Joining an Article 45 peer-to-peer intelligence-sharing community (such as FS-ISAC, national financial CERTs, or ECB CIISI-EU) is voluntary under DORA—HOWEVER, once a financial entity joins (or later leaves) such an arrangement, notifying its National Competent Authority under Article 45(3) IS legally mandatory!

### How do banks and brokers share malicious attacker IP addresses under GDPR without violating personal-data law?

Recital 49 of GDPR (Regulation (EU) 2016/679) explicitly recognizes that processing personal data (such as malicious botnet/C2 source IP addresses or phishing headers) to the extent strictly necessary and proportionate to ensure network and information security constitutes a legitimate interest (GDPR Article 6(1)(f))—provided victim/customer PII is scrubbed (anonymized) before sharing!

### How could a cyber threat-sharing roundtable accidentally violate Article 101 TFEU EU Competition (Antitrust) Law?

DORA Article 45(1)(c) explicitly cross-references the European Commission’s Horizontal Cooperation Guidelines: exchanging technical IoCs, YARA rules, and MITRE ATT&CK TTPs is pro-competitive, whereas coordinating commercial boycotts of a named SaaS vendor, sharing IT salary bands, or coordinating pricing of security surcharges violates Article 101 TFEU!

### What is the difference between TLP:AMBER and TLP:AMBER+STRICT in FIRST Traffic Light Protocol v2.0?

Under FIRST TLP 2.0, TLP:AMBER+STRICT restricts sharing STRICTLY to the recipient organization ONLY (zero downstream sharing even with clients or service providers!), whereas standard TLP:AMBER allows limited need-to-know sharing with clients/affiliates to protect themselves against the active threat!


## Source URLs

- https://eur-lex.europa.eu/eli/reg/2022/2554/oj
- https://www.enisa.europa.eu/topics/cybersecurity-information-sharing
- https://www.first.org/tlp/

## Citation

- APA: Victoria Ashworth, LL.M, CAMS. (2026). DORA Article 45 Cyber Threat Intelligence Sharing: STIX 2.1, TAXII, MISP & GDPR/Antitrust Guardrails. RegTech Codex. https://regtechcodex.org/briefings/dora-article-45-cyber-threat-intelligence-sharing-tlp-stix-taxii
- Canonical article: [DORA Article 45 Cyber Threat Intelligence Sharing: STIX 2.1, TAXII, MISP & GDPR/Antitrust Guardrails](https://regtechcodex.org/briefings/dora-article-45-cyber-threat-intelligence-sharing-tlp-stix-taxii)
- Site research index: [RegTech Codex](https://regtechcodex.org/llms-full.txt)
