What to include in IT documentation: 13 domains, one record — OC Security Audit
What to document

What to include in IT documentation: 13 domains, one record

From vendor contacts and rack layouts to firewall rule justifications and change records: what to write down, who owns it and how often to review it.

Every record needs a named owner and a review date — OC Security Audit
Owners and review cycles

Every record needs a named owner and a review date

Documentation goes stale when nobody owns it. Each domain below lists a sensible owner and a review cadence you can adopt.

Find out how your documentation scores — OC Security Audit
Already have documentation?

Find out how your documentation scores

Our IT Documentation Audit scores what you already have against all 13 domains and returns a prioritized 0–60 day roadmap.

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

What to include in IT documentation: 13 domains that describe how your IT works

Deciding what to include in IT documentation is the first decision in any documentation project, and the one most often skipped. Teams start with a network diagram, run out of time, and never record the circuit IDs, the reason behind each firewall rule or the order in which systems must be restored.

We use 13 domains, from ownership and vendors to change records. Together they answer the questions every outage, staff change and audit raises: what you have, where it is, how it connects, who supports it, how to recover it and what changed. Every audit we perform is scored against these domains, and every build documents them.

Each domain below lists what to record, who should own it and how often to review it, with a link to the page that covers it in depth. OC Security Audit works on-site from Irvine across Orange County and Southern California, and remotely nationwide.

IT staff reviewing system details on a laptop in a server room
How to read this page

Owners, review frequency and the CIS 12.4 baseline

Owner means the role accountable for the record being correct, not necessarily the person who types it. Name a person for each domain; “IT” is not an owner. Where an MSP maintains the record, a person inside your company should still own it.

Review sets the floor. CIS Controls v8.1 Safeguard 12.4 asks organizations to establish and maintain architecture diagrams and other network system documentation, and to review and update them annually or when significant enterprise changes occur. We apply that baseline to the network-related domains. Every other cadence in the tables is our recommendation; adjust it to your risk, your size and the frameworks you answer to.

Domains 1–4

Foundation: who, where and how it connects

Start here. Without owners, sites and a topology, every other record has nothing to attach to.

DomainWhat to recordOwnerReview
1. Ownership and vendors
IT asset inventory
A system owner for every application and device; MSP, ISP, software and hardware vendors; support lines and account references; contracts with renewal and end dates; who may open tickets and approve vendor work.Operations manager or practice administratorQuarterly and at each contract renewal (recommended)
2. Sites and physical
How to document a network
Addresses and after-hours access; server rooms and closets; rack elevations; patch panel and port maps; cabling labels; power circuits and UPS units with the last runtime test; rack photos.IT lead or MSPAnnually or after a move or re-cabling (CIS 12.4)
3. Network topology
Network documentation
Physical (Layer 1), switching and VLAN (Layer 2) and routing (Layer 3) diagrams; wireless SSIDs, security settings and access point placement; segmentation between clinical, office, guest and server networks.IT lead or network engineerAnnually or after significant change (CIS 12.4)
4. IP addressing
IP address and VLAN documentation
Prefixes and subnets with their purpose; VLAN IDs and names; gateways; DHCP scopes and reservations; static IPs; internal DNS zones and key records; public IPs and NAT mappings.Network engineer or MSPAt every change; full reconciliation annually (CIS 12.4)
Domains 5–8

Connectivity, security and platforms

These records are what your team reaches for during an outage, and what an auditor asks about first.

DomainWhat to recordOwnerReview
5. WAN and internet
WAN and ISP circuit documentation
For each circuit: provider, circuit ID, bandwidth, handoff type and location, static IP block, SLA and support line. SD-WAN or MPLS design, site-to-site VPN peers and protected subnets, failover design and its last test date.IT lead; finance holds the contractAt each circuit change; annually (CIS 12.4)
6. Security devices and settings
Firewall configuration documentation
The firewall rule base with a business justification and requester for each rule; NAT; remote access VPN; IDS/IPS settings; management access paths; firmware versions; golden configurations; configuration backup location and schedule.Network or security leadAt every rule change; full rule review annually (recommended)
7. Servers and identity
Active Directory security audit
Active Directory forests and domains; domain controllers and FSMO role holders; Group Policy objects and their purpose; service accounts; server roles; hypervisor hosts and virtual machines; backup jobs, retention and restore tests.Systems administrator or MSPPrivileged groups quarterly; the rest annually (recommended)
8. Cloud
Cloud documentation
Microsoft 365 and Entra ID: domains, Conditional Access policies, admin role holders, break-glass accounts. Azure: subscriptions, VNets, NSGs, Key Vault. AWS: accounts, VPCs, security groups. A SaaS inventory with owner and sign-in method.Microsoft 365 or cloud administratorAdmin roles and Conditional Access quarterly and after each policy change (recommended)
Domains 9–11

Assets, access and sensitive data

These domains connect your technology to money, people and regulated data.

DomainWhat to recordOwnerReview
9. Assets
IT asset inventory
Hardware and software with model, serial, version, location, assigned user, owner, purchase date, warranty end and end-of-life or end-of-support date. Systems past end of support with a replacement or isolation plan.IT lead; finance for purchase recordsReconcile against discovery monthly; full review annually (recommended)
10. Credentials and secrets
IT password documentation
An index of admin and service accounts that points to vault entries, never the passwords themselves; break-glass accounts and where their secrets are sealed; rotation dates; who can view each entry.IT lead; break-glass held by an executiveAt every staff departure; rotation per your policy (recommended)
11. Data flows
Data-flow diagrams
Where patient, card and taxpayer data is created, stored, sent and backed up; the systems, vendors and connections it crosses; encryption in transit and at rest for each flow.Compliance or privacy officer, with ITAnnually and when a system or vendor handling the data changes (recommended)
Domains 12–13

Operations: how work gets done and recorded

The last two domains keep the other eleven accurate. Without change records, every other document starts to drift from the day it is written.

DomainWhat to recordOwnerReview
12. Procedures and recovery
Runbooks and disaster recovery
Runbooks for routine and emergency tasks; SOPs; onboarding and offboarding steps; restore order for critical systems; disaster recovery and business continuity plans; a contact and escalation tree that works when email is down.IT lead with the operations managerAnnually, after each DR test and after any incident (recommended)
13. Change records
IT change management
For each change: request, risk rating, approval, implementation date and person, test result, rollback plan, and the before-and-after configuration difference.Change approver (owner or IT manager)Each change at closure; sample review monthly (recommended)
Sample

What one complete record looks like

A single network from the IP addressing domain, documented with owner, review date and links to the other domains.

SAMPLE · Harborview Dental Group (fictional company) · illustrative data
Record
VLAN 20 · Front office · Irvine office
Prefix and gateway
10.20.20.0/24 · gateway 10.20.20.1 on FW-HQ-01
DHCP
Scope 10.20.20.100–10.20.20.199 served by FW-HQ-01 · statics below .100
Devices
6 PCs · 8 IP phones · 1 check scanner · served by access switch SW-ACC-02
Open issue
Duplicate static 10.20.20.45 on a front-office PC and a label printer
Owner
Office manager (accountable) · MSP technician (maintains)
Last reviewed
14 Oct 2026 · next review Oct 2027 or at the next significant change
Change history
CHG-0139 · DHCP scope extended to .199 · approved and tested 2 Sep 2026

The same fictional practice appears across the sample documentation package, where you can see the full IP/VLAN table, circuit register and change log.

One more thing to document

Protect the documentation itself

A complete record of your network is valuable to an attacker too. Put the documentation platform behind MFA or single sign-on, use role-based access, keep secrets out of open text fields, turn on the audit log of views and edits, and keep an encrypted offline export for recovery. Details are on securing your IT documentation.
Next steps

Turn the 13 domains into a plan

Related

Where to go next

IT documentation checklist

Sixty-five items across the 13 domains, so you can see in minutes which records you are missing.

IT documentation software compared

Where each domain can live: documentation hubs, network sources of truth, vaults and change tools.

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 scores every engagement against these 13 domains so owners, auditors and engineers read the same structure.

FAQ

Questions about what to include in IT documentation

Do we need all 13 domains?

Most businesses with a network, cloud services and sensitive data need all 13, but the depth varies. A single-site office may cover sites and WAN in a page each; a multi-site practice needs more.

How often should IT documentation be reviewed?

CIS Controls v8.1 Safeguard 12.4 sets annual review, or review after significant change, for network documentation. The other cadences on this page are recommendations; the most reliable habit is updating the record as part of every approved change.

Should passwords be in the documentation?

No. Keep passwords and keys in an encrypted vault and record only a reference to the vault entry, plus the owner and rotation date.

Who should own the documentation if we use an MSP?

The MSP can maintain it, but a named person in your company should own each domain and have access to the record without asking the provider.

Where do we start if we have nothing?

Start with domains 1, 3, 5 and 10: owners and vendors, a network diagram, circuit details and a credential index. Those are the records teams reach for first in an outage. Our IT Documentation Build covers all 13.

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
Hands reviewing printed documentation with a pen and calculator

Get all 13 domains documented

Tell us what you have today and we will recommend the audit or the build, each $3,500 fixed, one-time. Schedule a consultation.

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