Updated
A PCI DSS assessment, a SOC 2 audit and an as-built handover ask for the same few things: a diagram that matches the network, a list of what's on it, a record of what changed, and a date someone checked. NetworkSketch produces all of them as one PDF, from one diagram, so they can't drift apart.
| The ask | Where you'll hear it | In NetworkSketch |
|---|---|---|
| An accurate network diagram showing every connection into and out of the sensitive environment, including wireless | PCI DSS 4.0 requirement 1.2.3; SOC 2 system descriptions and network security controls; customer security questionnaires | Devices with hostnames and IPs, VLAN and zone areas with their subnets, every cable with ports and media type. Put the cardholder data environment in its own zone so its boundary is visible. |
| A diagram of how sensitive data flows | PCI DSS 4.0 requirement 1.2.4 | Add a page with Data Flow lines between the systems that handle the data, each recording what it carries, its classification and its encryption, inside trust boundaries. Multi-page documents keep the physical and data-flow views together. More on data flow diagrams, with SaaS and contact center examples. |
| An inventory of system components in scope | PCI DSS 4.0 requirement 12.5.1; SOC 2 asset management | The PDF's device inventory: hostname, type, vendor and model, serial, management IP, area and location. The CSV adds MAC address, asset tag and OS version. |
| Proof the diagram is current | Every assessor's first follow-up question | Verified name and date in the title block (Document Settings, Mark verified today), printed on every page. |
| A record of changes | PCI DSS change control (requirements 1.2.2 and 6.5.1); SOC 2 change management (CC8.1) | The change log: date, who and what changed, with your ticket number. It prints as its own page in the PDF. |
| Subnets and VLANs, and what's segmented from what | Segmentation testing (PCI DSS 11.4.5); firewall rule reviews | The VLAN/subnet table, built from your areas: VLAN ID, name, subnet, gateway, DHCP and how many devices are in it. The network check flags IPs outside their subnet and duplicates across pages. |
| Cabling records: labels, lengths and test results | As-built handovers (ANSI/TIA-606 labeling, BICSI practice); landlord and customer acceptance | The cabling schedule: both ends with ports, media, speed, cable ID, length and certification test result. Also as a CSV. |
Requirement numbers are from PCI DSS v4.0.1 and the 2017 AICPA Trust Services Criteria. Your assessor decides what satisfies them; use this as a checklist, not a guarantee.
The editor runs in your browser and diagrams are saved as files on your computer. Your topology isn't stored on our servers, so there's no third party to add to your vendor list or questionnaire. Security details.
One PDF with the diagram, inventory, cabling schedule, VLAN table and change log, each page carrying the same title block and verified date. Attach it to the audit request as is.
The diagram is a plain, documented JSON file. Store it next to your policies, in SharePoint or Git, and keep every version you handed an auditor.
Start from a template, paste a device list from a spreadsheet, or import from SolarWinds Orion. Put each VLAN or zone in an area with its subnet.
When a change ticket touches the network, update the diagram and add a change log line with the ticket number.
Run the network check, walk the diagram against the real network on your review schedule, then Mark verified today and export the PDF.
No tool does. Compliance depends on your controls and your assessor. NetworkSketch helps you produce and keep current the network diagram, inventory and change history those audits ask to see.
No. The editor runs in your browser and diagrams are saved as files on your computer. There is no server copy, so we aren't another vendor holding your cardholder-environment topology.
PCI DSS 4.0 asks for an accurate diagram, so it has to change whenever connections into or out of the cardholder data environment change, and be reviewed as part of the regular review of network security controls. Record each change in the change log and mark the diagram verified after each review.
Yes. Keep one file per client site, put the client's name and address in the title block, and hand over the PDF at each review. Your files stay in your own document system.
Open the editor and start from a template. Exports need the 14-day free trial (no card) or a plan.
Open the editor