UMOWA POWIERZENIA PRZETWARZANIA DANYCH OSOBOWYCH

UMOWA POWIERZENIA PRZETWARZANIA DANYCH OSOBOWYCH

Wersja z dn. 09.08.2023.

Niniejsza umowa powierzenia przetwarzania danych osobowych (zwana dalej "Umową powierzenia") stanowi część umowy, zwanej dalej "Umową", która została zawarta pomiędzy OVH Sp. z o.o. ("OVH") a Klientem określającej warunki mające zastosowanie do usług świadczonych przez OVH ("Usługi"). Niniejsza Umowa powierzenia i inne postanowienia Umowy są komplementarne. Niemniej jednak, w przypadku niezgodności pomiędzy nimi, zastosowanie będzie miała Umowa powierzenia.

Terminy rozpoczynające się z wielkiej litery, które nie zostały zdefiniowane w niniejszej Umowie powierzenia, należy rozumieć tak, jak zostały one zdefiniowane w Umowie.

„Podmiot danych”,

„Wiążące reguły korporacyjne", „Administrator”, „Dane osobowe”, „Naruszenie ochrony danych osobowych”, „Przetwarzanie”, „Podmiot przetwarzający”, „Organ nadzorczy” należy rozumieć zgodnie z definicjami zawartymi w Rozporządzeniu Parlamentu Europejskiego i Rady (UE) 2016/679 z dnia 27 kwietnia 2016 r. w sprawie ochrony osób fizycznych w związku z przetwarzaniem danych osobowych i w sprawie swobodnego przepływu takich danych oraz uchylenia dyrektywy 95/46/WE („Ogólne rozporządzenie o ochronie danych” lub „RODO”).

Niniejsza DPA zgodnie z artykułem 28 RODO określa warunki, na jakich OVH jest uprawniony, jako Podmiot przetwarzający, w ramach świadczonych Usług określonych w Umowie, do przetwarzania Danych Osobowych w imieniu i na polecenie Klienta, z wyłączeniem czynności przetwarzania danych osobowych wykonywanych przez OVHcloud jako Administratora. Warunki przetwarzania przez OVHcloud jako Administratora Danych Osobowych dotyczących Klienta (w tym agentów Klienta) są określone w Polityce Wykorzystania Danych OVHcloud.

Dla celów niniejszej DPA, Klient, może działać jako „Administrator” lub „Podmiot przetwarzający” w stosunku do Danych Osobowych, pod warunkiem że jeśli Klient działa jako podmiot przetwarzający w imieniu zewnętrznego Administratora danych, Strony wyrażają zgodę na poniższe warunki:

(a) Klient zapewnia, że (I) uzyskał od Administratora wszelkie zezwolenia niezbędne do podpisania niniejszej Umowy powierzenia, w tym wskazał OVH jako podmiot mający dokonywać dalszego przetwarzania, (II) zawarł on z Administratorem umowę, która jest w pełni zgodna z warunkami Umowy zawierającej niniejszą Umowę powierzenia, zgodnie z artykułem 28 RODO, (III) wszelkie polecenia otrzymane przez OVH od

Klienta w ramach realizacji Umowy oraz niniejszej Umowy powierzenia są w pełni

zgodne z poleceniami

Administratora oraz, (IV) wszelkie informacje przekazane lub udostępnione przez OVH na podstawie niniejszej Umowy powierzenia są odpowiednio przekazywane Administratorowi;

(b) OVH powinno (I) przetwarzać Dane Osobowe wyłącznie zgodnie z poleceniem Klienta i (II) nie otrzymywać żadnych poleceń bezpośrednio od Administratora, poza przypadkami, gdy Klient przestał istnieć faktycznie lub formalnie i nie ma prawnego następcy, który przejmie prawa i obowiązki Klienta;

(c) Klient, który ponosi pełną odpowiedzialność wobec OVH w zakresie właściwej realizacji zobowiązań Administratora zgodnie z postanowieniami niniejszej Umowy powierzenia, zabezpiecza i chroni OVH przed (I) wszelkimi działaniami Administratora niezgodnymi z obowiązującym prawem i (II) przed wszelkimi działaniami, roszczeniami lub skargami ze strony Administratora dotyczącymi jakichkolwiek postanowień Umowy (w tym niniejszej Umowy powierzenia) lub jakichkolwiek poleceń otrzymanych przez OVH od Klienta.

1. Zakres

1.1 OVH jest upoważniony, jako Podmiot przetwarzający działający zgodnie z poleceniami Klienta, do przetwarzania Danych Osobowych Administratora w zakresie niezbędnym do świadczenia Usług.

1.2 Charakter operacji przeprowadzanych przez OVH na Danych Osobowych może być związany z obliczaniem, przechowywaniem i/lub z innymi Usługami określonymi w Umowie.

1.3 Rodzaj Danych Osobowych i Podmiotów Danych są określane i kontrolowane przez

Klienta.

1.4 Czynności przetwarzania są wykonywane przez OVH przez okres określony w Umowie.

2. Wybór Usług

2.1 Wyłącznie odpowiedzialnym za wybór Usług jest Klient. Klient zapewnia, że wybrane Usługi posiadają wymagane cechy oraz spełniają warunki zapewniające zgodność z działalnością Administratora i celami przetwarzania, jak również z rodzajem Danych Osobowych przetwarzanych w ramach Usług, w tym gdy Usługi są wykorzystywane do przetwarzania Danych Osobowych podlegających szczególnym regulacjom prawnym lub

standardom (takich jak dane dotyczące zdrowia czy dane bankowe w niektórych krajach). Klient jest informowany, że niektóre Usługi proponowane przez OVH posiadają środki organizacyjne oraz środki bezpieczeństwa zaprojektowane specjalnie do przetwarzania danych dotyczących zdrowia lub danych bankowych.

2.2 Jeśli przetwarzanie danych przez Administratora może powodować wysokie ryzyko naruszenia praw i wolności osób fizycznych, Klient powinien ostrożnie wybierać Usługi. Przy ocenie ryzyka należy uwzględnić w szczególności, ale nie wyłącznie, następujące kryteria: ocena lub punktowanie Podmiotów Danych; zautomatyzowane podejmowanie decyzji ze skutkiem prawnym lub w podobny sposób znacząco wpływających; systematyczne monitorowanie Podmiotów Danych; przetwarzanie danych wrażliwych lub danych o charakterze szczególnie osobistym; przetwarzanie na dużą skalę; dopasowywanie lub łączenie zbiorów danych; przetwarzanie danych Podmiotów Danych wymagających szczególnej opieki; wykorzystywanie do przetwarzania nowych innowacyjnych technologii nieznanych społeczeństwu.

2.3 OVH zobowiązuje się udostępnić Klientowi informacje, na warunkach określonych poniżej w punkcie „Audyty”, dotyczące stosowanych w ramach Usług środków bezpieczeństwa, w zakresie niezbędnym do oceny zgodności tych środków z czynnościami przetwarzania Administratora.

3. Zgodność z obowiązującymi przepisami

Każda ze stron zobowiązuje się do przestrzegania obowiązujących przepisów dotyczących ochrony danych osobowych (w tym Rozporządzenia o Ochronie Danych Osobowych).

4. Obowiązki OVH

4.1 OVH zobowiązuje się:

a) przetwarzać Dane Osobowe przesłane, przechowywane i wykorzystywane przez Klienta w ramach Usług tylko w zakresie koniecznym i proporcjonalnym do świadczenia Usług zgodnie z Umową,

b) nie uzyskiwać dostępu ani nie wykorzystywać Danych Osobowych do celów innych, niż wymagane do świadczenia Usług (w szczególności w odniesieniu do celów zarządzania incydentami),

c) wdrożyć środki techniczne oraz organizacyjne opisane w Umowie, w celu zapewnienia bezpieczeństwa Danych Osobowych w ramach Usługi,

d) zapewnić, że pracownicy OVH upoważnieni do przetwarzania Danych Osobowych zgodnie z Umową podlegają obowiązkowi zachowania tajemnicy i

zostali odpowiednio przeszkoleni w zakresie ochrony Danych Osobowych, informować Klienta, jeżeli jego zdaniem wydane mu polecenie stanowi naruszenie

Rozporządzenia RODO lub innych przepisów Unii Europejskiej lub państwa członkowskiego Unii Europejskiej o ochronie danych.

4.2 W przypadku wniosków otrzymanych od organów sądowych, administracyjnych lub innych o przekazanie Danych Osobowych przetwarzanych przez OVHcloud zgodnie z niniejszą Umową, OVHcloud podejmuje uzasadnione starania, by (i) przeanalizować kompetencje organu wnioskującego oraz zasadność wniosku, (ii ) odpowiadać wyłącznie organom i na wnioski, które nie są oczywiście niezasadne i nieważne, (iii) ograniczyć komunikację do danych wymaganych przez organ oraz (iv) wcześniej poinformować Klienta (o ile nie jest to zabronione przez obowiązujące prawo).

4.3 Jeżeli wniosek pochodzi od organu spoza Europy i ma na celu uzyskanie informacji o danych osobowych przetwarzanych przez OVHcloud zgodnie z niniejszą Umową powierzenia w imieniu Klienta europejskiego, OVHcloud odrzuca taki wniosek, z zastrzeżeniem następujących przypadków:

(x) wniosek został złożony zgodnie z umową międzynarodową, np. umową o wzajemnej pomocy prawnej, obowiązującą między państwem wnioskującym a Unią Europejską lub państwem członkowskim, w którym znajdują się dane osobowe, lub państwem członkowskim podmiotu OVHcloud, w którym klient zarejestrował swoje konto klienta OVHcloud;

(y) wnioskowane Dane Osobowe są przechowywane w centrum danych zlokalizowanym poza Unią Europejską;

(z) wniosek jest złożony zgodnie z art. 49 RODO, w szczególności służy ważnemu interesowi publicznemu uznanemu przez prawo Unii Europejskiej lub prawo państwa członkowskiego Unii Europejskiej lub jest niezbędny do ochrony żywotnych interesów podmiotu danych albo innych osób.

4.4 Na pisemne żądanie Klienta OVH zapewni Klientowi swoją pomoc w przeprowadzeniu oceny skutków dla ochrony danych i konsultacji z właściwym organem nadzorczym, jeśli jest to wymagane od Klienta zgodnie z obowiązującym prawem dotyczącym ochrony danych osobowych, wyłącznie w zakresie, w jakim ta pomoc jest konieczna i dotyczy przetwarzania przez OVH Danych Osobowych objętych tą Umową powierzenia. Pomoc ta będzie polegać

na zapewnieniu przejrzystości w zakresie środków bezpieczeństwa wdrożonych przez OVH dla Usług.

4.5 OVH zobowiązuje się do wdrożenia następujących środków technicznych i

organizacyjnych:

(a) fizyczne środki bezpieczeństwa, mające na celu uniemożliwienie dostępu osobom niepowołanym do Infrastruktury, na której są przechowywane dane Klienta,

(b) weryfikacja tożsamości i dostępu za pomocą systemu uwierzytelniania, jak również polityka dotycząca haseł,

(c) system zarządzania dostępem, który ogranicza dostęp do pomieszczeń do tych osób, które muszą mieć do nich dostęp w ramach pełnienia swoich obowiązków i w zakresie ich odpowiedzialności,

(d) personel ochrony odpowiedzialny za monitorowanie fizycznego bezpieczeństwa pomieszczeń OVH,

(e) system, który fizycznie i logicznie izoluje od siebie poszczególnych klientów,

(f) procesy uwierzytelniania dla użytkowników i administratorów oraz środki,

mające na celu ochronę dostępu do funkcji administracyjnych,

(g) system zarządzania dostępem dla operacji wsparcia i konserwacji, który działa na zasadach najmniejszych uprawnień i potrzebnych informacji, oraz

(h) procesy i środki służące do śledzenia wszystkich działań przeprowadzanych w

jego systemie informatycznym.

4.6 Powyższe środki techniczne i organizacyjne zostały szerzej opisane na Stronie internetowej OVH.

5. Naruszenie ochrony danych osobowych

5.1 Jeśli OVH stwierdzi wystąpienie incydentu wpływającego na Dane Osobowe

Administratora

(takiego jak nieuprawniony dostęp, utrata, ujawnienie lub modyfikacja danych), bez zbędnej zwłoki zgłasza go Klientowi.

5.2 Zgłoszenie musi (I) opisywać charakter incydentu, (II) opisywać możliwe konsekwencje incydentu, (III) opisywać środki zastosowane lub proponowane przez OVH w odpowiedzi na incydent i (IV) zawierać punkt kontaktowy OVH.

6. Lokalizacja i przekazywanie danych

6.1 W przypadku, gdy Usługa umożliwia Klientowi przechowywanie Treści, a w szczególności Danych Osobowych, lokalizacja (lokalizacje) lub obszar geograficzny dostępnych Centrów Danych są określone na stronie internetowej OVH. W przypadku dostępności kilku lokalizacji lub obszarów geograficznych, Klient wybiera jedną z nich podczas składania zamówienia. Z zastrzeżeniem odmiennych postanowień obowiązujących Szczegółowych Warunków Usług, OVH nie może bez zgody Klienta zmienić lokalizacji lub obszaru geograficznego wybranego podczas składania zamówienia.

6.2 Z zastrzeżeniem poprzednich postanowień dotyczących lokalizacji Centrów Danych, OVH i upoważnione Podrzędne Podmioty Przetwarzające na podstawie punktu 7 poniżej mogą zdalnie przetwarzać Treści Klientów pod warunkiem, że takie przetwarzanie odbywa się wyłącznie, gdy jest to niezbędne do realizacji Usług, a w szczególności w odniesieniu do celów zarządzania bezpieczeństwem i uaktualniania usług.

6.3 W odniesieniu do korzystania z Usług zlokalizowanych w pozaeuropejskich Centrach Danych, (a) Centra Danych mogą znajdować się w krajach, które podlegają decyzji Komisji Europejskiej w sprawie adekwatności zgodnie z art. 45 RODO („Decyzja o adekwatności”) i/lub ( b) Treść Klienta może, zgodnie z punktami 6.2 i 7 niniejszej Umowy powierzenia, być przetwarzana z krajów niepodlegających Decyzji o adekwatności.

6.4 W przypadku gdy Klient korzysta z Usług, o których mowa w punkcie powyżej do celów przetwarzania Danych osobowych podlegających RODO, Klient jest uważany za administratora danych, OVHcloud za podmiot przetwarzający a spółki zależne OVHcloud za dalsze podmioty przetwarzające. W przypadku operacji przekazywania danych osobowych do spółek zależnych zlokalizowanych w państwach, które nie dysponują Decyzją stwierdzającą odpowiedni stopień ochrony, OVHcloud uznaje się za Eksportera danych, a jego spółki zależne za Importerów danych w rozumieniu RODO. W tym kontekście OVHcloud i jej spółki zależne zawarły standardowe klauzule umowne przyjęte decyzją wykonawczą (UE) 2021/914 Komisji Europejskiej z dnia 4 czerwca 2021 r. ("Standardowe Klauzule Umowne"), załączone do niniejszego dokumentu, mające zastosowanie w przypadku tego typu operacji przekazywania.

6.5 W przypadku Usług zlokalizowanych w centrach danych zlokalizowanych w Unii Europejskiej, jeżeli mające zastosowanie Warunki korzystania z Usług przewidują, że przetwarzanie danych osobowych będące przedmiotem niniejszego dokumentu może być realizowane z jednego lub kilku krajów nie dysponujących Decyzją stwierdzającą odpowiedni stopień ochrony, zastosowanie mają wspomniane powyżej Standardowe Klauzule Umowne.

6.6 Klient jest odpowiedzialny (a) za ocenę skuteczności Standardowych Klauzul Umownych załączonych do niniejszego dokumentu, w tym za środki techniczne i organizacyjne, w szczególności w odniesieniu do kategorii danych osobowych, które Klient zamierza przetwarzać w ramach Usług, oraz prawa i praktyki kraju lub krajów odbierających dane, w celu ustalenia, czy istnieją elementy, które mogą mieć wpływ na skuteczność Standardowych Klauzul Umownych i (b) jeżeli ocena wykaże, że Standardowe Klauzule Umowne są nieskuteczne, wdrożenie, zgodnie z zaleceniami Europejskiej Rady Ochrony Danych, dodatkowych środków, które zapewnią poziom ochrony odpowiadający poziomowi ochrony gwarantowanemu w Unii Europejskiej. OVHcloud zobowiązuje się do udzielenia Klientowi pomocy w przeprowadzeniu wyżej wymienionej oceny przekazując mu, na jego wniosek, wszelkie istotne informacje będące w jego posiadaniu. Ponadto Klient jest odpowiedzialny za dopełnianie wszelkich formalności i / lub uzyskanie wszelkich zezwoleń lub zgód, które mogą, w stosownych przypadkach, być wymagane, w celu umożliwienia przekazywania danych osobowych do krajów niedysponujących Decyzją stwierdzającą odpowiedni stopień ochrony.

7. Dalsze przetwarzanie

7.1 Z zastrzeżeniem postanowień punktu 6 „Lokalizacja i przekazywanie danych” powyżej, OVH jest upoważniony do korzystania z usług dalszych podmiotów przetwarzających w celu uzyskania wsparcia w zakresie świadczenia Usług. W ramach takiego wsparcia dalsze podmioty przetwarzające mogą uczestniczyć w czynnościach przetwarzania danych przez OVH zgodnie z poleceniami Klienta. 7.2 Listę dalszych podmiotów przetwarzających uprawnionych do udziału w czynnościach przetwarzania przez OVH zgodnie z poleceniem Klienta („Dalszy(e) Podmiot(y)

Przetwarzający(e)”), w tym przedmiotowych Usług, a także lokalizację, z której mogą przetwarzać Dane Osobowe Klienta na podstawie niniejszej Umowy, zamieszczono (a) stronie internetowej OVH lub (b) jeżeli Dalszy Podmiot Przetwarzający uczestniczy jedynie w określonej Usłudze – w odpowiednich Warunkach Szczególnych.

7.3 Jeżeli OVH zadecyduje o zmianie Dalszego Podmiotu Przetwarzającego lub o dodaniu nowego Dalszego Podmiotu Przetwarzającego („Zmiana Dalszego Podmiotu Przetwarzającego”), OVH poinformuje Klienta w swoim panelu sterowania lub pocztą elektroniczną (na adres poczty elektronicznej zarejestrowany na Koncie Klienta) (a) z wyprzedzeniem trzydziestu (30) dni, jeżeli

Dalszy Podmiot Przetwarzający jest Podmiotem Powiązanym z OVH zlokalizowanym w Unii Europejskiej lub w kraju, którego dotyczy Decyzja stwierdzająca odpowiedni stopień ochrony, lub (b) z wyprzedzeniem dziewięćdziesięciu (90) dni w innym przypadku. Klientowi przysługuje prawo zgłoszenia sprzeciwu wobec Zmiany Dalszego Podmiotu

Przetwarzającego przewidziane w RODO. Sprzeciw ten powinien być zgłoszony do OVH w ciągu piętnastu (15) dni od powiadomienia Klienta przez OVH o Zmianie Dalszego Podmiotu Przetwarzającego i powinien przedstawiać przyczyny sprzeciwu. Taki sprzeciw zgłaszany jest przez Klienta za pośrednictwem jego Interfejsu Zarządzania w kategorii „Wniosek dotyczący ochrony danych” [„Data Protection request”] lub w piśmie do

Inspektora Ochrony Danych: Data protection Officer, OVH SAS, 2 rue Kellermann 59100 Roubaix (France). OVH w żadnym wypadku nie ma obowiązku odstąpienia od Zmiany Dalszego Podmiotu Przetwarzającego. Jeżeli po sprzeciwie Klienta OVH nie odstąpi od Zmiany Dalszego Podmiotu Przetwarzającego, Klientowi przysługuje prawo wypowiedzenia Usług, których zmiana dotyczy.

7.4 OVH zapewnia, że każdy Dalszy Podmiot Przetwarzający jest zdolny do spełniania zobowiązań podjętych przez OVH w niniejszej Umowie powierzenia dotyczących przetwarzania Danych Osobowych realizowanego przez ten Dalszy Podmiot Przetwarzający. W tym celu OVH zawiera umowę z tym Dalszym Podmiotem Przetwarzającym. OVH pozostaje w pełni odpowiedzialny wobec

Klienta za realizację wszelkich zobowiązań niedopełnionych przez tego Podwykonawcę

Przetwarzania.

7.5 Aby uniknąć wszelkich wątpliwości, OVH jest upoważniony do nawiązywania współpracy z dostawcami zewnętrznymi (takimi jak dostawcy energii elektrycznej, dostawcy sieci, firmy zarządzające punktami połączeń sieciowych, kolokowane centra danych, dostawcy sprzętu i oprogramowania, przewoźnicy, dostawcy techniczni, firmy ochroniarskie), niezależnie od ich lokalizacji, bez konieczności informowania Administratora, ani uzyskiwania jego uprzedniej zgody, o ile tacy dostawcy zewnętrzni nie będą przetwarzali Danych Osobowych Klienta.

8. Obowiązki Klienta

8.1 W celu przetwarzania Danych Osobowych zgodnie z Umową, Klient dostarcza OVH na piśmie

(a) odpowiednie polecenia i (b) wszelkie informacje niezbędne do utworzenia przez Podmiot przetwarzający rejestru czynności przetwarzania. Wyłącznie odpowiedzialnym za te informacje oraz polecenia przekazane OVH jest Klient.

8.2 Klient jest odpowiedzialny za zapewnienie, że:

a) przetwarzanie Danych Osobowych Klienta, jako część realizacji Usługi, posiada odpowiednią podstawę prawną (na przykład zgoda Podmiotów Danych, zgoda

Administratora, uzasadnione interesy, zezwolenie od właściwego organu

nadzorczego, itp.),

b) zostały zrealizowane wszelkie wymagane procedury i formalności (takie jak ocena skutków dla ochrony danych, powiadomienie właściwego organu do spraw ochrony danych i wniosek o udzielenie zezwolenia, gdy jest to wymagane),

c) Podmioty Danych, zostały poinformowane o przetwarzaniu ich Danych Osobowych w zwięzłej, przejrzystej, zrozumiałej i łatwo dostępnej formie, jasnym i prostym językiem zgodnie z przepisami RODO,

d) Podmioty Danych, zostały poinformowane, że w każdej chwili mogą wykonywać przysługujące im prawa zgodnie z RODO bezpośrednio u Administratora.

8.3 Klient jest odpowiedzialny za wdrożenie odpowiednich technicznych i organizacyjnych środków zapewniających bezpieczeństwo zasobów, systemów, aplikacji i operacji, które nie wchodzą w zakres odpowiedzialności OVH zgodnie z Umową (w szczególności systemów i oprogramowania wdrożonych i uruchomionych przez Klienta lub Użytkowników w ramach Usług).

9. Prawa Podmiotów Danych

9.1 Administrator jest całkowicie odpowiedzialny za informowanie Podmiotów Danych, o przysługujących im prawach, i za przestrzeganie tych praw, w tym prawa dostępu, sprostowania, usunięcia, ograniczenia lub przenoszenia.

9.2 OVH w miarę możliwości zapewni pomoc w wywiązywaniu się z obowiązku odpowiadania na żądania Podmiotów Danych. Pomoc ta może polegać na (a) informowaniu Klienta o każdym wniosku otrzymanym bezpośrednio od Podmiotu Danych i (b) umożliwieniu Administratorowi projektowania i wdrażania technicznych i organizacyjnych środków niezbędnych do odpowiadania na żądania Podmiotów Danych. Administrator ponosi pełną odpowiedzialność za odpowiadanie na te żądania. 9.3 Klient przyjmuje do wiadomości i zgadza się, że w przypadku, gdy taka współpraca i pomoc będzie wymagać znacznych zasobów ze strony Podmiotu przetwarzającego, wysiłki te zostaną podjęte za opłatą po uprzednim powiadomieniu Klienta i uzgodnieniu z Klientem.

10. Usunięcie i zwrot Danych Osobowych

10.1 Po wygaśnięciu Usługi (w szczególności w przypadku jej zakończenia lub nieodnowienia), OVH zobowiązuje się usunąć na zasadach przewidzianych w Umowie, całą zawartość (w tym informacje, dane, pliki, systemy, aplikacje, strony internetowe i inne elementy), która jest powielana, przechowywana, instalowana i w inny sposób używana przez Klienta w ramach Usług, chyba że wniosek złożony przez właściwy organ sądowy lub

prawny, lub obowiązujące prawo Unii Europejskiej lub państwa członkowskiego Unii

Europejskiej, stanowi inaczej.

10.2 Klient jest w pełni odpowiedzialny za wykonanie wszelkich operacji (takich jak tworzenie kopii zapasowych, przekazywanie danych do rozwiązań stron trzecich, Snapshoty, itp.) niezbędnych do zabezpieczenia Danych Osobowych, w szczególności przed zakończeniem lub wygaśnięciem Usług i przed przystąpieniem do operacji usunięcia, aktualizacji lub przeinstalowania Usług.

10.3 W związku z tym Klient jest informowany, że zakończenie i wygaśnięcie Usług z jakiegokolwiek powodu (w tym, ale nie wyłącznie, ich nieodnowienia), jak również niektóre operacje aktualizacji lub przeinstalowania Usług, powodują automatyczne i nieodwracalne usunięcie całej zawartości (w tym informacji, danych, plików, systemów, aplikacji, stron internetowych i innych elementów), która jest powielana, przechowywana, instalowana lub w inny sposób używana przez Klienta w ramach Usług, w tym ewentualnych kopii zapasowych.

11. Odpowiedzialność

11.1 OVH odpowiada za szkody spowodowane przetwarzaniem wyłącznie, gdy (I) nie dopełnił obowiązków, które RODO nakłada na podmioty przetwarzające lub gdy (II) działał wbrew zgodnym z prawem pisemnym instrukcjom Klienta. W takich przypadkach zastosowanie ma zapis dotyczący odpowiedzialności zawarty w Umowie.

11.2 Gdy OVH i Klient uczestniczą w przetwarzaniu w ramach niniejszej Umowy, które spowodowało szkody Podmiotom Danych, Klient w pierwszej kolejności zapłaci pełne odszkodowanie (lub inną rekompensatę) Podmiotowi Danych, a następnie będzie mógł żądać od OVH zwrotu części odszkodowania odpowiadającej części szkody, za którą ponosi on odpowiedzialność, z zastrzeżeniem ograniczeń odpowiedzialności stosowanych w ramach Umowy.

12. Audyty

12.1 OVH udostępnia Klientowi wszelkie informacje niezbędne do (a) wykazania zgodności z wymaganiami RODO i (b) umożliwienia przeprowadzenia audytów. Informacje te są dostępne w formie standardowej dokumentacji na Stronie internetowej OVH. Dodatkowe informacje mogą zostać przekazane Klientowi po uprzednim skontaktowaniu się Klienta z Biurem Obsługi Klienta.

12.2 Jeśli Usługa posiada certyfikat, jest zgodna z kodeksem postępowania lub podlega szczególnym procedurom audytu, OVH udostępnia Klientowi te certyfikaty i raporty z audytów na jego pisemne żądanie. 12.3 Jeśli powyższe informacje, raporty i certyfikaty okażą się niewystarczające, aby Xxxxxx mógł wykazać, że spełnia zobowiązania ustanowione przez RODO, OVH i Klient uzgodnią warunki operacyjne, warunki bezpieczeństwa oraz finansowe technicznej inspekcji na miejscu. W każdym przypadku, warunki tej inspekcji nie mogą wpływać na bezpieczeństwo innych klientów OVH.

12.4 Wspomniana wyżej inspekcja, a także przekazanie certyfikatów i raportów z audytów, mogą być przedmiotem dodatkowych kosztów.

12.5 Wszelkie informacje przekazane Klientowi zgodnie z tym punktem i niedostępne na Stronie internetowej OVH uważa się za poufne informacje OVH w ramach Umowy. Przed przekazaniem takich informacji Klient może być zobowiązany do podpisania umowy o poufności.

12.6 Niezależnie od powyższego Klient jest upoważniony do odpowiadania na wnioski właściwego organu nadzorczego, pod warunkiem że ujawni wyłącznie informacje wymagane przez wspomniany organ nadzorczy. W takim przypadku, o ile nie jest to zabronione przez obowiązujące prawo, Klient powinien najpierw skonsultować się z OVH w sprawie ujawnienia informacji.

13. Kontakt z OVH

W przypadku pytań dotyczących danych osobowych (incydenty, warunki korzystania, itp.), Klient może skontaktować się z OVH:

(a) Tworząc zgłoszenie w Panelu Klienta,

(b) Korzystając z formularza kontaktowego dostępnego na stronie OVH,

(c) Kontaktując się z Biurem Obsługi Klienta OVH,

(d) Pocztą na adres: OVH SAS, Data Protection Officer, 0 xxx Xxxxxxxxxx, 00000 Xxxxxxx

Xxxxxxx.

STANDARD CONTRACTUAL CLAUSES

Transfers from processor to processor

PREAMBLE

OVH SAS is the (direct or indirect) parent company of the OVH European Affiliates.

OVH SAS and the OVH European Affiliates are selling services, including without limitation infrastructure as a service and cloud services (together the “Services”).

As part of their activities and notably the execution of the Services, OVH SAS and the OVH European Affiliates are processing personal data subjected to the Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data (the “GDPR”), notably personal data of their Clients.

Such personal data processing activities are performed by OVH SAS and the OVH European Affiliates either

(a) as controller or (b) as a processor under their Clients’ instructions.

OVH SAS and the OVH European Affiliates, at the express request of their Clients, may transfer the aforementioned processing activities to one or more data importers located in a country which is not considered by the European Commission as a third country that ensures an adequate level of protection according to article 45 of the GDPR. Such processing activities will be performed by the relevant data importer as a processor under instruction of the relevant data exporter. The performance of such processing activities implies a transfer of personal data to the data importer (including remote access from its country).

The data importer’s country is not considered by the European Commission as a third country that ensures

an adequate level of protection according to article 45 of the GDPR.

For the purposes of Articles 28 (7) and 46 (c) of the Regulation (EU) 2016/679,, the parties have agreed on the following Contractual Clauses adopted by Decision n°2021/914/EU dated 4 June 2021 of the European Commission, which integrates the clauses of Module 3 applicable to transfers from processor to processor (the “Clauses”) in order to adduce adequate safeguards with respect to the protection of privacy and fundamental rights and freedoms of individuals for the transfer by the data exporter to the data importer of the personal data specified in Appendix 1.

The following Clauses are only applicable to personal data processing activities performed by OVH SAS and the OVH European Affiliates as processor under their Clients’ instructions entrusted to the relevant data importer as a processor.

SECTION I

Clause 1

Purpose and scope

(a) The purpose of these standard contractual clauses is to ensure compliance with the requirements of

Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data (General Data Protection Regulation) for the transfer of personal data to a third country.

(b) The Parties:

(i) the legal persons (hereinafter ‘entities’) transferring the personal data, as listed in Annex I.A

(hereinafter each ‘data exporter’), and

(ii) the entities in a third country receiving the personal data from the data exporter, directly or indirectly via another entity also Party to these Clauses, as listed in Annex I.A (hereinafter each ‘data importer’)

have agreed to these standard contractual clauses (hereinafter: ‘Clauses’).

(c) These Clauses apply with respect to the transfer of personal data as specified in Annex I.B.

(d) The Appendix to these Clauses containing the Annexes referred to therein forms an integral part of these Clauses.

Clause 2

Effect and invariability of the Clauses

(a) These Clauses set out appropriate safeguards, including enforceable data subject rights and effective legal remedies, pursuant to Article 46(1) and Article 46(2)(c) of Regulation (EU) 2016/679 and, with respect to data transfers from processors to processors, standard contractual clauses pursuant to Article 28(7) of Regulation (EU) 2016/679, provided they are not modified, except to select the appropriate Module(s) or to add or update information in the Appendix. This does not prevent the Parties from including the standard contractual clauses laid down in these Clauses in a wider contract and/or to add other clauses or additional safeguards, provided that they do not contradict, directly or indirectly, these Clauses or prejudice the fundamental rights or freedoms of data subjects.

(b) These Clauses are without prejudice to obligations to which the data exporter is subject by virtue of Regulation (EU) 2016/679.

Clause 3

Third-party beneficiaries

(a) Data subjects may invoke and enforce these Clauses, as third-party beneficiaries, against the data exporter and/or data importer, with the following exceptions:

(i) Clause 1, Xxxxxx 2, Xxxxxx 3, Xxxxxx 6, Xxxxxx 7;

(ii) Xxxxxx 0.0(x), (x) xxx (x) xxx Xxxxxx 0.0(x), (x), (x), (x), (x) and (g);

(iii) Clause 9(a), (c), (d) and (e);

(iv) Clause 12(a), (d) and (f);

(v) Clause 13;

(vi) Clause 15.1(c), (d) and (e);

(vii) Clause 16(e);

(viii) Clause 18(a) and (b).

(b) Paragraph (a) is without prejudice to rights of data subjects under Regulation (EU) 2016/679.

Clause 4

Interpretation

(a) Where these Clauses use terms that are defined in Regulation (EU) 2016/679, those terms shall have the same meaning as in that Regulation.

(b) These Clauses shall be read and interpreted in the light of the provisions of Regulation (EU) 2016/679.

(c) These Clauses shall not be interpreted in a way that conflicts with rights and obligations provided for in Regulation (EU) 2016/679.

Clause 5

Hierarchy

In the event of a contradiction between these Clauses and the provisions of related agreements between the Parties, existing at the time these Clauses are agreed or entered into thereafter, these Clauses shall prevail.

Clause 6

Description of the transfers

The details of the transfers, and in particular the categories of personal data that are transferred and the purposes for which they are transferred, are specified in Annex I.B.

Clause 7

Docking clause

(a) An entity that is not a Party to these Clauses may, with the agreement of the Parties, accede to these Clauses at any time, either as a data exporter or as a data importer, by completing the Appendix and signing Annex I.A.

(b) Once it has completed the Appendix and signed Annex I.A, the acceding entity shall become a Party to these Clauses and have the rights and obligations of a data exporter or data importer in accordance with its designation in Annex I.A.

(c) The acceding entity shall have no rights or obligations arising under these Clauses from the period prior to becoming a Party.

SECTION II – OBLIGATIONS OF THE PARTIES

Clause 8

Data protection safeguards

The data exporter warrants that it has used reasonable efforts to determine that the data importer is able, through the implementation of appropriate technical and organisational measures, to satisfy its obligations under these Clauses.

8.1 Instructions

(a) The data exporter has informed the data importer that it acts as processor under the instructions of its controller(s), which the data exporter shall make available to the data importer prior to processing.

(b) The data importer shall process the personal data only on documented instructions from the controller, as communicated to the data importer by the data exporter, and any additional documented instructions from the data exporter. Such additional instructions shall not conflict with the instructions from the controller. The controller or data exporter may give further documented instructions regarding the data processing throughout the duration of the contract.

(c) The data importer shall immediately inform the data exporter if it is unable to follow those instructions. Where the data importer is unable to follow the instructions from the controller, the data exporter shall immediately notify the controller.

(d) The data exporter warrants that it has imposed the same data protection obligations on the data importer as set out in the contract or other legal act under Union or Member State law between the controller and the data exporter.

8.2 Purpose limitation

The data importer shall process the personal data only for the specific purpose(s) of the transfer, as set out in Annex I. B., unless on further instructions from the controller, as communicated to the data importer by the data exporter, or from the data exporter.

8.3 Transparency

On request, the data exporter shall make a copy of these Clauses, including the Appendix as completed by the Parties, available to the data subject free of charge. To the extent necessary to protect business secrets or other confidential information, including personal data, the data exporter may redact part of the text of the Appendix prior to sharing a copy, but shall provide a meaningful summary where the data subject would otherwise not be able to understand its content or exercise his/her rights. On request, the Parties shall provide the data subject with the reasons for the redactions, to the extent possible without revealing the redacted information.

8.4 Accuracy

If the data importer becomes aware that the personal data it has received is inaccurate, or has become outdated, it shall inform the data exporter without undue delay. In this case, the data importer shall cooperate with the data exporter to rectify or erase the data.

8.5 Duration of processing and erasure or return of data

Processing by the data importer shall only take place for the duration specified in Annex I.B. After the end of the provision of the processing services, the data importer shall, at the choice of the data exporter, delete all personal data processed on behalf of the controller and certify to the data exporter that it has done so, or return to the data exporter all personal data processed on its behalf

and delete existing copies. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit return or deletion of the personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process it to the extent and for as long as required under that local law. This is without prejudice to Clause 14, in particular the requirement for the data importer under Clause 14(e) to notify the data exporter throughout the duration of the contract if it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under Clause 14(a).

8.6 Security of processing

(a) The data importer and, during transmission, also the data exporter shall implement appropriate technical and organisational measures to ensure the security of the data, including protection against a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access to that data (hereinafter ‘personal data breach’). In assessing the appropriate level of security, they shall take due account of the state of the art, the costs of implementation, the nature, scope, context and purpose(s) of processing and the risks involved in the processing for the data subject. The Parties shall in particular consider having recourse to encryption or pseudonymisation, including during transmission, where the purpose of processing can be fulfilled in that manner. In case of pseudonymisation, the additional information for attributing the personal data to a specific data subject shall, where possible, remain under the exclusive control of the data exporter or the controller. In complying with its obligations under this paragraph, the data importer shall at least implement the technical and organisational measures specified in Annex II. The data importer shall carry out regular checks to ensure that these measures continue to provide an appropriate level of security.

(b) The data importer shall grant access to the data to members of its personnel only to the extent strictly necessary for the implementation, management and monitoring of the contract. It shall ensure that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.

(c) In the event of a personal data breach concerning personal data processed by the data importer under these Clauses, the data importer shall take appropriate measures to address the breach, including measures to mitigate its adverse effects. The data importer shall also notify, without undue delay, the data exporter and, where appropriate and feasible, the controller after having become aware of the breach. Such notification shall contain the details of a contact point where more information can be obtained, a description of the nature of the breach (including, where possible, categories and approximate number of data subjects and personal data records concerned), its likely consequences and the measures taken or proposed to address the data breach, including measures to mitigate its possible adverse effects. Where, and in so far as, it is not possible to provide all information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay.

(d) The data importer shall cooperate with and assist the data exporter to enable the data exporter to comply with its obligations under Regulation (EU) 2016/679, in particular to notify its controller so that the latter may in turn notify the competent supervisory authority and the affected data subjects, taking into account the nature of processing and the information available to the data importer.

8.7 Sensitive data

Where the transfer involves personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data, or biometric data for the purpose of

uniquely identifying a natural person, data concerning health or a person’s sex life or sexual orientation, or data relating to criminal convictions and offences (hereinafter ‘sensitive data’), the data importer shall apply the specific restrictions and/or additional safeguards set out in Annex I.B.

8.8 Onward transfers

The data importer shall only disclose the personal data to a third party on documented instructions from the controller, as communicated to the data importer by the data exporter. In addition, the data may only be disclosed to a third party located outside the European Union (in the same country as the data importer or in another third country, hereinafter ‘onward transfer’) if the third party is or agrees to be bound by these Clauses, under the appropriate Module, or if:

(i) the onward transfer is to a country benefitting from an adequacy decision pursuant to Article 45 of Regulation (EU) 2016/679 that covers the onward transfer;

(ii) the third party otherwise ensures appropriate safeguards pursuant to Articles 46 or 47 of Regulation (EU) 2016/679;

(iii) the onward transfer is necessary for the establishment, exercise or defence of legal claims in the context of specific administrative, regulatory or judicial proceedings; or

(iv) the onward transfer is necessary in order to protect the vital interests of the data subject or of another natural person.

Any onward transfer is subject to compliance by the data importer with all the other safeguards under these Clauses, in particular purpose limitation.

8.9 Documentation and compliance

(a) The data importer shall promptly and adequately deal with enquiries from the data exporter or the controller that relate to the processing under these Clauses.

(b) The Parties shall be able to demonstrate compliance with these Clauses. In particular, the data importer shall keep appropriate documentation on the processing activities carried out on behalf of the controller.

(c) The data importer shall make all information necessary to demonstrate compliance with the obligations set out in these Clauses available to the data exporter, which shall provide it to the controller.

(d) The data importer shall allow for and contribute to audits by the data exporter of the processing activities covered by these Clauses, at reasonable intervals or if there are indications of non- compliance. The same shall apply where the data exporter requests an audit on instructions of the controller. In deciding on an audit, the data exporter may take into account relevant certifications held by the data importer.

(e) Where the audit is carried out on the instructions of the controller, the data exporter shall make the results available to the controller.

(f) The data exporter may choose to conduct the audit by itself or mandate an independent auditor. Audits may include inspections at the premises or physical facilities of the data importer and shall, where appropriate, be carried out with reasonable notice.

(g) The Parties shall make the information referred to in paragraphs (b) and (c), including the results of

any audits, available to the competent supervisory authority on request.

Clause 9

Use of sub-processors

(a)

The data importer has the controller’s general authorisation for the engagement of sub-processor(s) from an agreed list. The data importer shall specifically inform the controller in writing of any intended changes to that list through the addition or replacement of sub-processors at least 90 days in advance, thereby giving the controller sufficient time to be able to object to such changes prior to the engagement of the sub-processor(s). The data importer shall provide the controller with the information necessary to enable the controller to exercise its right to object. The data importer shall inform the data exporter of the engagement of the sub-processor(s).

(b) Where the data importer engages a sub-processor to carry out specific processing activities (on behalf of the controller), it shall do so by way of a written contract that provides for, in substance, the same data protection obligations as those binding the data importer under these Clauses, including in terms of third-party beneficiary rights for data subjects. The Parties agree that, by complying with this Clause, the data importer fulfils its obligations under Clause 8.8. The data importer shall ensure that the sub-processor complies with the obligations to which the data importer is subject pursuant to these Clauses.

(c) The data importer shall provide, at the data exporter’s or controller’s request, a copy of such a sub- processor agreement and any subsequent amendments. To the extent necessary to protect business secrets or other confidential information, including personal data, the data importer may redact the text of the agreement prior to sharing a copy.

(d) The data importer shall remain fully responsible to the data exporter for the performance of the sub- processor’s obligations under its contract with the data importer. The data importer shall notify the data exporter of any failure by the sub-processor to fulfil its obligations under that contract.

(e) The data importer shall agree a third-party beneficiary clause with the sub-processor whereby – in the event the data importer has factually disappeared, ceased to exist in law or has become insolvent

– the data exporter shall have the right to terminate the sub-processor contract and to instruct the sub-processor to erase or return the personal data.

Clause 10

Data subject rights

(a) The data importer shall promptly notify the data exporter and, where appropriate, the controller of any request it has received from a data subject, without responding to that request unless it has been authorised to do so by the controller.

(b) The data importer shall assist, where appropriate in cooperation with the data exporter, the controller in fulfilling its obligations to respond to data subjects’ requests for the exercise of their rights under Regulation (EU) 2016/679 or Regulation (EU) 2018/1725, as applicable. In this regard, the Parties shall set out in Annex II the appropriate technical and organisational measures, taking into account the nature of the processing, by which the assistance shall be provided, as well as the scope and the extent of the assistance required.

(c) In fulfilling its obligations under paragraphs (a) and (b), the data importer shall comply with the instructions from the controller, as communicated by the data exporter.

Clause 11

Redress

(a) The data importer shall inform data subjects in a transparent and easily accessible format, through individual notice or on its website, of a contact point authorised to handle complaints. It shall deal promptly with any complaints it receives from a data subject.

(b) In case of a dispute between a data subject and one of the Parties as regards compliance with these Clauses, that Party shall use its best efforts to resolve the issue amicably in a timely fashion. The Parties shall keep each other informed about such disputes and, where appropriate, cooperate in resolving them.

(c) Where the data subject invokes a third-party beneficiary right pursuant to Clause 3, the data importer shall accept the decision of the data subject to:

(i) lodge a complaint with the supervisory authority in the Member State of his/her habitual residence or place of work, or the competent supervisory authority pursuant to Clause 13;

(ii) refer the dispute to the competent courts within the meaning of Clause 18.

(d) The Parties accept that the data subject may be represented by a not-for-profit body, organisation or association under the conditions set out in Article 80(1) of Regulation (EU) 2016/679.

(e) The data importer shall abide by a decision that is binding under the applicable EU or Member State law.

(f) The data importer agrees that the choice made by the data subject will not prejudice his/her substantive and procedural rights to seek remedies in accordance with applicable laws.

Clause 12

Liability

(a) Each Party shall be liable to the other Parties for any damages it causes the other Parties by any breach of these Clauses.

(b) The data importer shall be liable to the data subject, and the data subject shall be entitled to receive compensation, for any material or non-material damages the data importer or its sub-processor causes the data subject by breaching the third-party beneficiary rights under these Clauses.

(c) Notwithstanding paragraph (b), the data exporter shall be liable to the data subject, and the data subject shall be entitled to receive compensation, for any material or non-material damages the data exporter or the data importer (or its sub- processor) causes the data subject by breaching the third- party beneficiary rights under these Clauses. This is without prejudice to the liability of the data

exporter and, where the data exporter is a processor acting on behalf of a controller, to the liability of the controller under Regulation (EU) 2016/679 or Regulation (EU) 2018/1725, as applicable.

(d) The Parties agree that if the data exporter is held liable under paragraph (c) for damages caused by the data importer (or its sub-processor), it shall be entitled to claim back from the data importer that part of the compensation corresponding to the data importer’s responsibility for the damage.

(e) Where more than one Party is responsible for any damage caused to the data subject as a result of a breach of these Clauses, all responsible Parties shall be jointly and severally liable and the data subject is entitled to bring an action in court against any of these Parties.

(f) The Parties agree that if one Party is held liable under paragraph (e), it shall be entitled to claim back from the other Party/ies that part of the compensation corresponding to its/their responsibility for the damage.

(g) The data importer may not invoke the conduct of a sub-processor to avoid its own liability.

Clause 13

Supervision

(a) The supervisory authority with responsibility for ensuring compliance by the data exporter with Regulation (EU) 2016/679 as regards the data transfer, as indicated in Annex I.C, shall act as competent supervisory authority.

(b) The data importer agrees to submit itself to the jurisdiction of and cooperate with the competent supervisory authority in any procedures aimed at ensuring compliance with these Clauses. In particular, the data importer agrees to respond to enquiries, submit to audits and comply with the measures adopted by the supervisory authority, including remedial and compensatory measures. It shall provide the supervisory authority with written confirmation that the necessary actions have been taken.

SECTION III – LOCAL LAWS AND OBLIGATIONS IN CASE OF ACCESS BY PUBLIC AUTHORITIES

Clause 14

Local laws and practices affecting compliance with the Clauses

(a) The Parties warrant that they have no reason to believe that the laws and practices in the third country of destination applicable to the processing of the personal data by the data importer, including any requirements to disclose personal data or measures authorising access by public authorities, prevent the data importer from fulfilling its obligations under these Clauses. This is based on the understanding that laws and practices that respect the essence of the fundamental rights and freedoms and do not exceed what is necessary and proportionate in a democratic society to safeguard one of the objectives listed in Article 23(1) of Regulation (EU) 2016/679, are not in contradiction with these Clauses.

(b) The Parties declare that in providing the warranty in paragraph (a), they have taken due account in particular of the following elements:

(i) the specific circumstances of the transfer, including the length of the processing chain, the number of actors involved and the transmission channels used; intended onward transfers; the type of recipient; the purpose of processing; the categories and format of the transferred personal data; the economic sector in which the transfer occurs; the storage location of the data transferred;

(ii) the laws and practices of the third country of destination– including those requiring the disclosure of data to public authorities or authorising access by such authorities – relevant in light of the specific circumstances of the transfer, and the applicable limitations and safeguards;

(iii) any relevant contractual, technical or organisational safeguards put in place to supplement the safeguards under these Clauses, including measures applied during transmission and to the processing of the personal data in the country of destination.

(c) The data importer warrants that, in carrying out the assessment under paragraph (b), it has made its best efforts to provide the data exporter with relevant information and agrees that it will continue to cooperate with the data exporter in ensuring compliance with these Clauses.

(d) The Parties agree to document the assessment under paragraph (b) and make it available to the competent supervisory authority on request.

(e) The data importer agrees to notify the data exporter promptly if, after having agreed to these Clauses and for the duration of the contract, it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under paragraph (a), including following a change in the laws of the third country or a measure (such as a disclosure request) indicating an application of such laws in practice that is not in line with the requirements in paragraph (a). The data exporter shall forward the notification to the controller.

(f) Following a notification pursuant to paragraph (e), or if the data exporter otherwise has reason to believe that the data importer can no longer fulfil its obligations under these Clauses, the data exporter shall promptly identify appropriate measures (e.g. technical or organisational measures to ensure security and confidentiality) to be adopted by the data exporter and/or data importer to address the situation, if appropriate in consultation with the controller. The data exporter shall suspend the data transfer if it considers that no appropriate safeguards for such transfer can be ensured, or if instructed by the controller or the competent supervisory authority to do so. In this case, the data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses. If the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise. Where the contract is terminated pursuant to this Clause, Clause 16(d) and (e) shall apply.

Clause 15

Obligations of the data importer in case of access by public authorities

15.1 Notification

(a) The data importer agrees to notify the data exporter and, where possible, the data subject promptly (if necessary with the help of the data exporter) if it:

(i) receives a legally binding request from a public authority, including judicial authorities, under the laws of the country of destination for the disclosure of personal data transferred pursuant to these Clauses; such notification shall include information about the personal data requested, the requesting authority, the legal basis for the request and the response provided; or

(ii) becomes aware of any direct access by public authorities to personal data transferred pursuant to these Clauses in accordance with the laws of the country of destination; such notification shall include all information available to the importer.

The data exporter shall forward the notification to the controller.

(b) If the data importer is prohibited from notifying the data exporter and/or the data subject under the laws of the country of destination, the data importer agrees to use its best efforts to obtain a waiver of the prohibition, with a view to communicating as much information as possible, as soon as possible. The data importer agrees to document its best efforts in order to be able to demonstrate them on request of the data exporter.

(c) Where permissible under the laws of the country of destination, the data importer agrees to provide the data exporter, at regular intervals for the duration of the contract, with as much relevant information as possible on the requests received (in particular, number of requests, type of data requested, requesting authority/ies, whether requests have been challenged and the outcome of such challenges, etc.). The data exporter shall forward the information to the controller.

(d) The data importer agrees to preserve the information pursuant to paragraphs (a) to (c) for the duration of the contract and make it available to the competent supervisory authority on request.

(e) Paragraphs (a) to (c) are without prejudice to the obligation of the data importer pursuant to Clause 14(e) and Clause 16 to inform the data exporter promptly where it is unable to comply with these Clauses.

15.2 Review of legality and data minimisation

(a) The data importer agrees to review the legality of the request for disclosure, in particular whether it remains within the powers granted to the requesting public authority, and to challenge the request if, after careful assessment, it concludes that there are reasonable grounds to consider that the request is unlawful under the laws of the country of destination, applicable obligations under international law and principles of international comity. The data importer shall, under the same conditions, pursue possibilities of appeal. When challenging a request, the data importer shall seek interim measures with a view to suspending the effects of the request until the competent judicial authority has decided on its merits. It shall not disclose the personal data requested until required to do so under the applicable procedural rules. These requirements are without prejudice to the obligations of the data importer under Clause 14(e).

(b) The data importer agrees to document its legal assessment and any challenge to the request for disclosure and, to the extent permissible under the laws of the country of destination, make the documentation available to the data exporter. It shall also make it available to the competent supervisory authority on request. The data exporter shall make the assessment available to the controller.

(c) The data importer agrees to provide the minimum amount of information permissible when responding to a request for disclosure, based on a reasonable interpretation of the request.

SECTION IV – FINAL PROVISIONS

Clause 16

Non-compliance with the Clauses and termination

(a) The data importer shall promptly inform the data exporter if it is unable to comply with these Clauses, for whatever reason.

(b) In the event that the data importer is in breach of these Clauses or unable to comply with these Clauses, the data exporter shall suspend the transfer of personal data to the data importer until compliance is again ensured or the contract is terminated. This is without prejudice to Clause 14(f).

(c) The data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses, where:

(i) the data exporter has suspended the transfer of personal data to the data importer pursuant to paragraph (b) and compliance with these Clauses is not restored within a reasonable time and in any event within one month of suspension;

(ii) the data importer is in substantial or persistent breach of these Clauses; or

(iii) the data importer fails to comply with a binding decision of a competent court or supervisory authority regarding its obligations under these Clauses.

In these cases, it shall inform the competent supervisory authority and the controller of such non- compliance. Where the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise.

(d) Personal data that has been transferred prior to the termination of the contract pursuant to paragraph (c) shall at the choice of the data exporter immediately be returned to the data exporter or deleted in its entirety. The same shall apply to any copies of the data. The data importer shall certify the deletion of the data to the data exporter. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit the return or deletion of the transferred personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process the data to the extent and for as long as required under that local law.

(e) Either Party may revoke its agreement to be bound by these Clauses where (i) the European Commission adopts a decision pursuant to Article 45(3) of Regulation (EU) 2016/679 that covers the transfer of personal data to which these Clauses apply; or (ii) Regulation (EU) 2016/679 becomes part of the legal framework of the country to which the personal data is transferred. This is without prejudice to other obligations applying to the processing in question under Regulation (EU) 2016/679.

Clause 17

Governing law

These Clauses shall be governed by the law of the EU Member State in which the data exporter is established. Where such law does not allow for third-party beneficiary rights, they shall be governed by the law of another EU Member State that does allow for third-party beneficiary rights. The Parties agree that this shall be the law of France.

Clause 18

Choice of forum and jurisdiction

(a) Any dispute arising from these Clauses shall be resolved by the courts of an EU Member State.

(b) THE PARTIES AGREE THAT THOSE SHALL BE THE COURTS OF FRANCE.

(c) A data subject may also bring legal proceedings against the data exporter and/or data importer before the courts of the Member State in which he/she has his/her habitual residence.

(d) The Parties agree to submit themselves to the jurisdiction of such courts.

ANNEX I

A. LIST OF PARTIES Data exporter (processor)

OVH SAS

Company incorporated under French Law whose registered office is located at 0 xxx Xxxxxxxxxx 00000 Xxxxxxx (Xxxxxx),

OVH Hispano

Company incorporated under Spanish law whose registered office is located et X/ Xxxxxx 00, 0x xxxxxx, 00000 Xxxxxx (Xxxxx),

OVH SRL

Company incorporated under Italian law whose registered office is located et Xxx Xxxxx Xxxxxxxx 00, XXX 00000 Xxxxxx (Xxxxx),

OVH GmbH

Company incorporated under German law whose registered office is located at Xxxxxxxxxxxxxxx 00, 00000 Xxxx (Xxxxxxx),

OVH Hosting Limited

Company incorporated under Irish law whose registered office is located at 00/00 Xxxxxxxxxxx Xxxxxx Xxxx Xxxxxx 0 X00 XX00 (Xxxxxxx),

OVH Sp. Zo.o.

Company incorporated under Polish law whose registered office is located at xx. Xxxxxxxx 0, 00-000

Xxxxxxx (Xxxxxx),

OVH Hosting Sistemas informaticos unipessoal

Company incorporated under Portuguese law whose registered office is located at Xxxxx xx Xxxxxxxx, xx 0, 0x xxx 0000 000 Xxxxxx (Xxxxxxxx),

OVH BV

Company incorporated under Dutch law whose registered office is located at Xxxxxxxxxx 00, 0000 XX Xxxxxxxxx-Xxxxxxxx, (Xxxxxxxxxxx),

OVH SAS and OVH European Affiliates contact point for standard contractual clauses : OVH - Data Protection Officer - 0 xxx Xxxxxxxxx 00000 Xxxxxxx Xxxxxx

Activities relevant to the data transferred under these Clauses:

Computing, storage and/or any such other Services as described in the agreement concluded with the Clients.

Data importer (processor)

OVH Singapore PTE Ltd, Company incorporated under Singaporean law whose registered office is located 000 Xxxxx xxxxxx #00-00, Xxxxxxxxxx airlines building, 069536 (Singapore). Activities relevant to the data transferred under these Clauses: Computing, storage and/or any such other Services (i) hosted in Datacenter(s) located in Asia-Pacific area or (ii) for which the applicable Specific Terms and Conditions provide these OVH Affiliates may participate to carry out such Services	Altimat Data Center Singapore PTE. Ltd, Company incorporated under Singaporean law whose registered office is located 000 Xxxxx xxxxxx #00-00, Xxxxxxxxxx airlines building, 069536 (Singapore) Activities relevant to the data transferred under these Clauses: Computing, storage and/or any such other Services (i) hosted in Datacenter(s) located in Asia-Pacific area or (ii) for which the applicable Specific Terms and Conditions provide these OVH Affiliates may participate to carry out such Services
OVH Australia PTY Ltd, Company incorporated under Australian law whose registered office is located Xxxxx 00 - 00 Xxxxxx Xxxxxx, Xxxxx Xxxxxx XXX 0000, registered under company number 612612754. (Australia) Activities relevant to the data transferred under these Clauses: Computing, storage and/or any such other Services (i) hosted in Datacenter(s) located in Asia-Pacific area or (ii) for which the applicable Specific Terms and Conditions provide these OVH Affiliates may participate to carry out such Services	Data Center Sydney PTY Ltd, Company incorporated under Australian law whose registered office is located Xxxxx 00 - 00 Xxxxxx Xxxxxx, Xxxxx Xxxxxx XXX 0000 (Australia). Activities relevant to the data transferred under these Clauses: Computing, storage and/or any such other Services (i) hosted in Datacenter(s) located in Asia-Pacific area or (ii) for which the applicable Specific Terms and Conditions provide these OVH Affiliates may participate to carry out such Services
Contact point for Singapore and Australia entities: OVH Singapore XXX Xxx, 000 Xxxxx xxxxxx #00-00, Xxxxxxxxxx airlines building, 069536 (Singapore).
OVH Tech R&D Private Limited, Company incorporated under Indian law, whose registered office is located at Salapuria Symbiosis, Xxxxx Xxxxxxx, Xxxxx Xxxxx, Xxxxxxxxxxxx Xxxx, Xxxxxxxxx, Xxxxxxxxx, 000000 Xxxxx Contact point: Xxxxxxxxx Xxxxxxxxx, Xxxxx Xxxxxxx, Xxxxx Xxxxx, Xxxxxxxxxxxx Xxxx, Xxxxxxxxx, Xxxxxxxxx, 000000 Xxxxx Activities relevant to the data transferred under these Clauses: Computing, storage and/or any such other Services (i) hosted in Datacenter(s) located in Asia-Pacific area or (ii) for which the applicable Specific Terms and Conditions provide these OVH Affiliates may participate to carry out such Services	Altimat Data Center India Private Limited, Company incorporated under Indian law, whose registered office is located at H No. 215, A102 1st Floor A Wing, Narpoli, Golden Park, Rallway Stn Road, Anjur Phata, Bhiwandi, Thana, Xxxxxxxxxxx, Xxxxx, 000000 Contact point: Xxxxxxxxx Xxxxxxxxx, Xxxxx Xxxxxxx, Xxxxx Xxxxx, Xxxxxxxxxxxx Xxxx, Xxxxxxxxx, Xxxxxxxxx, 000000 Xxxxx Activities relevant to the data transferred under these Clauses: Computing, storage and/or any such other Services (i) hosted in Datacenter(s) located in Asia-Pacific area or (ii) for which the applicable Specific Terms and Conditions provide these OVH Affiliates may participate to carry out such Services

B. DESCRIPTION OF TRANSFER

Categories of data subjects whose personal data is transferred

The categories of data subjects are determined and controlled by the Clients, at their sole discretion.

Categories of personal data transferred

Personal data used by the Clients within the Services including but not limited to any personal data stored by the Clients on, and/or computed by the Clients using, OVH SAS’ and OVH European Affiliates’ infrastructures. The categories of such personal data are determined and controlled by the Clients, at their sole discretion.

Sensitive data transferred (if applicable) and applied restrictions or safeguards that fully take into consideration the nature of the data and the risks involved, such as for instance strict purpose limitation, access restrictions (including access only for staff having followed specialised training), keeping a record of access to the data, restrictions for onward transfers or additional security measures.

The categories of such personal data are determined and controlled by the Client, at its sole discretion. The frequency of the transfer (e.g. whether the data is transferred on a one-off or continuous basis). The frequency of the transfer is determined by the Clients, at their sole discretion.

Nature of the processing

The nature of processing activities carried out by the data importer on personal data may be computing, storage and/or any such other Services as provided in the agreement in force between OVH SAS or the OVH European Affiliates and the respective Client.

Purposes of the data transfer and further processing

Process the personal data to the extent necessary to provide the Services.

The period for which the personal data will be retained, or, if that is not possible, the criteria used to determine that period

The processing activities are performed for the duration provided in the Agreement

For transfers to (sub-) processors, also specify subject matter, nature and duration of the processing

When processors external to the OVH Group are involved in the processing of personal data carried out, this is mentioned in the terms and conditions applicable to the services concerned.

C. COMPETENT SUPERVISORY AUTHORITY

Identify the competent supervisory authority in accordance with Clause 13

France - Commission Nationale de l'Informatique et des Libertés - CNIL

8 rue Vivienne, CS 30223 F-75002 Paris, Cedex 02

Tel. x00 0 00 00 00 00

Spain - Agencia de Protección de Datos

C/Xxxxx Xxxx, 6 00000 Xxxxxx

Tel. x00 00000 0000 • e-mail: xxxxxxxxxxxxx@xxxx.xx

Portugal - Comissão Nacional de Protecção de Dados - CNPD

X. xx Xxx. Xxxxx, 000-0x 0000-000 Xxxxxx

Xxx. x000 00 000 00 00 • e-mail: xxxxx@xxxx.xx

Italy - Garante per la protezione dei dati personali

Xxxxxx xx Xxxxx Xxxxxxx, 000 00000 Xxxx

Tel. x00 00 00000 0 • e-mail: xxxxxxx@xxxxxxxxxxxxxx.xx

Germany - Die Bundesbeauftragte für den Datenschutz und die Informationsfreiheit

Xxxxxxxxxxxxx 00 - 00000 Xxxx

Tel. x00 000 000000 0 • e-mail: xxxxxxxxxx@xxxx.xxxx.xx

Netherlands - Autoriteit Persoonsgegevens

Prins Clauslaan 60 P.O. Box 93374 0000 XX Xxx Xxxx/Xxx Xxxxx Tel. x00 00 000 0000 • e-mail: xxxx@xxxxxxxxxxxxxxxxxxxxxxxxxx.xx

ANNEX II

TECHNICAL AND ORGANISATIONAL MEASURES INCLUDING TECHNICAL AND ORGANISATIONAL MEASURES TO ENSURE THE SECURITY OF THE DATA

The applicable security principles and rules are defined by the security team in partnership with OVHcloud top management. The security team, under the responsibility of the CISO, is itself composed of 4 teams:

The xxxxxxxx.xxxxx team in charge of developing the security tool used within OVHcloud. This team designs and operates the tools to support certain security measures deployed on all OVHcloud information systems. These tools include the management of the identities and accesses of employees and service providers, authentication mechanisms made available to clients, identification of vulnerabilities on systems and security monitoring. This team also assists other business teams in the design and deployment of architectures by ensuring security from the definition phase onwards.

The security.operations team is responsible for supporting teams in the implementation of good security practices within operations, the implementation of formal security management processes, the support in the integration of security tools and the alignment of security devices within OVHcloud. The security.ops team puts in place an internal control system, both organizational and technical on security and assists the product teams in the implementation of formal information security management systems and in their certification.

The security.cert team is responsible for monitoring threat sources, identifying attack tools and methods to anticipate them, and managing malicious security incidents. This team manages the OVHcloud CSIRT and exchanges with international expert communities to provide the best sources of information to anticipate attacks.

The security.customer team is in charge of adapting the products offered by OVHcloud to the specific needs of specific business sectors (healthcare, finance, etc.). The team values the expectations of these business sectors, and coordinates OVHcloud’s response to contractual and standard compliance. It also provides level 3 support for customer questions about compliance and information security.

The security team is accompanied by the physical security management teams and the privacy teams. These three teams work together to ensure optimal effectiveness of actions on these subjects with strong adherence.

In addition, security referees are deployed within OVHcloud teams. These focal points enable the dissemination of good practices within teams, provide an identified point of contact for incident and crisis management, and enable the gathering of information from operations to the security team.

A security committee led by the CISO and the managers of the security team ensures communication with the Executive Committee (ComEx) of OVHcloud. This semi-annual committee presents the main threats under surveillance, the major risks, the monitoring metrics, the progress of the ongoing actions and the updated roadmap. This committee also ensures that the ISSP is aligned with OVHcloud's strategic and operational objectives.

Security compliance management

The ISMS aims to ensure that the security requirements of the various interested parties of OVHcloud are taken into account. These requirements are of different kinds:

• legal or regulatory requirements

• contractual commitments

• good practices on which OVHcloud is committed explicitly

OVHcloud must identified and consolidate those requirements and implement the management system in support for the compliance to these requirements.

Documentation

OVHcloud must deploy a formal documented management system to :

• provide a comprehensive framework for policy rules, guideline, operational documentation, records and indicators

• ensure formalism and follow-up of activities implemented to reduce risks

• demonstrate compliance with applicable legal, regulatory or contractual requirements

• demonstrate compliance with the rules set out in the detailed security policies

Assets management

OVHcloud must deploy a formal approach for managing assets carrying security risks or in support for security management to ensure appropriate security controls over them:

• Maintain accurate inventories of those assets

• Define and maintain ownership for those assets

• Classification of those assets based on appropriate criteria to support security decision

• Definition of security rules adapted to their criticality

Security risks management

OVHcloud must deploy a risk management approach to structure operational decisions affecting security. This risk management approach is based on the principles of ISO/IEC 31000 and ISO/IEC 27005 standards. It is based on:

• In-depth knowledge of systems through asset cartography, asset classifications and valuations from a security perspective

• Ongoing analysis of feared events, vulnerabilities, and the threat environment

• uniform formalization of security risks to make them explicit to technical experts and decision- makers for reasonable and informed decision-making

• follow-up of decisions and action plans following the identification of a risk

The establishment of formal risk management enables the operational specificity of a project or product to be taken into account and the achievement of specific security objectives. Failure to comply with a ISSP rule results in an analysis of the risks resulting from the introduction of compensatory security measures to achieve at least an equivalent level of safety or acceptance of risk.

Privacy

The legislation applicable to the protection of personal data and our privacy policy constitute the framework for the processing of this data that OVHcloud applies. ISMS complements this framework by consistently defining, implementing, and improving security arrangements that ensure the protection of hosted personal data.

This commitment is reflected in particular in:

• The implementation of a Personal Information Management System (PIMS) integrated with ISMS

• Setting up a joint management instance between the security and privacy teams

• Alignment of security and data usage policies

• Integrating security measures within ISMS into contractual commitments on personal information protection with customers

• The privacy team's participation in ISMS management

• Involvement of the security team in efforts to identify privacy risks

• Joint participation in resolving security incidents that impact personal information

• Joint definition of security objectives and measures to be implemented in the context of projects.

Customer Protection

OVH implements means of protection on the tools made available to these customers as well as on the communication channels between them and OVHcloud such as: :

• Customer interfaces through the use of identification factors ;

• Tools of detection and alerting when customer credentials are used for illegitimate purpose;

• Protection of customer infrastructures and services against external threats

• data related to customer managed by OVHcloud

Moreover, OVHcloud protects its communications with customers with adequate means according to the context like encrypted channels, collaborative tools with access and security controls or any other means defined with customers.

Customer trust

OVHcloud must provide the adequate transparency to customer in order the assist them in defining the right product for their needs. In particular, OVHcloud must provide information about :

• Physical location of the data and workloads hosting

• Physical location of the control plane and administrators

• Physical location of the support teams

• Applicable law for the service contract

• Supply chain and technical dependencies (Hardware, Software, Subcontractors)

• Reversibility capabilities information

• Certification and assurance mechanisms in place

Customer in cloud security

OVHcloud must produce a clear definition of responsibilities between OVHcloud and customer:

• Assets ownership

• Operations responsibility

• Security risk ownership

• Recommendation of security controls to implement by customer with OVHcloud included features and configuration

• Recommendation of security controls to implement by customer with optional features or external means when relevant

Security Ecosystem

OVHcloud must maintain close relationship with security communities to improve the quality of risk mitigation and accelerate response time to security threats. Security communities are covering but not limited to :

• Security experts, internally and externally

• Security team from hardware manufacturers

• Security team of software editors

• Open source groups

• Security software editors

• Security professional services providers

External technical reputation

OVHcloud must implement a set of processes to ensure the technical reputation of all systems exposed on public networks, since OVHcloud customers are relying on OVHcloud assets for their own information system. This covers:

• IP reputation to ensure that IP allocated to a customer infrastructure are usable for all legitimate purposes

• Abuse process to handle the dispute process when customer infrastructures are used for malicious activities

• Anti-fraud process to ensure all infrastructure usage is legitimate

• Anti-hack process to take down customer compromised infrastructures

• Spam, phishing, malware and dDoS detection and mitigation to protect the public from threats that might be hosted on OVHcloud infrastructure

• Protection and management of all assets under OVHcloud responsibility connected to public networks

Information system user

OVHcloud must protect information and systems by ensuring the information system is adequately operated:

• users are aware of the rules applicable to IS usage

• Company owned device management

• Employee owned device management

• Access to IS from external devices

• Collaborative tools

• Workstation security

• Mobile devices

Human resources

OVHcloud must integrate security topic into HR processes to ensure adapted resources are available to meet security objectives. This includes:

• security investments and human resources related to security priorities

• development of roadmaps of other OVHcloud teams to integrate security needs (investment and human resources)

• skills and training requirements for teams and inclusion in the training plan

• identifying gaps between needs and available resources for the adaptation of roadmaps and taking into account in risk management.

OVHcloud must educate employees on security as soon as they are integrated and throughout their presence in OVHcloud. This awareness is realized by:

• IT policy document to define the rules of usage of information system

• On boarding awareness session for all employees

• Formal threat presentation sessions targeting OVHcloud and security features in place

• Regular communications on good practices and risks

• Communications focused on a specific threat, related to current events or our detection activities

• Tests of the reflexes and the reaction capabilities of the collaborators

• Sharing information resources and feedback on cloud threats and vulnerabilities OVHcloud must manage security in the complete employee life-cycle:

• Background check fitted to position criticality

• On boarding management including contractual commitment and awareness management

• Specific security training depending of position criticality

• Regular awareness session

• Disciplinary process for security violation

• Termination of contract management

Identity and access management

OVHcloud must maintain a strict policy of logical access rights management for employees :

• all employees use nominative user accounts to access any system

• generic and anonymous accounts is prohibited for any human access

• authorizations are issued and monitored by managers, following the principle of least privilege and the principle of gradually gaining trust

• to the greatest extent possible, all authorizations should be based on roles rather than unit rights

• a formal, fully auditable process is in place for account creation, modification, deletion and password change

• connection sessions systematically have an expiry period suited to each application

• user accounts are automatically deactivated if the password is not renewed after 90 days

• password complexity is mandatory based on best practices and recommendations from authorities:

o users use automatic password generators rather than choosing their own passwords

o Complexity rules are defined and communicated to all employees, and when possible technically enforced on systems

o passwords must be renewed regularly, with a maximum of 90 days

• storing passwords in unencrypted files, on paper or in web browsers is prohibited OVHcloud must maintain a strict policy of for managing administrator access rights for platforms :

• all administrator access to live systems is realized via a bastion host

• administrators connect to the bastion hosts via SSH, using individual and nominative pairs of public and private keys

• connection to the target system is realized either via a shared service account or via a nominative account and bastion hosts; using default accounts on systems and equipment is prohibited;

• dual-factor authentication is mandatory for remote administrator access and for any employees accessing sensitive areas of the system, with such access being fully traced

• administrators have an account exclusively devoted to administration tasks, in addition to their standard user account;

• authorizations are granted and monitored by managers, in accordance with the principle of least privilege

• SSH keys are protected by a password that meets the requirements of the password policy

Cryptography

• Use strong cryptography to secure data at rest and in transit and administration operations.

o Manage cryptographic assets with automated process

o Monitor certificates and keys to ensure all systems have valid certificates at all time

Physical security

OVHcloud physical security is based on zoning. Each area within OVHcloud premises is categorized in a zone type dependent from the area usage and the sensitivity of operations and assets hosted. At each zone type, according to it's sensitivity is defined security controls on:

• Environmental protection against fire, flood, weather conditions our any applicable environmental hazard related to premises location

o Monitoring of any malicious or accidental events with automated (CCTV, sensors) or human (security watch)

o Zone control, with a formal definition of all zones interfaces and gateway

o Access control to ensure only authorized people access each zone for legitimate purpose

Supply Chain

OVHcloud’s product teams rely mainly on other OVHcloud teams, but also on partners, subcontractors and suppliers to manage operations, and to compose products and services delivered to customers. The match between the outsourced activities and OVHcloud’s security commitment must be managed:

• Identify dependencies between OVHcloud teams and subcontractors, suppliers and partners

o Classification of criticality dependencies

o Risk analysis and risk reduction where necessary

o Service level cascade and security commitments

o Integrating security into projects

o Security insurance plan for subcontractors

Architecture

OVHcloud must ensure that cloud architecture is designed to be and stay secure taking into account the complexity of information system required to deliver the service, the factorization of information systems assets to optimize ressources and the management of several generations of technologies. We rely on several pillars to achieve this objective:

• Strong segregation of systems by criticality

• Mutualization of security primitives under the management of security team

• Harmonization of management of specific security assets and processes under common management rules

• Strong automation for security deployment

OVHcloud security team maintain a list of basic security architecture guidelines for systems. Architecture principles must be defined and documented for each type of infrastructure internally. OVHcloud uses several classification scheme for IT architecture depending of needs.

Exemples of classification:

• Tiers 0, Tiers 1, Tiers 2 for internal IS, depending of the internal usage

• Mutualized control plane

• Product dedicated control plane

• Customer infrastructure (Data plane)

Classification scheme must be used to define the set of security controls to apply according to the threat environment relevant to the classification characteristics.

Configuration and hardening

• Use OS patterns with system exposure minimization and baseline of security tools

• Use hardened kernels

• Follow best practices for configuration

• Deploy system as code with automated deployment tools

• Regularly review configurations for security

Administration

OVHcloud maintain those rules for administration activities:

• all administrator access to live systems is realized via a bastion host

• administrators connect to the bastion hosts via SSH, using individual and nominative pairs of public and private keys

• connection to the target system is realized either via a shared service account or via a nominative account and bastion hosts; using default accounts on systems and equipment is prohibited

• dual-factor authentication is mandatory for remote administrator access and for any employees accessing sensitive areas of the system, with such access being fully traced

• administrators have an account exclusively devoted to administration tasks, in addition to their standard user account

• authorizations are granted and monitored by managers, in accordance with the principle of least privilege and the principle of gaining trust

• SSH keys are protected by a password that meets the requirements of the password policy; access rights are reviewed on a regular basis, in collaboration with the departments concerned

Vulnerability and patch management

OVHcloud must ensure a systematic deployment of available security patches within a time frame defined by system based on its criticality. Vulnerabilities on systems must be identified and evaluated as soon as the associated patch is available. The application of the patch outside the predefined time limit must be justified on the basis of the level of risk associated with the corrected vulnerability or the existence of compensatory controls reducing the risk to an acceptable level.

• System owners are responsible of vulnerabilities management of their systems

• Assets shall be classified in terms of criticality

• Patch deployment is based on asset criticality and prioritization of patch deployment is based on risk level

• Vulnerability mitigation can be achieve without patch deployment, in that case, a complete analysis of the situation must be performed

OVHcloud must complete this process by a threat intelligence process and vulnerabilities monitoring to ensure all vulnerabilities that could put systems at risk are mitigated.

Monitoring and detection

OVHcloud must log all records necessary to understand any security events:

• logs are backed up and not limited to local storage

• logs are consulted and analyzed by a limited number of authorized personnel, in accordance with the authorization and access management policy

• tasks are divided up between the teams responsible for operating the monitoring infrastructure and the teams responsible for operating the service

The list of activities that are logged includes the following:

• logs of storage servers hosting customer data;

• logs of the machines managing the customer’s infrastructure;

• logs of the machines monitoring the infrastructures;

• logs of the antivirus software installed on all equipped machines;

• integrity checks of logs and systems, where appropriate;

• tasks and events carried out by the customer on their infrastructure;

• network intrusion detection logs and alerts, if appropriate;

• logs of network equipment;

• logs of the infrastructure of the surveillance cameras;

• logs of administrator machines;

• logs of time servers;

• logs of badge readers;

• logs of bastion hosts.

OVHcloud implement tools and process to ensure:

• Fast detection of security events to minimize the occurrence of incidents and minimize impacts

• Adapted capabilities to investigate in post mortem

Change management

OVHcloud must maintain a formal change management principles including security :

• roles and responsibilities in security are clearly defined

• All changes are documented in tracking tool

• criteria for classification are set out in order to identify the security analysis to follow

• the risks associated with the changes are analyzed (if a risk is identified, the security manager and risk manager work together to validate the change)

• intrusion tests may be carried out (where applicable); the change is planned and scheduled with the customers (where applicable)

• the change is rolled out gradually (1/10/100/1000) and, if there is a risk, a rollback procedure is planned

• a retrospective review of the change is carried out

Each unit within OVHcloud implement its own change management procedure according to this principles.

Project management

OVHcloud integrates security within evolution and transformation projects. Compliance with ISSP and data protection is a general requirement for all OVHcloud activities. The security team assists OVHcloud project teams in the full lifecycle of all projects to ensure that the security means are adequate and properly implemented. This support consists of:

• Determine the security criticality of the data and processes involved in the project

o Accompany project managers in the definition of technical and functional architecture

o Support project teams in integration into the OVHcloud IS

o Ensure compliance with the security base in the context of the project and the specific security measures to be put in place

o Assist sponsors and project leaders in arbitrating specific measures against financial and operational constraints

o Evaluate the security level of the project before production phase and after go-live

o Identify residual risks and monitor them over time

Incident management

OVHcloud deploys a unified approach to security incident management by putting in place the organizational and technical means to:

• Detect and consolidate events that can impact the security of information systems and services

o Correlate events that indicate a possible breach of information security and trigger incident handling as soon as possible

o Mobilize experts and decision-makers in charge of resolving the incident

o Support the incident with the following objectives

▪ Reduce operational impacts

▪ Preserve evidences to support possible judicialization or internal sanctions

▪ Return to nominal situation

o Inform interested parties in accordance with legal and contractual obligations

o Identify root causes, update risk analysis, and define potential action plans to reduce the risk of a new occurrence

Network security

OVHcloud is managing a worldwide backbone to connect all infrastructures hosted in the datacenters and local networking to ensure the appropriate functioning and administration of the systems. The network security relies on:

• segmentation and segregation of network zones

• all networks equipment's are administered via a bastion host, applying the principle of least privilege

• access to the administration interfaces and administrator features for equipment is reserved to staff listed on control lists

• Network device inventory and automatized management

• Management of traffic and reaction to specific events

• Configuration of networks devices in terms of networking rules and access control

o Administration of network based on automation. Configurations are deployed automatically, based on validated templates

o Devices configuration are managed in a central configuration repository

o A process is in place for ensuring changes are controlled

• the logs are collected, centralized and monitored on a permanent basis by the network operations team

Continuity

Continuity management relies on all mechanisms to ensure Availability, Rescue and Recovery.

Systems criticality must be defined to determine acceptable Recovery Point Objective (RPO) and Recovery Time Objective (RTO).

System owners must implement controls to ensure the effectiveness ot continuity mechanisms.

Internal controls

First-level internal controls are deployed by the operational teams and the security team. These monitoring activities are mainly carried out in the form of:

• automated systems monitoring mechanisms

• operational checkpoints integrated into processes to ensure team coordination, risk accounting, and possible validations of risky activities. Where possible, these control points are integrated into the tools.

• ad hoc operational controls by security experts

Second-level internal control is carried out by the security teams to ensure the effectiveness of the first- level controls. These activities are formal. The effectiveness of ISMS is also monitored in the context of steering activities.

Internal audits

OVHcloud relies on internal audit approaches to assess the effectiveness of internal control activities. These audits are performed by teams independent of audited operations and systems. Internal audit approaches include:

• Organizational and technical audit of the rules defined within ISSP

• Technical audit of architecture review, deployment, project

• Source code audit

• Intrusion tests

These steps are carried out by OVHcloud personnel or external contractors.

OVHcloud is implementing a public Bug Bounty program that will enable the permanent testing of our systems exposed on the internet.

These activities help identify vulnerabilities, non-conformities and opportunities for improvement and fuel the process of continuous improvement of security.

External audits

OVHcloud implements an external audit program on certified perimeters. We rely on:

• general security framework: XXX 00000, XXXXX TSP (SOC)

• Cloud Provider-specific security framework: ISO 27017, CISPE, CSA CCM

• repositories dedicated to specific issues such as privacy: CISPE, ISO 27018, ISO 27701

• industry or geographical specific security framework: PCI DSS, HDS, PSEE, SecNumCloud, AGID, ENS, C5

For each framework, we determine the most appropriate certification or audit organization to strengthen our clients' confidence in our ability to meet the requirements that meet their expectations.

Audits by customers and authorities

OVHcloud allows its customers, under certain conditions, to perform security audits on systems. Such audits may be:

• Technical, performed remotely (Intrusion Test, Vulnerability Scan) without OVHcloud teams intervention

• Organizational and technical in asynchronous way through questionnaires and written exchanges with OVHcloud

• On-site organizational and technical, including installation visits, interviews with operational staff, and access to documentation and configurations.

As with internal and external audits, these evaluations provide input to the security continuous improvement.

Continuous improvement

OVHcloud is implementing a continuous improvement of security and management processes. Opportunities for improvement are identified by:

• Internal control activities

• Internal and external audits

• Security Incident Analysis

• Identification of security risks

• Stakeholders involved in security management processes

• OVHcloud Security Interested Parties

• Analysis of root causes of non-conformities, vulnerabilities and incidents

These opportunities for improvement are evaluated before implementation and where appropriate prioritized and arbitrated. Consecutive action plans are formally followed in the project management tools used by teams

The processor adopts the same technical and organizational measures as the controller, listed above.