ICO

INFORMATION COMMISSIONER'S OFFICE (UK)

Preparing for the General Data Protection Regulation (GDPR)

12 steps to take now

1. Awareness

You should make sure that decision makers and key people in your organisation are aware that the law is changing to the GDPR. They need to appreciate the impact this is likely to have.

2.Information you hold

You should document what personal data you hold, where it came from and who you may need to organise an information audit.

3.Communicating privacy information

You should review your current privacy notices and put a plan in place for making any necessary changes in time for GDPR implementation.

4.Individuals’ rights

You should check your procedures to ensure they cover all the rights individuals have, including how you would delete personal data or provide data electronically and in a commonly used format

5.Subject access requests

You should update your procedures and plan how you will handle requests within the new timescales and provide any additional information.

6.Lawful basis for processing personal data

You should identify the lawful basis for your processing activity in the GDPR, document it and update your privacy notice to explain it.

7.Consent

You should review how you seek, record and manage consent and whether you need to make any changes. Refresh existing consents now if they don’t meet the GDPR standard.

8.Children

You should start thinking now about whether you need to put systems in place to verify individuals’ ages and to obtain parental or guardian consent for any data processing activity.

9.Data breaches

You should make sure you have the right procedures in place to detect, report and investigate a personal data breach.

10.Data Protection by Design and Data Protection Impact Assessments

You should familiarise yourself now with the ICO’s code of practice on Privacy Impact Assessments as well as the latest guidance from the Article 29 Working Party, and work out how and when to implement them in your organisation.

11.Data Protection Officers

You should designate someone to take responsibility for data protection compliance and assess where this role will sit within your organisation’s structure and governance arrangements. You should consider whether you are required to formally designate a Data Protection Officer.

12.International

If your organisation operates in more than one EU member state (ie you carry out cross-border processing), you should determine your lead data protection supervisory authority. Article 29 Working Party guidelines will help you do this.

Introduction

This checklist highlights 12 steps you can take now to

prepare for the General Data Protection Regulation

(GDPR) which will apply from 25 May 2018.

Many of the GDPR’s main concepts and principles are much the same as those in the current Data Protection Act (DPA), so if you are complying properly with the current law then most of your approach to compliance will remain valid under the GDPR and can be the starting point to build from. However, there are new elements and significant enhancements, so you will have to do some things for the first time and some things

differently.

It is important to use this checklist and other Information Commissioner’s Office (ICO) resources to work out the main differences between the current law and the GDPR. The ICO is producing new guidance and other tools to assist you, as well as contributing to guidance that the Article 29 Working Party is producing at the European level. These are all available via the ICO’s Overview of the General Data Protection Regulation. The ICO is also working closely with trade associations and bodies representing the various sectors – you should also work closely with these bodies to share knowledge about implementation in your sector.

It is essential to plan your approach to GDPR compliance now and to gain ‘buy in’ from key people in your organisation. You may need, for example, to put new procedures in and individuals’ rights provisions. In a large or complex business this could have significant budgetary, IT, personnel, governance and communications implications.

The GDPR places greater emphasis on the documentation that data controllers must keep to demonstrate their accountability. Compliance with all the areas listed in this document will require organisations to review their approach to governance and how they manage data protection as a corporate issue. One aspect of this might be to review the

contracts and other arrangements you have in place when sharing data with other organisations.

Some parts of the GDPR will have more of an impact on some organisations than on others (for example, the provisions relating to profiling or children’s data), so it would be useful to map out which parts of the GDPR will have the greatest impact on your business model and give those areas due prominence in your planning process.

…......

Step 6: Lawful basis for processing personal data

You should identify the lawful basis for your processing activity in the GDPR, document it and update your privacy notice to explain it. Many organisations will not have thought about their lawful basis for processing personal data. Under the current law this does not have many practical implications. However, this will be different under the GDPR because some individuals’ rights will be modified depending on your lawful basis for processing their personal data. The most obvious example is that people will have a stronger right to have their data deleted where you use consent as your lawful basis for processing.

You will also have to explain your lawful basis for processing personal data in your privacy notice and when you answer a subject access request. The lawful bases in the GDPR are broadly the same as the conditions for processing in the DPA. It should be possible to review the types of processing activities you carry out and to identify your lawful

basis for doing so. You should document your lawful bases in order to help you comply with the GDPR’s ‘accountability’ requirements.

Step 7: Consent

You should review how you seek, record and manage consent and whether you need to make any changes. Refresh existing consents now if they don’t meet the GDPR standard.

You should read the detailed guidance the ICO has published on consent under the GDPR, and use our consent checklist to review your practices. Consent must be freely given, specific, informed and unambiguous. There must be a positive opt-in – consent cannot be inferred from silence, preticked boxes or inactivity. It must also be separate from other terms and conditions, and you will need to have simple ways for people to withdraw

consent. Public authorities and employers will need to take particular care. Consent has to be verifiable and individuals generally have more rights where you rely on consent to process their data.

You are not required to automatically ‘repaper’ or refresh all existing DPA consents in preparation for the GDPR. But if you rely on individuals’ consent to process their data, make sure it will meet the GDPR standard on being specific, granular, clear, prominent, opt-in, properly documented and easily withdrawn. If not, alter your consent mechanisms and seek fresh GDPR-compliant consent, or find an alternative to consent.

Step 8: Children

You should start thinking now about whether you need to put systems in place to verify individuals’ ages and to obtain parental or guardian consent for any data processing activity.

For the first time, the GDPR will bring in special protection for children’s personal data, particularly in the context of commercial internet services such as social networking. If your organisation offers online services (‘information society services’) to children and relies on consent to collect information about them, then you may need a parent or guardian’s consent in order to process their personal data lawfully. The GDPR sets the age when a child can give their own consent to this processing at 16 (although this may be lowered to a minimum of 13 in the UK). If a child is younger then you will need to get consent from a person holding ‘parental responsibility’. This could have significant implications if your organisation offers online services to children and collects their personal data. Remember that consent has to be verifiable and that when collecting children’s data your privacy notice must be written in language that children will understand.

ICO

INFORMATION COMMISSIONER'S OFFICE (UK)

Preparing for the General Data Protection Regulation (GDPR)

12 steps to take now

1. Awareness

You should make sure that decision makers and key people in your organisation are aware that the law is changing to the GDPR. They need to appreciate the impact this is likely to have.

2.Information you hold

You should document what personal data you hold, where it came from and who you may need to organise an information audit.

3.Communicating privacy information

You should review your current privacy notices and put a plan in place for making any necessary changes in time for GDPR implementation.

4.Individuals’ rights

You should check your procedures to ensure they cover all the rights individuals have, including how you would delete personal data or provide data electronically and in a commonly used format

5.Subject access requests

You should update your procedures and plan how you will handle requests within the new timescales and provide any additional information.

6.Lawful basis for processing personal data

You should identify the lawful basis for your processing activity in the GDPR, document it and update your privacy notice to explain it.

7.Consent

You should review how you seek, record and manage consent and whether you need to make any changes. Refresh existing consents now if they don’t meet the GDPR standard.

8.Children

You should start thinking now about whether you need to put systems in place to verify individuals’ ages and to obtain parental or guardian consent for any data processing activity.

9.Data breaches

You should make sure you have the right procedures in place to detect, report and investigate a personal data breach.

10.Data Protection by Design and Data Protection Impact Assessments

You should familiarise yourself now with the ICO’s code of practice on Privacy Impact Assessments as well as the latest guidance from the Article 29 Working Party, and work out how and when to implement them in your organisation.

11.Data Protection Officers

You should designate someone to take responsibility for data protection compliance and assess where this role will sit within your organisation’s structure and governance arrangements. You should consider whether you are required to formally designate a Data Protection Officer.

12.International

If your organisation operates in more than one EU member state (ie you carry out cross-border processing), you should determine your lead data protection supervisory authority. Article 29 Working Party guidelines will help you do this.

Introduction

This checklist highlights 12 steps you can take now to

prepare for the General Data Protection Regulation

(GDPR) which will apply from 25 May 2018.

Many of the GDPR’s main concepts and principles are much the same as those in the current Data Protection Act (DPA), so if you are complying properly with the current law then most of your approach to compliance will remain valid under the GDPR and can be the starting point to build from. However, there are new elements and significant enhancements, so you will have to do some things for the first time and some things

differently.

It is important to use this checklist and other Information Commissioner’s Office (ICO) resources to work out the main differences between the current law and the GDPR. The ICO is producing new guidance and other tools to assist you, as well as contributing to guidance that the Article 29 Working Party is producing at the European level. These are all available via the ICO’s Overview of the General Data Protection Regulation. The ICO is also working closely with trade associations and bodies representing the various sectors – you should also work closely with these bodies to share knowledge about implementation in your sector.

It is essential to plan your approach to GDPR compliance now and to gain ‘buy in’ from key people in your organisation. You may need, for example, to put new procedures in and individuals’ rights provisions. In a large or complex business this could have significant budgetary, IT, personnel, governance and communications implications.

The GDPR places greater emphasis on the documentation that data controllers must keep to demonstrate their accountability. Compliance with all the areas listed in this document will require organisations to review their approach to governance and how they manage data protection as a corporate issue. One aspect of this might be to review the

contracts and other arrangements you have in place when sharing data with other organisations.

Some parts of the GDPR will have more of an impact on some organisations than on others (for example, the provisions relating to profiling or children’s data), so it would be useful to map out which parts of the GDPR will have the greatest impact on your business model and give those areas due prominence in your planning process.

…......

Step 3: Communicating privacy information

You should review your current privacy notices and put a plan in place for making any necessary changes in time for GDPR implementation. When you collect personal data you currently have to give people certain information, such as your identity and how you intend to use their information. This is usually done through a privacy notice. Under the GDPR there are some additional things you will have to tell people. For example, you will need to explain your lawful basis for processing the data, your data retention periods and that individuals have a right to complain to the ICO if they think there is a problem with the way you are handling their data. The GDPR requires the information to be provided in

concise, easy to understand and clear language.

The ICO’s Privacy notices code of practice reflects the new requirements of the GDPR.

Step 4: Individuals’ rights

You should check your procedures to ensure they cover all the rights individuals have, including how you would delete personal data or provide data electronically and in a commonly used format.

The GDPR includes the following rights for individuals:

 the right to be informed;

 the right of access;

 the right to rectification;

 the right to erasure;

 the right to restrict processing;

 the right to data portability;

 the right to object; and

 the right not to be subject to automated decision-making including

profiling.

On the whole, the rights individuals will enjoy under the GDPR are the same as those under the DPA but with some significant enhancements. If you are geared up to give individuals their rights now, then the transition to the GDPR should be relatively easy. This is a good time to check your procedures and to work out how you would react if someone asks to have their personal data deleted, for example. Would your systems help you to

locate and delete the data? Who will make the decisions about deletion?

The right to data portability is new. It only applies:

 to personal data an individual has provided to a controller;

 where the processing is based on the individual’s consent or for the performance of a contract; and

 when processing is carried out by automated means.

You should consider whether you need to revise your procedures and make any changes. You will need to provide the personal data in a structured commonly used and machine readable form and provide the information free of charge.

Step 5: Subject access requests

You should update your procedures and plan how you will handle requests to take account of the new rules:

 In most cases you will not be able to charge for complying with a request.

 You will have a month to comply, rather than the current 40 days.

 You can refuse or charge for requests that are manifestly unfounded or excessive.

 If you refuse a request, you must tell the individual why and that they have the right to complain to the supervisory authority and to a judicial remedy. You must do this without undue delay and at the latest, within one month.

If your organisation handles a large number of access requests, consider the logistical implications of having to deal with requests more quickly.

You could consider whether it is feasible or desirable to develop systems that allow individuals to access their information easily online.

TBC

Изграждане 

на Система за защита на личните данни, 

съгласно изискванията на GDPR

Какви и колко основни стъпки трябва да извървим, за да защитим личните данни, които обработваме, съхраняваме и обменяме ? Професионален отговор е даден от Infomation Commissioner's Office / ICO (UK). 

Infosec Service (в частност аз - Пламен Каменов) със сигурност може да Ви помогне да преминете тези стъпки без особени проблеми, на база услугите, които предлага за обучение и консултации по информационна / киберсигурност и защита на личните данни.

В няколко последователни публикации ще  представя описанието на стъпките (така, както са дадени от ICO), съпроводени от кратки, мои коментари.

ICO

INFORMATION COMMISSIONER'S OFFICE (UK)

Preparing for the General Data Protection Regulation (GDPR)

12 steps to take now

1. Awareness

You should make sure that decision makers and key people in your organisation are aware that the law is changing to the GDPR. They need to appreciate the impact this is likely to have.

2.Information you hold

You should document what personal data you hold, where it came from and who you may need to organise an information audit.

3.Communicating privacy information

You should review your current privacy notices and put a plan in place for making any necessary changes in time for GDPR implementation.

4.Individuals’ rights

You should check your procedures to ensure they cover all the rights individuals have, including how you would delete personal data or provide data electronically and in a commonly used format

5.Subject access requests

You should update your procedures and plan how you will handle requests within the new timescales and provide any additional information.

6.Lawful basis for processing personal data

You should identify the lawful basis for your processing activity in the GDPR, document it and update your privacy notice to explain it.

7.Consent

You should review how you seek, record and manage consent and whether you need to make any changes. Refresh existing consents now if they don’t meet the GDPR standard.

8.Children

You should start thinking now about whether you need to put systems in place to verify individuals’ ages and to obtain parental or guardian consent for any data processing activity.

9.Data breaches

You should make sure you have the right procedures in place to detect, report and investigate a personal data breach.

10.Data Protection by Design and Data Protection Impact Assessments

You should familiarise yourself now with the ICO’s code of practice on Privacy Impact Assessments as well as the latest guidance from the Article 29 Working Party, and work out how and when to implement them in your organisation.

11.Data Protection Officers

You should designate someone to take responsibility for data protection compliance and assess where this role will sit within your organisation’s structure and governance arrangements. You should consider whether you are required to formally designate a Data Protection Officer.

12.International

If your organisation operates in more than one EU member state (ie you carry out cross-border processing), you should determine your lead data protection supervisory authority. Article 29 Working Party guidelines will help you do this.

Introduction

This checklist highlights 12 steps you can take now to

prepare for the General Data Protection Regulation

(GDPR) which will apply from 25 May 2018.

Many of the GDPR’s main concepts and principles are much the same as those in the current Data Protection Act (DPA), so if you are complying properly with the current law then most of your approach to compliance will remain valid under the GDPR and can be the starting point to build from. However, there are new elements and significant enhancements, so you will have to do some things for the first time and some things

differently.

It is important to use this checklist and other Information Commissioner’s Office (ICO) resources to work out the main differences between the current law and the GDPR. The ICO is producing new guidance and other tools to assist you, as well as contributing to guidance that the Article 29 Working Party is producing at the European level. These are all available via the ICO’s Overview of the General Data Protection Regulation. The ICO is also working closely with trade associations and bodies representing the various sectors – you should also work closely with these bodies to share knowledge about implementation in your sector.

It is essential to plan your approach to GDPR compliance now and to gain ‘buy in’ from key people in your organisation. You may need, for example, to put new procedures in and individuals’ rights provisions. In a large or complex business this could have significant budgetary, IT, personnel, governance and communications implications.

The GDPR places greater emphasis on the documentation that data controllers must keep to demonstrate their accountability. Compliance with all the areas listed in this document will require organisations to review their approach to governance and how they manage data protection as a corporate issue. One aspect of this might be to review the

contracts and other arrangements you have in place when sharing data with other organisations.

Some parts of the GDPR will have more of an impact on some organisations than on others (for example, the provisions relating to profiling or children’s data), so it would be useful to map out which parts of the GDPR will have the greatest impact on your business model and give those areas due prominence in your planning process.

Step1: Awareness

You should make sure that decision makers and key people in your organisation are aware that the law is changing to the GDPR. They needto appreciate the impact this is likely to have and identify areas that could cause compliance problems under the GDPR. It would be useful to start by looking at your organisation’s risk register, if you have one.

Implementing the GDPR could have significant resource implications, especially for larger and more complex organisations.

You may find compliance difficult if you leave your preparations until the last minute.

Step 2: Information you hold

You should document what personal data you hold, where it came from and who you share it with. You may need to organise an information audit across the organisation or within particular business areas.

The GDPR requires you to maintain records of your processing activities. It updates rights for a networked world. For example, if you have inaccurate personal data and have shared this with another organisation, you will have to tell the other organisation about the inaccuracy so it can correct its own records. You won’t be able to do this unless you know what personal data you hold, where it came from and who you share it with. You should with the GDPR’s accountability principle, which requires organisations to be able to show how they comply with the data protection principles, for example by having effective policies and procedures in place.

TBC

КАТАЛОГ

НА ДИСТАНЦИОННО ПРЕДОСТАВЯНИТЕ УСЛУГИ

ЗА УПРАВЛЕНИЕ НА 

ИНФОРМАЦИОННАТА / КИБЕР СИГУРНОСТ

1. Обучение за:
   - изграждане на Система за управление на информационната / кибер сигурност, в съответствие с изискванията на ISO 27001 и препоръките на приложими стандарти от фамилията ISO 27000;
   - изграждане на Система за управление на защитата на личните данни, в съответствие с изискванията на Европейския Регламент (ЕС) 2016 / 679 (EU Global Data Prtotection Regulation – EU GDPR);
   - провеждане на Оценка и анализ на риска към информационната / кибер сигурност;
   - провеждане на Оценка и анализ на риска към защитата на личните данни;
   - избор на контролни / защитни механизми за противодействие на рисковете към информационната / кибер сигурност и сигурността на личните данни;
   - изпълнение на функцията „Длъжностно лице по защита на личните данни“, съгласно изискванията на EU GDPR;
   - провеждане на одити за съответствие с изискванията на ISO 27001 на Системи за управление на информационната сигурност;
   - провеждане на одити за съответствие с изискванията на EU GDPR на Системи за управление на защитата на личните данни;

2. Изпълнение на:
   - задачите на „Длъжностно лице по защита на личните данни“, съгласно изискванията на EU GDPR;
   - подготовка и последваща поддръжка на документалната част (напр. политики, процедури, инструкции, планове и др.) на Системи за управление на информационната сигурност, в съответствие с изискванията на ISO 27001;
   - подготовка и последваща поддръжка на документалната част (напр. политики, процедури, инструкции, планове и др.) на Системи за управление на защитата на личните данни, в съответствие с изискванията на EU GDPR;
   - препоръки за избор на контролни / защитни механизми , свързани с информационната / кибер сигурност и защитата на личните данни;
   - препоръки за начина на внедряване, поддръжка и развитие на контролни / защитни механизми , свързани с информационната / кибер  сигурност и защитата на личните данни;

Контакти:

Пламен Каменов – Водещ одитор ISO 27001

0886 655 315 / infosecservicebg@gmail.com

ПРЕДОСТАВЯНЕ НА УСЛУГИ ЗА ИЗПЪЛНЕНИЕ НА ЗАДАЧИТЕ

НА „ДЛЪЖНОСТНО ЛИЦЕ ПО ЗАЩИТА НА ДАННИТЕ“

В СЪОТВЕТСТВИЕ С ИЗИСКВАНИЯТА НА РЕГЛАМЕНТ (ЕС) 2016/679

EU GLOBAL DATA PROTECTION REGULATION (GDPR)

Data Processing Officer as a Service

Описаните по-долу услуги, се основават на възможността, посочена в Раздел 4, Член 37, параграф 6, от Регламента, че „Длъжностното лице по защита на данните може да бъде член на персонала на администратора или на обработващия лични данни или да изпълнява задачите въз основа на договор за услуги“. Това означава, че всяка организация (администратор или обработваща лични данни) е в правото си да вземе решение, за това кой да изпълнява функциите и задачите на „Длъжностно лице по защита на данните“ - свой служител или да наеме външно лице, което да предоставя по договор съответните услуги.

Използването на външно лице за изпълнение на задачите на „Длъжностно лице по защита на данните“ е особено приложимо и икономически обосновано за малки и средни, бизнес организации (администратори или обработващи лични данни) които:

• нямат опит в областта на информационната сигурност и/или защитата на личните данни;
• нямат подготвен персонал, за работа по въпросите на информационната сигурност и/или защитата на личните данни;
• нямат сериозни бизнес причини да инвестират в собствен персонал, който да изпълнява задачите на „Длъжностно лице по защита на личните данни“;
• желаят да се възползват от бизнес модела “Data Processing Officer as a Service”, в контекста на прилагане на финансово и икономически изгодно бизнес решение, осигуряващо контролирано, професионално изпълнение на задачите на „Длъжностно лице по защита на личните данни“.

Обхвата на предоставяните услуги включва изпълнението на всички задачи, така, както са описани в Член 39 от Регламента - „Задачи на длъжностното лице по защита на данните“.

Начина на изпълнение на всяка конкретна задача е обект на съгласуване и договаряне със съответната организация (администратор или обработваща лични данни), ползвател на услугите по модела “Data Processing Officer as a Service”.

Освен описаните в Член 39 от Регламента задачи могат, в зависимост конкретния случай, да се съгласуват и договорят допълнителни задачи към тези от Член 35 на Регламента, свързани с „Длъжностното лице по защитата на личните данни“.

Всички услуги по изпълнението на задачите на „Длъжностното лице по защитата на личните данни“, могат да бъдат реализирани на место, в съответната организация и/или дистанционно, по електронен път.

Всички услуги ще се извършват от Пламен Каменов (водещ одитор по ISO 27001, ISO 9001 и одитор ISO 20000-1), със значителен професионален опит в областта на обучението, изграждането и сертифицирането на:

• системи за управление на информационната сигурност (ISO 27001);
• системи за управление на ИТ услугите и тяхната сигурност (ISO 20000-1);
• системи за управление на качеството (ISO 9001);

Забележка: По - долу е приложен пълния текст на Раздел 4 от Регламент (ЕС) 2016/679, свързан с „Длъжностно лице по защита на данните“.

РЕГЛАМЕНТ (ЕС) 2016/679 НА ЕВРОПЕЙСКИЯ ПАРЛАМЕНТ И НА СЪВЕТА

от 27 април 2016 година

относно защитата на физическите лица във връзка с обработването на лични данни и относно свободното движение на такива данни и за отмяна на Директива 95/46/EО 

(Общ регламент относно защитата на данните)

Раздел 4

Длъжностно лице по защита на данните

Член 37

Определяне на длъжностното лице по защита на данните

1.Администраторът и обработващият лични данни определят длъжностно лице по защита на данните във всички случаи, когато:

a) обработването се извършва от публичен орган или структура, освен когато става въпрос за съдилища при изпълнение на съдебните им функции;

б) основните дейности на администратора или обработващия лични данни се състоят в операции по обработване, които поради своето естество, обхват и/или цели изискват редовно и систематично мащабно наблюдение на субектите на данни; или

в) основните дейности на администратора или обработващия лични данни се състоят в мащабно обработване на специалните категории данни съгласно член 9 и на лични данни, свързани с присъди и нарушения, по член 10.

2.Група предприятия може да назначи едно длъжностно лице по защита на данните, при условие че от всяко предприятие има лесен достъп до длъжностно лице по защита на данните.

3.Когато администраторът или обработващият лични данни е обществен орган или структура, едно длъжностно лице по защита на данните може да бъде назначено за няколко такива органа или структури, като се отчита организационната им структура и размер.

4.В случаи, различни от посочените в параграф 1, администраторът или обработващият лични данни или сдружения и други структури, представляващи категории администратори или обработващи лични данни, могат да определят — или ако това се иска от правото на Съюза или право на държава членка определят — длъжностно лице по защита на данните. Длъжностното лице по защита на данните може да действа в полза на такива сдружения и други структури, представляващи администратори или обработващи лични данни.

5.Длъжностното лице по защита на данните се определя въз основа на неговите професионални качества, и по- специално въз основа на експертните му познания в областта на законодателството и практиките в областта на защитата на данните и способността му да изпълнява задачите, посочени в член 39.

6.Длъжностното лице по защита на данните може да бъде член на персонала на администратора или на обработващия лични данни или да изпълнява задачите въз основа на договор за услуги.

7.Администраторът или обработващият лични данни публикува данните за контакт с длъжностното лице по защита на данните и ги съобщава на надзорния орган.

Член 38

Длъжност на длъжностното лице по защита на данните

1.Администраторът и обработващият лични данни гарантират, че длъжностното лице по защита на данните участва по подходящ начин и своевременно във всички въпроси, свързани със защитата на личните данни.

2.Администраторът и обработващият лични данни подпомагат длъжностното лице по защита на данните при изпълнението на посочените в член 39 задачи, като осигуряват ресурсите, необходими за изпълнението на тези задачи, и достъп до личните данни и операциите по обработване, а така също поддържат неговите експертни знания.

3.Администраторът и обработващият лични данни правят необходимото длъжностното лице по защита на данните да не получава никакви указания във връзка с изпълнението на тези задачи. Длъжностното лице по защита на данните не може да бъде освобождавано от длъжност, нито санкционирано от администратора или обработващия лични данни за изпълнението на своите задачи. Длъжностното лице по защита на данните се отчита пряко пред най-висшето ръководно ниво на администратора или обработващия лични данни.

4.Субектите на данни могат да се обръщат към длъжностното лице по защита на данните по всички въпроси, свързани с обработването на техните лични данни и с упражняването на техните права съгласно настоящия регламент.

5.Длъжностното лице по защита на данните е длъжно да спазва секретността или поверителността на изпълняваните от него задачи в съответствие с правото на Съюза или правото на държава членка.

6.Длъжностното лице по защита на данните може да изпълнява и други задачи и задължения. Администраторът или обработващият лични данни прави необходимото тези задачи и задължения да не водят до конфликт на интереси.

Член 39

Задачи на длъжностното лице по защита на данните

1.Длъжностното лице по защита на данните изпълнява най-малко следните задачи:

a) да информира и съветва администратора или обработващия лични данни и служителите, които извършват обработване, за техните задължения по силата на настоящия регламент и на други разпоредби за защитата на данни на равнище Съюз или държава членка;

б) да наблюдава спазването на настоящия регламент и на други разпоредби за защитата на данни на равнище Съюз или държава членка и на политиките на администратора или обработващия лични данни по отношение на защитата на личните данни, включително възлагането на отговорности, повишаването на осведомеността и обучението на персонала, участващ в операциите по обработване, и съответните одити;

в) при поискване да предоставя съвети по отношение на оценката на въздействието върху защитата на данните и да наблюдава извършването на оценката съгласно член 35;

г) да си сътрудничи с надзорния орган;

д) да действа като точка за контакт за надзорния орган по въпроси, свързани с обработването, включително предварителната консултация, посочена в член 36, и по целесъобразност да се консултира по всякакви други въпроси.

2.При изпълнението на своите задачи длъжностното лице по защита на данните надлежно отчита рисковете, свързани с операциите по обработване, и се съобразява с естеството, обхвата, контекста и целите на обработката.

За контакти:

Пламен Каменов

0886 655 315

е-mail: infosecservicebg@gmail.com