GDPR

Publikacja i obecny kontekst

Adopted in 2016 and applicable from 25 May 2018 across the European data-protection regime.

Obowiązkowy czy dobrowolny

Applies to organizations processing personal data of people in the EU/EEA when the territorial or offering/monitoring tests are met.

Dla kogo istotny

Controllers, processors, SaaS providers, public bodies, global companies with EU users, and teams handling employee, customer, student, patient, or citizen data.

Model mechanizmów kontrolnych

Privacy governance, lawful basis, data-subject rights, records of processing, processor controls, breach readiness, retention, DPIAs, access, and accountability evidence.

What GDPR asks teams to prove

Ogólne rozporządzenie o ochronie danych becomes operational when obligations are turned into scoped controls, named owners, evidence requests, review decisions, residual risk, and management reporting. The guide page keeps that chain explicit so buyers can understand how the standard is handled inside PlanGRC.

Praktyczny plan działania

1. Define scope

   Confirm business units, systems, data classes, regions, and services where GDPR applies.

2. Map controls

   Translate obligations into controls, owner assignments, due dates, testing approach, and evidence expectations.

3. Collect proof

   Request evidence from owners, preserve attachments or vault references, and keep reviewer decisions traceable.

4. Assess gaps

   Score readiness, identify missing evidence, evaluate residual risk, and create remediation tickets where needed.

5. Report and maintain

   Publish executive and audit-ready views, keep exceptions visible, and re-run periodic reviews after change.

Powiązane procesy