---
title: "Data flow diagrams auditors accept, with a worked example"
canonical: "https://auditbadger.com/blog/data-flow-diagrams-auditors-accept-with-a-worked-example/"
last-updated: "2026-10-05"
---

# Data flow diagrams auditors accept, with a worked example

By Maciej • Published 2026-10-23 • 8 min read • Categories: Soc2, ISO, Evidence Collection, Compliance Governance

Created with AI assistance. AuditBadger retains editorial control and responsibility.

**TL;DR:** A data flow diagram passes a SOC 2 or ISO 27001 audit when every transfer names its source, target, the data moved and how it is protected, when it matches your real asset and vendor registers, when a named person approved that exact version, and when it is reviewed whenever systems or vendors change. Auditors use it to understand the system boundary and components in a SOC 2 system description and to test CC6.7, and in ISO 27001 it supports the scope interfaces in clause 4.3 and information transfer under A.5.14; it also feeds GDPR Article 30 records. A typical small SaaS needs about six transfers: browser to app, app to database, database to backups, app to email provider, browser to analytics, and engineers querying production, which is the flow most teams forget. Write more on the arrows than in the boxes, keep protections to things you can prove, split diagrams by process, and approve every version you rely on so it counts as evidence.

A data flow diagram auditors accept is boring on purpose. It shows every place customer data moves, and for each move it names four things: where the data comes from, where it goes, what data it is, and how it is protected on the way. It matches how your system actually works today, someone approved that exact version, and you can show when it was last reviewed. That is the whole bar for SOC 2® and ISO 27001. It is not a design exercise.

It is easy to miss in either direction. Teams produce a beautiful architecture diagram with forty boxes and zero information about data. Or nothing exists, and the auditor asks for one in week two.

Here is what the diagram is for, what makes it pass, and a worked example for a typical small SaaS.

## Where do auditors and buyers actually use a data flow diagram?

None of the frameworks says &quot;thou shalt draw a diagram&quot;. They all ask questions that a diagram happens to answer faster than prose.

**SOC 2.** Your system description has to explain the components of the system (infrastructure, software, people, procedures and data) and where the boundaries are. A data flow diagram is the quickest way to show what is inside the boundary and which subservice organizations sit outside it. The auditor also uses it to test CC6.7, which is about restricting and protecting information as it moves between users, systems and external parties. If you have not written your system description yet, [what a SOC 2 system description is](/blog/what-is-a-soc-2-system-description/) covers the full structure.

**ISO 27001.** Clause 4.3 asks you to consider the interfaces and dependencies between what you do and what other organizations do for you when you set your scope. Annex A control A.5.14 (information transfer) asks you to have rules for transferring information, internally and with outside parties. A diagram is evidence for both, and it keeps your scope statement honest. Our guide to [writing an ISMS scope statement](/blog/how-to-write-your-isms-scope-statement-with-examples/) leans on exactly this.

**GDPR.** Article 30 records of processing activities ask for categories of data, recipients and transfers to third countries. A good data flow map is most of the raw material.

**Buyers.** Security questionnaires keep asking &quot;where is our data stored, and who else touches it?&quot; A diagram with a transfer table answers that in one attachment instead of twelve free-text fields.

## What makes a data flow diagram acceptable?

Four properties. Miss one and the diagram turns into decoration.

### 1. Every transfer has source, target, data and protection

This is the part people skip. An arrow from &quot;App&quot; to &quot;Database&quot; says nothing. An arrow labelled &quot;customer account records and uploaded files, TLS 1.2+ inside the VPC, encrypted at rest with provider-managed keys&quot; says everything an auditor needs to pick a sample.

If you only take one thing from this post: draw fewer boxes, and write more on the arrows.

### 2. It matches reality

Auditors compare the diagram to the things they can see: your infrastructure inventory, your vendor list, your cloud console screenshots. If the diagram says &quot;PostgreSQL&quot; and your vendor list says you also send data to an analytics tool nobody drew, that is a finding. Build the diagram from your asset and vendor registers, not from memory.

### 3. It is approved and versioned

A diagram in a shared drive that anyone can edit is a sketch, not evidence. The auditor wants to know which version was in force during the audit period and who signed off on it. That means an approval with a name and a date, and old versions that stay frozen when you edit the current one.

### 4. It is reviewed when systems change

New vendor? New region? New feature that ships data to a model provider? The diagram has to move with it. A yearly review is the minimum. A review triggered by architecture changes is what actually keeps it true (and is a much easier conversation with your auditor).

## A worked example for a small SaaS

Take a typical setup: a web app on a cloud provider, a managed PostgreSQL database, nightly backups, a transactional email provider and a product analytics tool. Six transfers cover almost everything.

| # | Source | Target | Data | Protection |
| --- | --- | --- | --- | --- |
| 1 | Customer browser | Web app (load balancer) | Login credentials, account data, uploaded files | HTTPS (TLS 1.2+), HSTS, MFA available for users |
| 2 | Web app | Managed PostgreSQL | Customer records, uploaded file metadata | Private network only, TLS, encryption at rest, access limited to the app role |
| 3 | Managed PostgreSQL | Backup storage (same provider, second region) | Full database snapshots | Encrypted at rest, access limited to two named admins, restore tested quarterly |
| 4 | Web app | Transactional email provider | Recipient email address, name, notification content | TLS to provider API, API key in secrets manager, provider on the vendor register with its report reviewed |
| 5 | Customer browser | Product analytics tool | Pseudonymous user ID, page events (no form contents) | HTTPS, IP truncation enabled, no customer records sent |
| 6 | Engineer laptop | Managed PostgreSQL (read replica) | Query results for support cases | SSO plus MFA, bastion access only, sessions logged |

Then draw it. Six arrows, each numbered to match the table. Put a dashed line around what is inside your system boundary and mark the email and analytics providers as outside it. That is the whole diagram.

Notice what row 6 does. It is the transfer most teams forget, because nobody thinks of a support query as &quot;data flow&quot;. Auditors do. Humans pulling data out of production is exactly the kind of movement CC6.7 and A.5.14 care about.

Also notice the protection column says things you can prove. &quot;Restore tested quarterly&quot; only belongs there if a restore log exists. If it does not exist yet, write what is true and fix the gap, rather than writing the aspiration.

## Which mistakes get data flow diagrams rejected?

- **Architecture instead of data.** Forty boxes, no labels on the arrows. Pretty, useless for a sample.
- **The forgotten vendor.** Error tracking, support desk, analytics, an AI feature that calls a model API. If it receives customer data, it is a transfer and it belongs on the vendor register too.
- **Human flows missing.** Support exports, admin consoles, CSV downloads for a sales deck. People move data as well as services.
- **No owner and no date.** If nobody approved it, the auditor cannot tell whether it reflects the period under review.
- **One giant diagram.** Splitting by process (signup, billing, file processing, support) is easier to keep true than one poster nobody dares to edit.
- **Protection by vibes.**&quot;Secure&quot; is not a protection. TLS version, encryption at rest, who has access and how it is logged are.

## How often should you update it?

Review it at least once a year as part of your management review or system description refresh. Update it whenever you add a vendor that touches customer data, change regions, or ship a feature that sends data somewhere new. The approval step is what turns each update into evidence, so approve every version you actually rely on.

## How we handle this in AuditBadger

The usual failure is drift: the diagram lives in a drawing tool, the vendor list lives somewhere else, and they slowly disagree. That is why data flow maps sit under Assets in AuditBadger. You can describe a process in plain words and get a suggested map to review, start from an editable example, or build one by hand. Each transfer lists the source, target, data and protection, and the suggestion can use the vendor and infrastructure asset names you already have in your [asset register](/features/asset-management/), so the map and the registers use the same names.

The suggestion is a starting point. You answer its questions, ask for changes, and your manual edits are kept. Saving creates a draft. When the map is right, you approve it with a short summary, and that exact version is frozen with the approver&#39;s name and the time. Later edits do not touch the approved version, and each approved version can be downloaded as a PDF. In an ISO 27001 workbook you can link an approved version to a requirement as evidence.

Approved maps can also be collected as an evidence snapshot, which uses the latest approved version of each map and shows whether the map has changed since approval. Collection runs on a schedule, so a fresh approval may take a little while to show up. What it does not do is decide whether your protections are adequate. That judgement, and the approval, stay with you.

For context: our own SOC 2® Type II observation window ran from 27 March to 27 June 2026, on AuditBadger, with no external consultants. Draw the six arrows first. The rest of the system description gets much easier once you have.

