Events

Event Calen­der

Lec­tures + Seminars

Event calen­dar review

GDPR Work­shop — The Direc­to­ry of Pro­ces­sing Acti­vi­ties with Template

DSGVO Was und Wie Workshop - Das Verzeichnis der Verarbeitungstätigkeiten von SEC4YOU

Due to the gre­at demand of our cus­to­mers and inte­res­ted par­ties, SEC4YOU offe­red a GDPR work­shop in Novem­ber 2017, which spe­ci­fi­cal­ly high­lights the imple­men­ta­ti­on of GDPR mea­su­res and offers affec­ted com­pa­nies the oppor­tu­ni­ty to start with the mea­su­res direct­ly at the work­shop or to sup­port their own pro­ject with tem­pla­tes and decis­i­on-making bases.

The work­shop was aimed at public and pri­va­te com­pa­nies from all sec­tors that pro­cess or store per­so­nal data. Con­tra­ry to the wide­spread opi­ni­on that the GDPR only appli­es to lar­ge com­pa­nies, this ques­ti­on was ans­we­red con­clu­si­ve­ly by work­shop lea­der Man­fred Scholz as well as by two lawy­ers present:

The GDPR affects all com­pa­nies that pro­cess per­so­nal data — regard­less of com­pa­ny size and legal form — as of 25.5.2018!

After explai­ning the histo­ry of the GDPR and the posi­ti­on of Aus­tria in the Euro­pean vote, the par­ti­ci­pan­ts agreed on the essen­ti­al com­pon­ents of the GDPR imple­men­ta­ti­on. As an important task within the GDPR mea­su­res, the new requi­re­ment of kee­ping a regis­ter of pro­ces­sing acti­vi­ties in Aus­tria was discussed.

Direc­to­ry of pro­ces­sing acti­vi­ties using software?

Con­tra­ry to the opi­ni­on of indi­vi­du­al pro­vi­ders, a soft­ware tool for main­tai­ning the direc­to­ry of pro­ces­sing acti­vi­ties should not be at the fore­front of a GDPR pro­ject, as the initi­al crea­ti­on can usual­ly be done in Excel or Word for small and medi­um-sized com­pa­nies. In lar­ge com­pa­nies, or if the main­ten­an­ce effort for the manage­ment and regu­lar con­trol or revi­si­on of the direc­to­ry is to be car­ri­ed out by seve­ral employees or in dis­tri­bu­ted com­pa­nies, the intro­duc­tion of a spe­cial tool can also save costs.

The Direc­to­ry of Pro­ces­sing Acti­vi­ties — DSGVO VV

As has been cus­to­ma­ry in Ger­man data pro­tec­tion for over 10 years as a “pro­ce­du­ral direc­to­ry” or “pro­ce­du­ral over­view”, the GDPR now also requi­res com­pa­nies to main­tain a direc­to­ry of pro­ces­sing acti­vi­ties. Experts see a dif­fe­rence here to the DSG 2000 whe­re in Aus­tria a basic obli­ga­ti­on to report cer­tain data appli­ca­ti­ons in the data pro­tec­tion regis­ter is requi­red (until May 2018) or was requi­red (from May 2018).

An important fea­ture of a pro­ce­du­re direc­to­ry is that the data-pro­ces­sing com­pa­ny pro­ces­ses are recor­ded and not the appli­ca­ti­ons themselves.

=> What the­r­e­fo­re does not belong in a direc­to­ry of pro­ces­sing acti­vi­ties? e.g. MS CRM, Excel or Exchange.

The important con­tents of the direc­to­ry of pro­ces­sing acti­vi­ties have been summarized.

In the role of the respon­si­ble per­son must be recorded:

  • Name and cont­act details of the respon­si­ble per­son, if appli­ca­ble joint­ly respon­si­ble per­son or a repre­sen­ta­ti­ve (EU).
  • Name and cont­act details of the data pro­tec­tion officer
  • Pur­po­se of the processing
  • Cate­go­ries of data subjects
  • Cate­go­ries of per­so­nal data
  • Cate­go­ries of recipients
  • Trans­fer to third count­ries (gua­ran­tees, if applicable)
  • Dele­ti­on periods
  • Gene­ral descrip­ti­on of tech­ni­cal and orga­niza­tio­nal mea­su­res (TOM accor­ding to Art 32 para.1).

On the other hand, pro­ces­sors have the fol­lo­wing recor­ding obligations:

  • Name and cont­act details of the data con­trol­ler, joint data con­trol­ler or repre­sen­ta­ti­ve (EU), if applicable.
  • Name and cont­act details of the data pro­tec­tion officer
  • Cate­go­ries of processing
  • Trans­fer to third count­ries (gua­ran­tees, if applicable)
  • Gene­ral descrip­ti­on of tech­ni­cal and orga­niza­tio­nal mea­su­res (TOM accor­ding to Art 32 para.1)

In the last part of the work­shop, exem­pla­ry examp­les of how a direc­to­ry of pro­ces­sing acti­vi­ties looks like were pre­sen­ted and the SEC4YOU tem­p­la­te V1.1 of the direc­to­ry of pro­ces­sing acti­vi­ties was presented.

DEEPSEC IN-DEPTH SECURITY CONFERENCE 2016

DEEPSEC IN-DEPTH SECURITY CONFERENCE 2016

DEEPSEC In-Depth Secu­ri­ty Con­fe­rence 2016

DEEPSEC 2016 was a gre­at suc­cess. As in pre­vious years, the loca­ti­on The Impe­ri­al Riding School Vien­na — A Renais­sance Hotel was an excel­lent venue for the high qua­li­ty pre­sen­ta­ti­ons. Due to the inter­na­tio­nal audi­ence, all pre­sen­ta­ti­ons were in English.

Espe­ci­al­ly con­vin­cing were work­shops orga­ni­zed in small groups, here an excerpt:

  • Hack­ing von Web­an­wen­dun­gen: Fall­stu­di­en über preis­ge­krön­te Bugs in Goog­le, Yahoo, Mozil­la und mehr, Dawid Czagan (Sile­sia Secu­ri­ty Lab)
  • Do-It-Yours­elf-Patching: Schrei­ben Sie Ihren eige­nen Micro­patch, Mit­ja Kol­sek (ACROS d.o.o.)
  • Siche­re Anwen­dun­gen mit TLS bereit­stel­len, Juraj Somo­rovs­ky (Hack­ma­nit GmbH / Ruhr-Uni­ver­si­tät Bochum)
  • Offen­si­ve iOS-Aus­nut­zung, Mar­co Lan­ci­ni (MWR InfoSecurity)
  • IoT-Hack­ing: Linux Embedded, Blue­tooth Smart, KNX Heim­au­to­ma­ti­sie­rung, Sla­wo­mir Jasek (Secu­Ring)
  • Hands on Hack­ing mit der WiFi Pineapp­le, USB Rub­ber Ducky und LAN Turt­le, Dar­ren Kit­chen, Sebas­ti­an Kin­ne, Robin Wood (Hak5 LLC, Digininja)
  • Offen­si­ve Power­Shell für rote und blaue Teams, Nik­hil Mit­tal (unab­hän­gig)
  • Grund­la­gen von Rou­ting und Swit­ching aus der Sicht von Blue und Red Teams, Paul Cog­gin (Selbst­dar­stel­lung)
  • Pene­tra­ti­ons­tests für Men­schen, Betha­ny Ward & Cyni Win­egard (Trace­Secu­ri­ty)
  • Siche­re Web-Ent­wick­lung, Mar­cus Nie­mietz (Hack­ma­nit)

Many thanks to the Orga-Team Micha­el ‘MiKa’ Kaf­ka & René ‘Lynx’ Pfeif­fer for the excel­lent event, next year we will sure­ly be the­re again!