A data flow diagram that shows where your sensitive data goes — OC Security Audit
Data-flow diagrams

A data flow diagram that shows where your sensitive data goes

Patient records, card data and taxpayer files: where they enter, which systems touch them, where they are stored, which vendors receive them and where they are encrypted.

The diagram auditors and risk assessors ask for first — OC Security Audit
PCI DSS, HIPAA, IRS WISP

The diagram auditors and risk assessors ask for first

PCI DSS Req. 1.2.4 names it outright, and HIPAA risk analysis and a WISP both depend on knowing where the data lives.

A diagram that changes when your systems change — OC Security Audit
Kept current

A diagram that changes when your systems change

New software, a new vendor or a cloud move adds a data path. Tying the diagram to change records keeps it accurate.

25+ yearsIT & cybersecurity experience
Certified expertsCISSP · C|CISO · Microsoft · Cisco
Southern CaliforniaLocal and on-site, based in Irvine
NationwideRemote documentation & audits
What it is

Follow the data, not the cables

A data flow diagram shows how a specific kind of sensitive data moves through your business: where it enters, which systems process it, where it is stored, which networks and vendors it crosses, and where it is protected. It answers the question every regulator, auditor and cyber insurer eventually asks: where is our sensitive data, and who can reach it?

Most businesses can name their main system for patient, card or client data. Few can name every copy: the scanned intake forms, the export a staff member emails to the billing service, the backup that replicates to the cloud, the vendor portal that pulls records every night. Those copies are where breaches and audit findings tend to start.

The diagram builds on the network documentation and the IT asset inventory: each box is a documented system, and each arrow crosses a documented network.

Team discussing how data flows between business applications
Two different drawings

Data flow diagram vs network diagram

They look similar and often share boxes, but they answer different questions. Most audits need both.

QuestionNetwork diagramData-flow diagram
What does it follow?Devices, links, subnets and VLANsOne type of data: patient records, card data, taxpayer data
What does an arrow mean?A physical or logical connectionData moving from one place to another, in one direction
What does it include beyond your network?ISP circuits and cloud network linksVendors, clearinghouses, payment processors, cloud apps, email and people
Where is protection shown?Firewalls and segmentation zonesEncryption in transit and at rest, and trust boundaries
PCI DSS v4.0.1 requirementReq. 1.2.3: all connections to the cardholder data environmentReq. 1.2.4: all account data flows across systems and networks
Frameworks

Why frameworks ask for a data flow diagram

The diagram is evidence that supports your compliance program. It does not by itself make you compliant with any framework.

FrameworkWhat it saysHow the diagram helps
PCI DSS v4.0.1 Req. 1.2.4An accurate data-flow diagram showing all account data flows across systems and networks, updated as needed upon changesShows the assessor every path card data takes, and therefore what is in scope
HIPAA 45 CFR 164.308(a)(1)(ii)(A)An accurate and thorough assessment of risks and vulnerabilities to the confidentiality, integrity and availability of ePHI held by the covered entity or business associateYou cannot assess risk to ePHI you have not located; the diagram shows every ePHI path
IRS WISP (Gramm-Leach-Bliley Act)The IRS says federal law requires tax and accounting professionals to maintain a Written Information Security Plan, including identifying and assessing risks to customer informationShows where taxpayer data is stored and sent, for the WISP’s risk section
NIST CSF 2.0 ID.AM-03Representations of the organization’s authorized network communication and internal and external network data flows are maintainedThe data-flow diagram is that representation, with a date and review record

Our compliance services cover each one: HIPAA compliance, PCI DSS readiness and IRS WISP compliance. The full mapping is on IT documentation for compliance.

What to show

Six things every data-flow diagram should show

Leave any one out and the diagram has a blind spot.

01

Entry points

Every way the data arrives: front-desk intake, patient portal, card terminal, e-commerce page, email, scanned paper, a vendor feed.

02

Systems that process it

Applications and servers that read or change the data, named exactly as in the asset inventory.

03

Storage locations

Databases, file shares, NAS devices, cloud storage, backups and local copies on workstations, each with its location.

04

Transmissions

Each arrow labeled with the method: application protocol, file transfer, email, VPN tunnel, API, removable media.

05

Third parties

Clearinghouses, payment processors, billing services, cloud backup, IT providers: who receives the data and under which agreement.

06

Encryption and trust boundaries

Where data is encrypted in transit and at rest, and the lines where it leaves your control or crosses into a less trusted zone.

Sample

Sample patient-data path: Harborview Dental Group

One ePHI flow from the fictional practice, simplified to its main path. A full diagram adds every branch.

Front-desk intake

Forms entered on front-office PCs, VLAN 20

SRV-PM-01

Practice-management server, VLAN 30, encrypted disk

Imaging

Sensors on VLAN 10 save X-rays to the chart

NAS-BK-01

Nightly encrypted backup, VLAN 30

Cloud backup

Encrypted copy over VPN-HQ-CLOUD

Claims clearinghouse

Claims sent over TLS · third party

All names and paths are fictional. Each box links to its asset record, and each arrow to the network and firewall rule that carries it.

Sample

Sample data-flow register behind the diagram

The drawing is easy to read; the register holds the detail an auditor checks.

SAMPLE · Harborview Dental Group (fictional company) · illustrative data
FlowFrom → ToDataMethodEncryptionOwner
DF-01Front-office PCs → SRV-PM-01Demographics, insurance, historyPractice-management appApplication encryption per vendor; crosses FW-HQ-01Office manager
DF-02Imaging sensors → SRV-PM-01X-ray imagesImaging softwareStored on encrypted diskLead dentist
DF-03SRV-PM-01 → NAS-BK-01Full database backupBackup job, nightlyEncrypted at restIT
DF-04NAS-BK-01 → cloud backupBackup copySite-to-cloud VPNTunnel plus encrypted backupIT
DF-05SRV-PM-01 → claims clearinghouseClaims dataVendor portalTLSBilling lead
DF-06Front-office PC → emailReferral lettersEmail attachmentNot documentedFlagged for review

DF-06 is a typical finding: a real data path nobody had drawn. All values are fictional.

Keeping it current

Keep the data flow diagram current with change management

PCI DSS Req. 1.2.4 expects the diagram to be updated as needed upon changes. These events should trigger an update in the change record.

  • A new application, integration or patient or client portal
  • A new vendor that receives sensitive data, or a vendor contract that ends
  • A move to the cloud, a new backup target or a new storage location
  • Changes to the network segments or firewall rules that carry the data
  • A new office, a closed office or a merger
  • A scheduled review, at least annually, with the date and reviewer recorded

Our IT change management page shows how a change record includes the documentation update as a required step.

How we help

Data-flow diagrams reviewed or built with your team

The IT Documentation Audit reviews any data-flow diagrams you have against the systems and vendors actually in use. The IT Documentation Build delivers the diagram and the register behind it, built from interviews with the people who handle the data and from your system configuration. Each package is $3,500 fixed, one-time; see IT documentation pricing.

Ali works on-site across Orange County and Southern California from Irvine, and remotely nationwide, for dental and medical practices, CPA and tax firms, law offices and other businesses that handle sensitive data. The work is read-only; IT Perfection can handle any fixes.

Colleagues reviewing a data-flow diagram on a laptop
Related

Where to go next

Network documentation

L1, L2 and L3 diagrams, segmentation zones and device records for the networks your data crosses.

IT documentation for compliance

What HIPAA, PCI DSS, NIST CSF and insurance questionnaires expect you to have on file.

Ali Hassani, CISO, OC Security Audit
CISO-led

Guided by Ali Hassani, CISO

Certified CISO (C|CISO) and CISSP with 25+ years in IT, cybersecurity, compliance and infrastructure, and dozens of Microsoft and Cisco certifications, including MCSE, MCITP, MCSA Security, CCNP and CCNA. Ali builds each data-flow diagram from interviews with the people who handle the data, then confirms every path against the systems themselves.

FAQ

Questions about data flow diagrams

Do we need one data-flow diagram or several?

Usually one per type of sensitive data: patient records, card data, taxpayer data. Combining them makes each harder to read and to review.

We do not store card numbers. Do we still need a card data flow?

If card data passes through your terminals or network, those account data flows belong on the diagram under PCI DSS Req. 1.2.4. A clear diagram also makes the scope discussion with your assessor or payment processor easier.

Does HIPAA require a data-flow diagram by name?

The HIPAA Security Rule requires an accurate and thorough risk analysis for ePHI. A data-flow diagram is one of the clearest ways to show where ePHI lives so the analysis is complete.

What tools do you use to draw the diagram?

Any standard diagramming tool your team can edit. We deliver editable files plus printable versions, in your documentation platform or our encrypted documentation package.

Who should own the diagram?

A named person who knows the business process, often the practice manager or compliance lead, with IT confirming the technical paths. We record the owner and review date on the diagram.

Implementation partner

OC Security Audit documents and audits; it stays independent of the administration of your systems. If you want hands-on work, IT Perfection can fix what the documentation uncovers and keep the records current as part of managed IT.

IT Perfection managed IT
Business owner and colleague discussing documentation audit findings

Find every place your sensitive data goes

Tell us which data you handle and which systems hold it. Schedule a consultation and we will scope the diagram on a 30-minute call.

Irvine, Orange County and Southern California on-site; remote nationwide. Fixed one-time price: $3,500.