Compliance

GDPR and ISO 27001, without the theatre.

Practical data-protection and information-security compliance for teams that build software. GDPR and ISO 27001 mapped to controls your engineers can actually live with.


Outcomes

What you walk away with

  • A defensible position for your next GDPR or ISO 27001 audit
  • Controls documented once and enforced in the pipeline, not in a binder
  • A posture your customers' procurement and security teams will accept

Capabilities

How the work breaks down

  • GDPR readiness

    Data mapping, lawful-basis and consent review, DPIAs, records of processing, data-subject request workflows, and processor agreements — scoped to what you actually process.

  • ISO 27001 groundwork

    Statement of Applicability, risk assessment and treatment, Annex A control mapping, and the evidence trail an external auditor expects to see.

  • Policy & documentation

    Security, access, incident-response, and data-retention policies written to be read and followed, not filed and forgotten.

  • Controls as code

    Access reviews, logging, encryption, and change management wired into your existing pipelines so compliance is a by-product of how you already work.


Stack & methods

Tools I reach for

  • GDPR
  • ISO/IEC 27001
  • ISO 27002 controls
  • DPIA / ROPA
  • Risk registers
  • Azure Policy & Purview
  • Audit evidence automation

Engagement

Ways we can work together

  • GDPR or ISO 27001 gap assessment
  • Certification readiness programme
  • Ongoing compliance retainer

Questions

Good to know

  • What is GDPR and ISO 27001 compliance?

    GDPR is the EU regime governing how you handle personal data — lawful basis, data-subject rights, and accountability for what you collect. ISO 27001 is the international standard for running an information-security management system. Compliance means mapping both to concrete controls and keeping the evidence that shows they are actually in place, not merely written down.

  • Why choose Stratis for compliance?

    Because I approach it as an engineer, not a form-filler: controls wired into your pipelines and cloud so evidence is generated automatically, and policies written to be followed rather than filed. You get an audit-ready posture that fits how your team builds, instead of a binder that goes stale the day it is signed.


Ready to talk about compliance?

Send a short note about your project. I will reply within a couple of days.

Start a conversation