Which existing business processes must GDPR obligations be built into?
The GDPR (Regulation (EU) 2016/679) is written in terms of outcomes: the controller must be able to demonstrate compliance (Article 5(2)) and implement appropriate technical and organisational measures (Article 24). Demonstrating it means the obligations have to live inside processes that run every day. We usually start at six points:
- Product development and change requests: Article 25 requires data protection by design and by default, processing by default only the personal data necessary for each purpose, so privacy checks belong in requirements and design review, not after go-live.
- Project intake: processing likely to result in a high risk needs a DPIA before it starts (Article 35).
- Membership, marketing and customer service: requests from data subjects must in principle be answered within one month of receipt, extendable by two further months where necessary (Article 12(3)).
- Security incident response: a personal data breach must, where feasible, be notified to the supervisory authority within 72 hours of becoming aware of it (Article 33).
- Procurement and outsourcing: processors are governed by contract (Article 28), and Chapter V applies when third countries are involved.
- Data governance: the Article 30 record of processing activities (RoPA) has to keep up with system changes.
This page is about how legal obligations become systems and processes. If you want a certifiable management system to carry those obligations, see ISO 27701.
Which implementation and security technologies put each GDPR obligation into practice?
Every GDPR obligation ends up as a setting in some system or a record in some process. These are the mappings we build most often; article numbers follow the text published on EUR-Lex:
| Requirement (article / control) | Implementing technology | Evidence left behind |
|---|---|---|
| Art. 25: data protection by design and by default | Privacy checks at requirements stage, pseudonymisation, collecting only necessary fields with the shortest retention by default | Design review records, versioned field and retention settings |
| Art. 30: records of processing activities (RoPA) | RoPA fields updated from the data catalogue and data-flow inventory: purposes, categories of data subjects and data, recipients, third-country transfers, erasure time limits, security measures | A RoPA version that can be made available to the supervisory authority under Art. 30(4) |
| Art. 32: security of processing | Encryption and pseudonymisation, least-privilege IAM, backup with timely restore, regular testing of control effectiveness | Encryption settings, access reviews, restore tests, vulnerability scan reports |
| Art. 33–34: breach notification and communication to data subjects | SIEM/DLP alerts feed incident tickets with a 72-hour clock and a high-risk assessment step; a channel for processors to notify the controller | Breach register (Art. 33(5)), notification content with timestamps |
| Art. 35–36: DPIA and prior consultation | DPIA triggers built into project intake, assessment templates and risk scoring | DPIA reports covering the four elements of Art. 35(7), review and consultation records |
| Art. 12–22: data subject rights | Request portal, identity verification, cross-system search and erasure, structured machine-readable export | Request log, deadline tracking, export files and erasure records |
| Art. 28: processor contracts | Processor inventory, contract templates, register of sub-processors and their countries | Signed contracts, processor assessment records |
| Chapter V (Art. 44–49): international transfers | Data-flow map flagging third countries; standard contractual clauses under Art. 46 (Decision (EU) 2021/914); transfer impact assessment and supplementary measures such as encryption | SCC signing pack, transfer impact assessment, transfer list |
Two reminders. First, Article 32 does not prescribe a particular type of encryption or product. It requires a level of security appropriate to the risk and lists pseudonymisation and encryption; ongoing confidentiality, integrity, availability and resilience; timely restoration of access; and regular testing of the effectiveness of measures. Technology choices must go back to the risk assessment. Second, Taiwan is not currently on the European Commission's list of adequacy decisions, so personal data sent from the EU to Taiwan usually relies on appropriate safeguards under Article 46, such as standard contractual clauses. The evidence column in each row is what you should be able to hand over directly when a supervisory authority or client comes asking.
How does personal data risk flow through to GDPR articles, technical controls and metrics?
We tie risk, compliance and technology into one chain. Take an e-commerce business that uses member data for personalised recommendations, hosted by a cloud provider in a third country:
- Risk identification: member behaviour is profiled for preferences; data is stored in a third country; the customer-service and marketing systems each hold a copy, and erasure requests reach only one of them.
- Regulatory requirement: processing likely to result in a high risk needs a prior DPIA (Article 35); data protection by design and by default (Article 25); third-country transfers must meet Chapter V; rights such as erasure and portability must be answered on time (Articles 12–22).
- Technical control: the recommendation model takes only necessary fields, pseudonymised; the data catalogue tags every copy so erasure runs across systems; transfers are covered by standard contractual clauses and encryption; SIEM and DLP detect abnormal access.
- Metrics: actual response days for rights requests against the one-month limit, hours from awareness to completed assessment of a breach against 72 hours, the number of differences between the RoPA and the data catalogue, and the share of high-risk processing with a completed DPIA.
It can be done in one pass because the same team plans risk management, legal compliance, implementation and security technology, and process improvement together. Security controls fold straight into an existing ISO 27001 system, so one body of evidence answers several regulations and client requirements without a parallel system.
Which departments, systems, data and evidence must GDPR integrate vertically?
GDPR evidence is spread across legal, product, IT, customer service and procurement. The point of vertical integration is to give each processing activity one identifier across the RoPA, the data catalogue, contracts and incident tickets, so it can be found, fully erased and explained. This is the mapping we usually build:
| Department | System | Data | Evidence |
|---|---|---|---|
| Legal / data protection officer (DPO) | Contract and compliance management | Lawful bases, processor contracts, SCCs | Applicability assessment, signed contracts, transfer impact assessments |
| Product and engineering | Requirements management, CI/CD | Field design, retention settings, pseudonymisation rules | Design review and release approval records |
| IT / security | IAM, SIEM, DLP, backup | Access records, logs, alerts | Access reviews, breach register, restore tests |
| Marketing and customer service | CRM, membership system, consent management | Consent records, rights requests | Request handling records, export files, erasure records |
| Data and IT architecture | Data catalogue, data warehouse | Data categories, data flows, retention periods | RoPA versions, data-flow maps |
| Procurement | Supplier management | Processors and sub-processors, their countries | Processor assessments, transfer list |
The table is used directly. When the supervisory authority asks for the RoPA, the version from data architecture must match the data catalogue. When a member asks for erasure, the customer-service ticket must trigger every system holding a copy and leave an erasure record. When a breach happens, security's alerts, legal's high-risk assessment and the notification content sit on one timeline.
We start from the system you already have. If you already run a CRM, a ticketing system or an ISMS, we add the GDPR fields and process steps to them rather than building a parallel system, which reduces duplicated effort and lowers long-term maintenance.
What does Ahura do in a GDPR engagement, and how does data flow?
Ahura is a Taiwan-born RegTech platform for enterprise risk and compliance developed by Winners Consulting, currently at POC (proof-of-concept) stage. In a GDPR engagement it is the evidence retention and sign-off layer; it does not replace your CRM, data catalogue or SIEM.
The data flow is: consultant deliverables (applicability assessment, RoPA template, DPIA reports, breach response procedure) and records produced by your systems (RoPA exports, rights-request records, breach register, SCC signing packs) → imported into Ahura on-premises → signed off step by step by the responsible owners, each sign-off entering the chain → available to internal audit, clients, certification bodies or supervisory authorities.
Capabilities in the POC version that matter for GDPR:
- 100% on-premises: RoPAs, DPIAs and breach records themselves contain personal data and trade secrets; they never go to the cloud or leave your environment.
- End-to-end evidence chain: every sign-off enters the chain, compatible with EU eIDAS certificates.
- EU multilingual interface: German, French, Dutch, Czech and more, plus Traditional Chinese and English.
- Modular extension design: EU regulations, harmonised standards and international standards are added as modules.
To be clear: GDPR-specific modules (for example RoPA or rights-request management) are planned under the modular extension design. For now the platform focuses on the evidence chain, sign-off and on-premises retention. Document upload with compliance gap analysis, cross-standard comparison and regulatory change tracking are in development and will open as the POC progresses.
What verifiable governance, risk, efficiency and continuous-compliance gains follow?
We only describe changes you can check afterwards, with no guarantees:
- Governance: Article 5(2)'s "able to demonstrate compliance" becomes tangible. RoPAs, DPIAs, the breach register and rights-request records are versioned and signed, so management sees traceable records.
- Risk: high-risk processing is caught and assessed at project intake rather than discovered after launch; third-country transfers have a list, contracts and supplementary measures, instead of "we don't know where the data is".
- Efficiency: one body of evidence answers several requirements. Client privacy questionnaires, processor contract audits and ISO 27001 or ISO 27701 certification draw on the same records; new requirements fold into the existing system, cutting duplicated effort and long-term maintenance.
- Continuous compliance: design reviews, rights requests and breach notification have clocks and owners; the RoPA updates when systems change, and DPIAs are reviewed under Article 35(11) when the risk changes.
Indicators you can test: the share of rights requests answered within the deadline, actual hours from awareness to the notification decision, the match rate between the RoPA and the data catalogue, and the share of high-risk processing with a completed DPIA. Engagements are led in person by vice-president and director-level consultants, never outsourced; Winners provides consulting only and does not certify. To scope your case, contact us.
Continuous assurance & trusted supply chain: GDPR Internal Audit Outsourcing & Processor Audits
Technical integration for related services
Official sources
- Regulation (EU) 2016/679 (General Data Protection Regulation, GDPR) — EUR-Lex
- EDPB — Guidelines on Data Protection Impact Assessment (WP248 rev.01)
- Commission Implementing Decision (EU) 2021/914 — standard contractual clauses for transfers to third countries — EUR-Lex
- European Commission — Adequacy decisions (data protection adequacy for non-EU countries)
