SOVEREIGN OPEN-SOURCE PLATFORMS · BUILT, HANDED OVER, SUPPORTEDWatch SAFI work, live

WHITE PAPERS

In-depth guides,
free to download.

Practical, vendor-neutral white papers from the team that builds and hands over open-source platforms. No registration needed.

WHITE PAPERSovereign Data ExchangeDesigning an inter-organisation API exchange on the X-Road model (download PDF)

Sovereign Data Exchange

Organisations that must share data with one another usually do it one bilateral interface at a time. The result is expensive to build, hard to secure and almost impossible to audit as a whole. This paper sets out an alternative based on X-Road, the open-source exchange layer developed by the Nordic Institute for Interoperability Solutions (NIIS), founded by Estonia and Finland. Data moves directly from member to member through security servers at each organisation's edge, every message is signed and time-stamped, and the operator governs trust without holding member data. We cover architecture, trust and identifiers, API management on WSO2, first services and a phased roadmap that leaves the operator in full ownership.

  • Point-to-point integration between organisations grows roughly with the square of the number of parties, and every connection carries its own contract, security review and failure mode.
  • The X-Road model replaces that web with a shared exchange in which each organisation is a registered member, runs its own security server at its edge, and exchanges signed, time-stamped messages directly with other members.
  • The central operator governs the member registry, trust services and global configuration, but sits outside the data path: it holds routing and evidence records, and zero copies of member data.
  • Stable four-part service identifiers, a single catalogue and per-service consent rules let providers publish once and let consumers subscribe once, with access enforced at the provider's own edge.
WHITE PAPERSecurity Data Without the BillAn edge-classification approach to SIEM cost, evidence and control (download PDF)

Security Data Without the Bill

Most SIEM platforms are priced on what they ingest, so the bill follows volume rather than value. This paper describes an alternative: classify every event at the edge, before it reaches the indexer, using plain-text rules that a security team can read, test and reverse. Each event ends in one of three places: forwarded and indexed, archived in full at storage prices, or dropped with a recorded reason. A raw archive keeps every event regardless of verdict, so nothing is lost and every decision can be audited. We set out the architecture, the rule process, how to measure the effect honestly, and a practical route from proof of concept to production.

  • SIEM cost is driven largely by ingest volume, and a significant share of what most estates ingest is never searched, alerted on or read; the remedy is to decide where each event should live before it is billed, not after.
  • Classifying events at the edge, on an open-source collector such as Vector, lets an organisation send the SIEM only what is worth indexing while keeping everything else, in full and searchable, at storage prices.
  • Every event has one of three endings: forwarded (indexed and billed), archived (kept at full fidelity off the ingest line) or dropped with a reason, and an event can only be dropped after it has been named twice, first as low value and then as noise.
  • A raw archive receives every event whatever its verdict, which makes each classification decision auditable and allows an archived window to be replayed into the SIEM when an investigation needs it.

STAY CURIOUS

Want the short version?

Our Insights articles cover the same ground in a few minutes.

Read Insights