The Principles

The spe­ci­fi­ca­ti­on of the IDS Asso­cia­ti­on forms the basis for a data mar­ket­place based on Euro­pean values, i.e. data pri­va­cy and secu­ri­ty, equal oppor­tu­nities through a fede­r­a­ted design, and ensu­ring data sov­er­eig­n­ty for the creator of the data and trust among par­ti­ci­pants. It forms the stra­te­gic link bet­ween the crea­ti­on of data in the inter­net of things (IoT) on the one hand and the use of this data in machi­ne lear­ning (ML) and arti­fi­cial intel­li­gence (AI) algo­rith­ms on the other.

Digi­tal respon­si­bi­li­ty is evol­ving from a hygie­ne fac­tor to key dif­fe­ren­tia­tor and source of com­pe­ti­ti­ve advan­ta­ge. Future data plat­forms and mar­kets will be built on design princi­ples that go bey­ond our tra­di­tio­nal under­stan­ding of cyber­se­cu­ri­ty and pri­va­cy. Based on strong data ethics princi­ples the IDS Refe­rence Archi­tec­tu­re Model puts the user in its cent­re to ensu­re trust­wort­hi­ness in eco­sys­tems and sov­er­eig­n­ty over data in the digi­tal age as its key value pro­po­si­ti­on.

IDSA defi­nes a refe­rence archi­tec­tu­re, which sup­ports sov­er­eign exchan­ge and sharing of data bet­ween part­ners inde­pen­dent from their size and finan­cial power. Thus, it meets the needs of both lar­ge and small and medi­um enter­pri­ses (SMEs). Fur­ther down the road, it may be taken up by indi­vi­du­als as well. Whe­ther data of IoT devices is con­cer­ned, in on-pre­mi­se sys­tems or cloud plat­forms, the IDSA aims at pro­vi­ding the stan­dard for sharing data bet­ween dif­fe­rent end­points while ensu­ring data sov­er­eig­n­ty.

A trustworthy architecture

In order to give pro­spects and poten­ti­al users of the IDS tech­no­lo­gy and eco­sys­tem, we have worked on a com­pre­hen­si­ve over­view, allowing to exp­lain the key princi­ples, com­pon­ents, roles and rules of the IDS-based data mar­ket place.

For instance, take a look at the dif­fe­rent roles of tran­sac­tion part­ners: Data Pro­vi­der, Data User, Data Bro­ker, etc.

Then have a glance at the infra­st­ruc­tu­re, con­sis­ting of IDS Con­nec­tors. They are the guar­di­ans of data exchan­ge at any source and point of use. It beco­mes evi­dent that the IDS is not about data lakes, but pro­vi­des a solu­ti­on for dis­tri­bu­t­ed data mar­ket pla­ces, and bet­ween dif­fe­rent, even pro­prie­ta­ry data sphe­res.

The gra­phic also exp­lains the princi­ples of gover­nan­ce and con­trol in the IDS eco­sys­tem, mani­fes­ted by cer­ti­fi­ca­ti­on cri­te­ria for tie­red secu­ri­ty levels, spe­ci­fi­cal­ly appoin­ted eva­lua­ti­on faci­li­ties and cer­ti­fi­ca­ti­on bodies of which the­re are likely to be several on a glo­bal sca­le.

Get acquain­ted with this over­view and find your own path through the ele­ments. This over­view is hel­pful in brin­ging insight and under­stan­ding to the rea­der as it encap­su­la­tes the ent­i­re mea­ning of the IDS eco­sys­tem and why its approach to gran­ting data sov­er­eig­n­ty, inter­ope­ra­bi­li­ty, ease of adop­ti­on and use, and the low tran­sac­tion cost is so uni­que.

Con­cep­ti­on and design: INFOGRAFIK PRO

How to get IDS_Certified

Bene­fits, Steps, and Details

BENEFITS:

Trust is the basis for suc­cess­ful col­la­bo­ra­ti­on bet­ween part­ners. In busi­ness as well as in social life.

Col­la­bo­ra­ti­on is the core of IDS. The­re­fo­re, it is necessa­ry to estab­lish trust bet­ween all IDS par­ti­ci­pants as a key enab­ler for a thri­ving data eco­no­my.

We desi­gned a pro­cess that will estab­lish this trust: the IDS cer­ti­fi­ca­ti­on.

By defi­ning a stan­dar­di­zed level of secu­ri­ty rela­ted to tech­ni­cal and orga­niz­a­tio­nal aspects in an ent­i­re­ly trans­pa­rent pro­cess the IDS cer­ti­fi­ca­ti­on ensu­res secu­ri­ty for ever­yo­ne. The IDS cer­ti­fi­ca­ti­on is of fun­da­men­tal impor­t­ance for a trust­worthy and sov­er­eign data exchan­ge.

Get IDS_certified NOW!

STEPS:

We are hap­py that you deci­ded to get IDS_certified.
Fol­low the­se three steps to start the pro­cess:

  1. We will con­sult you on the pro­cess and help you find the per­fect Eva­lua­ti­on Faci­li­ty.
  2. Onboar­ding ses­si­on with your Eva­lua­ti­on Faci­li­ty. You will get your indi­vi­du­al audit road map.
  3. The Eva­lua­ti­on Faci­li­ty will start the audit pro­cess and col­la­bo­ra­te with you on collec­ting all necessa­ry docu­ments and infor­ma­ti­on.

The Eva­lua­ti­on Faci­li­ty con­ducts the audit, while the Sup­port Office moni­tors the pro­cess, mana­ges the qua­li­ty assuran­ce, and pro­vi­des gui­d­ance to you throughout. After a suc­cess­ful audit we will pre­sent you with the cer­ti­fi­ca­ti­on of com­ple­ti­on.

Read the Leaf­let on Bene­fits & Steps of IDS_Certified!

DETAILS:

The par­ti­ci­pants of the IDS-based data eco­sys­tem will col­la­bo­ra­te by sharing their valu­able data. For the suc­cess of this col­la­bo­ra­ti­on trust bet­ween all par­ties invol­ved is nee­ded, which will be ensu­red by a trans­pa­rent cer­ti­fi­ca­ti­on of the envi­ron­ment and com­pon­ents.

Ther­eby, an eva­lua­ti­on of each participant’s ope­ra­tio­nal envi­ron­ment is requi­red, but also of the com­pon­ents, used in in the IDS-based eco­sys­tem.

To cer­ti­fy a participant’s ope­ra­tio­nal envi­ron­ment means to eva­lua­te his ope­ra­tio­nal envi­ron­ment regar­ding the ful­film­ent of the defi­ned levels of secu­ri­ty, inclu­ding infra­st­ruc­tu­re relia­bi­li­ty and pro­cess com­pli­an­ce.

The­re­fo­re, the cer­ti­fi­ca­ti­on of the participant’s ope­ra­tio­nal envi­ron­ment demons­tra­tes a level of secu­ri­ty regar­ding avai­la­bi­li­ty, con­fi­den­tia­li­ty and inte­gri­ty to all other par­ti­ci­pants and sta­ke­hol­ders. The ope­ra­tio­nal envi­ron­ment cer­ti­fi­ca­ti­on approach is dis­play­ed by two dimen­si­ons: The hori­zon­tal dimen­si­on is Eva­lua­ti­on Depth, describ­ing the level of detail at which an eva­lua­ti­on is per­for­med. The ver­ti­cal dimen­si­on is the incre­a­sing extent of the Secu­ri­ty Requi­re­ments that need to be ful­fil­led. The Cer­ti­fi­ca­ti­on of the par­ti­ci­pants ope­ra­tio­nal envi­ron­ment tar­gets dif­fe­rent levels of capa­bi­li­ties and assuran­ce.

To secu­re the inten­ded cross-indus­tri­al and cross-com­pa­ny infor­ma­ti­on exchan­ge, the Inter­na­tio­nal Data Space (IDS) com­pon­ents must pro­vi­de the requi­red func­tio­n­a­li­ty and an appro­pria­te level of secu­ri­ty. As such, the com­po­nent cer­ti­fi­ca­ti­on is inter­ope­ra­bi­li­ty- and secu­ri­ty-focu­sed, while aiming to streng­t­hen the deve­lo­p­ment and main­ten­an­ce pro­cess of the­se com­pon­ents. The com­po­nent cer­ti­fi­ca­ti­on approach is dis­play­ed by two dimen­si­ons: The depth and rigo­ur of an eva­lua­ti­on incre­a­ses with each of the three defi­ned Assuran­ce Levels. Simi­lar­ly, the secu­ri­ty needs to be requi­red by the data owner and data con­su­mer for data exchan­ge, incre­a­sing with the three defi­ned Secu­ri­ty Pro­files.

The­re are dif­fe­rent Eva­lua­ti­on Faci­li­ties for cer­ti­fy­ing the ope­ra­tio­nal envi­ron­ment and the com­pon­ents.

If you plan to purcha­se IDS com­pon­ents from ano­t­her orga­niz­a­ti­on, usual­ly, that orga­niz­a­ti­on must ensu­re that they are cer­ti­fied, while you need to ensu­re that your ope­ra­tio­nal envi­ron­ment is cer­ti­fied.

Get Cer­ti­fied Now!

Fur­ther Readings/ Learn More

Cri­te­ria Cata­lo­gue: Com­pon­ents- Bro­ker

Cri­te­ria Cata­lo­gue: Com­pon­ents- Con­nec­tor

Cri­te­ria Cata­lo­gue: Ope­ra­tio­nal Envi­ron­ments

Spe­ci­fi­ca­ti­on: IDS Meta Data Bro­ker

Spe­ci­fi­ca­ti­on: IDS Clea­ring House

IDS Cer­ti­fi­ca­ti­on Exp­lai­ned

Stra­te­gy Paper Cer­ti­fi­ca­ti­on

White Paper Cer­ti­fi­ca­ti­on

Unleash the value of your data

When broa­de­ning the per­spec­ti­ve from an indi­vi­du­al use case sce­n­a­rio to a plat­form land­s­cape view, the Inter­na­tio­nal Data Spaces posi­ti­ons its­elf as an archi­tec­tu­re to link dif­fe­rent cloud plat­forms through secu­re exchan­ge and trus­ted sharing of data, i.e. through data sov­er­eig­n­ty.

1.

Make data avail­ab­le – dyna­mic, on demand
(descri­be, expo­se)

2.

Link with eco­sys­tem part­ners
(con­nect, match, inter­pre­te)

3.

Con­trol the access to your data
(usa­ge con­trol)

4.

Crea­te value
(Apps, remo­te soft­ware exe­cu­ti­on, aggre­ga­ti­on)

A blueprint for data space

The refe­rence archi­tec­tu­re model for the Indus­tri­al Data Space con­sists of four par­ti­al archi­tec­tures. It will pre­sent a blue­print for safe data exchan­ge and the effi­ci­ent com­bi­na­ti­on of data and can be con­fi­gu­red for each indi­vi­du­al case.

Business architecture

Inclu­des all con­cepts that are important from an eco­no­mic per­spec­ti­ve, e.g. data gover­nan­ce, coope­ra­ti­ve data manage­ment.

Data and service architecture

Forms the tech­ni­cal func­tio­n­al core of the Indus­tri­al Data Space with app store, bro­kers and con­nec­tors

Software architecture

Descri­bes the imple­men­ta­ti­on of the data and ser­vice archi­tec­tu­re of the Indus­tri­al Data Space.

Security architecture

Con­tains dif­fe­rent secu­ri­ty aspects, e.g. inter­face secu­ri­ty, evi­dence of iden­ti­ty, data use moni­to­ring.

Self determined control of data flows

Unlimited
Interoperability

stan­dard for data flows bet­ween all kinds of data end­points

Trust between different
security domains

com­pre­hen­si­ve secu­ri­ty func­tions pro­vi­ding a maxi­mum level of trust

Governance for the
data economy

usa­ge con­trol and enfor­ce­ment for data flows

Roles Model

Providing, obtaining and utilising data: The roles model for International Data Spaces guarantees the necessary data security and digital sovereignty – have a look at the interaction overview

New standards for the digital economy

With their work on Inter­na­tio­nal Data Spaces. The sci­ence and busi­ness com­mu­nities are pur­suing the objec­ti­ve of set­ting a new com­pre­hen­si­ve stan­dard for data eco­no­my. During the deve­lo­p­ment of the Inter­na­tio­nal Data Spaces, exis­ting stan­dards are being used and fur­ther deve­lo­ped if necessa­ry.

This is whe­re the Inter­na­tio­nal Data Spaces Asso­cia­ti­on gets acti­ve:

Designing the cer­ti­fi­ca­ti­on mea­su­res

Defi­ning and imple­men­ting stan­dards