Why does demonstrating GDPR compliance require governance, process and technology working as one?
Article 24(1) of the GDPR requires the controller to implement appropriate technical and organisational measures and to review and update them where necessary. Compliance is not a one-off state; it is the ability to produce evidence at any time.
We look at the GDPR in three layers:
- Governance: who determines the lawful basis, who approves high-risk processing, who decides whether a breach is notified. These belong in your existing data protection and corporate governance framework.
- Process: product development, project intake, customer service, incident response and procurement each take on the obligations that naturally land on them.
- Technology: access control, pseudonymisation, logging and the data catalogue keep producing records you can trace.
The most common break point is that the same processing activity cannot be matched across the record of processing activities, the processor contract and the data catalogue. Integration means each piece of evidence is created once and answers supervisory authorities, customer audits and your existing ISO certifications at the same time.
We start from the management system you already operate and build the GDPR requirements into it rather than creating a parallel one, cutting duplicated effort now and maintenance cost later. VP- and director-level consultants lead the engagement end to end, never outsourced. For how each obligation becomes a system setting or a process step, see GDPR technical integration.
How does Ahura keep GDPR evidence reusable across ISO 27001 and ISO 27701?
Records of processing activities, DPIAs and breach records overlap heavily with ISO 27001 and ISO 27701 records, and customers' privacy questionnaires ask for the same material. Continuous integration starts from one principle: a single evidence record and a single sign-off chain should be referenced by every framework that needs it.
The Ahura enterprise risk management platform is currently at proof-of-concept (POC) stage, and everything below refers to the POC version. In a GDPR programme it is the evidence and sign-off layer; it does not replace your CRM, data catalogue or SIEM.
- Available in the POC: 100% on-premises deployment, so records containing personal data never go to the cloud; an end-to-end evidence chain in which every sign-off is recorded and compatible with EU eIDAS certificates; a group-wide distributed architecture; EU multilingual interface; modular extension for EU regulations and international standards.
- In development, released as the POC progresses: cross-standard comparison, gap analysis on uploaded documents, regulatory version timelines and regulatory change tracking. There is no GDPR-specific module today.
Today, DPIAs, the breach register and processor assessments can be signed off on one chain and cited in both GDPR and ISO audits. Once the development features ship, the goal is to show which evidence needs a second look when guidance or regulation changes.
How does outsourcing your GDPR internal audit help you and your DPO plan what comes next?
Article 39(1)(b) of the GDPR makes monitoring compliance, including the related audits, a task of the data protection officer, and Article 32(1)(d) requires a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures. Our internal audit outsourcing service typically checks whether the record of processing activities matches the systems actually in use, whether data subject requests are answered on time, how breaches are assessed and notified, and whether processor contracts are in place.
Objectivity comes first. Under ISO 9000:2015, 3.13.1, an internal (first-party) audit may be conducted by the organisation itself or on its behalf, and independence can be demonstrated by freedom from responsibility for the activity being audited. ISO/IEC 27001:2022, clause 9.2, likewise requires the audit process to be objective and impartial. Our principle follows directly: a consultant never audits a process they designed. The audit is performed by a consultant who had no part in that design.
After the audit we work through the findings with your DPO and management and sort them into three horizons: fixes that cannot wait, work for the next system release, and longer-term capability building. The result is a privacy roadmap you can track. An internal audit is not third-party certification and does not represent the view of a supervisory authority; Winners Consulting provides consulting only and does not issue certifications.
How should processor audits under GDPR Article 28 be run to protect your supply chain?
Article 28(1) requires controllers to use only processors providing sufficient guarantees. Article 28(3)(h) requires the processor to make available all information necessary to demonstrate compliance and to allow for and contribute to audits, including inspections, conducted by the controller or another auditor mandated by the controller. Articles 28(2) and 28(4) govern prior written authorisation of sub-processors and flow-down of the same obligations. The EDPB's Guidelines 07/2020 add that controllers should verify processors' guarantees at appropriate intervals, including through audits where appropriate.
Our GDPR supplier audit service acts as the auditor you mandate. Under ISO 9000:2015, 3.13.1, that makes it a second-party audit. It is not certification: the findings belong to you and feed directly into vendor terms and corrective actions, giving you supply chain assurance you can evidence.
| Supplier type | Audit focus (GDPR requirement) | Evidence retained |
|---|---|---|
| Cloud and SaaS providers | Art. 28(1): technical and organisational measures | Assessment record, security evidence |
| Outsourced customer service and contact centres | Art. 28(3)(h): audits and inspections | Audit report, inspection record |
| Marketing and adtech vendors | Art. 28(1): sufficient guarantees | Processor assessment record |
| HR and payroll outsourcing | Art. 28(3)(h): information demonstrating compliance | Audit report, supporting documents |
| Sub-processors | Art. 28(2) and 28(4): written authorisation, same obligations | Authorisation record, sub-processing contract |
To scope a processor audit programme, contact us.
Official sources
- Regulation (EU) 2016/679 (General Data Protection Regulation, GDPR) — EUR-Lex
- EDPB — Guidelines 07/2020 on the concepts of controller and processor in the GDPR
- ISO/TC 176 — Terms and definitions in TC 176 standards (ISO 9000:2015, 3.13.1 audit, Notes 1–4)
- ISO CASCO — Conformity assessment techniques: Auditing (first-, second-, third-party audits)
