IT documentation audit: know what is missing before it costs you — OC Security Audit
Read-only review · $3,500 fixed, one-time

IT documentation audit: know what is missing before it costs you

We review the documentation you already have, score it against 13 domains and hand you a prioritized roadmap to close the gaps.

A domain scorecard that shows exactly where you stand — OC Security Audit
Scored, not guessed

A domain scorecard that shows exactly where you stand

Each of the 13 domains is rated Complete, Partial, Missing or Out of date, with the evidence behind every rating.

We read. We never change your systems. — OC Security Audit
Read-only

We read. We never change your systems.

Read-only access and no configuration changes. Your team or your MSP stays in control of every system.

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

What an IT documentation audit covers

An IT documentation audit is a read-only review of the documentation you already have: network diagrams, the IP plan, WAN circuit records, firewall rule records, cloud settings records, how your password vault is used and how changes are recorded. We compare each record to what is actually in place and score it against 13 documentation domains.

Read-only means exactly that. We look at documents, consoles and exports with read access you grant, and we never change a setting, rule or account on your systems. The result is a clear picture of what an engineer, an auditor or an insurer would find if they asked for your records today.

OC Security Audit is based in Irvine and works on-site across Orange County, Los Angeles County and Southern California, and remotely nationwide. The audit is $3,500 fixed, one-time.

Business owner and colleague discussing documentation audit findings
What we check

The 13 domains we review in every IT documentation audit

The domains follow our guide to what to include in IT documentation.

DomainWhat we checkGaps we look for
1. Ownership and vendorsNamed owner per system, vendor and support contacts, contract datesSystems with no owner; vendors with access nobody can name
2. Sites and physicalRooms, racks, cabling, power and access for each siteUnlabeled patch panels; no rack elevations
3. Network topologyL1, L2 and L3 diagrams, wireless, segmentationDiagram older than the last major change; segments missing
4. IP addressingPrefixes, VLANs, DHCP scopes and reservations, static IPs, DNS zones, public IPs, NATStatic IPs found on the network but not in the plan
5. WAN and internetProvider, circuit ID, bandwidth, handoff, static block, SLA, support line, VPN peers, failoverA circuit in service but missing from the register
6. Security devices and settingsFirewall rules with business justification, NAT, remote access VPN, management access, firmware, config backupsRules with no reason or owner; no recent backup
7. Servers and identityActive Directory, domain controllers, FSMO roles, GPOs, server roles, hypervisors, backupsRole holders and backup jobs not recorded
8. CloudMicrosoft 365 and Entra ID domains, Conditional Access, admin roles, break-glass accounts; Azure and AWS networks; SaaS inventoryConditional Access policies undocumented; SaaS apps nobody listed
9. AssetsHardware and software with owner, warranty and end-of-life dateInventory that does not match what discovery finds
10. Credentials and secretsVault references only, break-glass process, rotation recordsPasswords in documents, spreadsheets or tickets
11. Data flowsWhere PHI, card data or taxpayer data is created, stored and sentNo data-flow diagram for the regulated data
12. Procedures and recoveryRunbooks, SOPs, onboarding and offboarding, restore order, DR/BCP, contact treeA restore order nobody has tested or written down
13. Change recordsRequest, risk, approval, implementation, test, rollback, before-and-after diffChanges made with no ticket or approval

We also check how the documentation itself is protected: MFA or SSO on the platform, role-based access, no secrets in notes or page text, an audit log of views and edits and an encrypted offline export. See securing your IT documentation.

How we score

Four ratings for each domain

Every rating comes with the evidence we saw, so you can check our work.

01

Complete

The record exists, matches what is in place, has an owner and was reviewed recently enough for its purpose.

02

Partial

The record exists but leaves out sites, systems or fields an engineer or auditor would need.

03

Missing

No record exists, or it lives only in one person’s memory or inbox.

04

Out of date

The record exists but no longer matches the environment, or has no review date.

Change-process review

We trace recent changes from request to updated record

Documentation goes stale through changes, so we review the change process as its own finding.

We pick a set of recent changes to firewalls, switches, cloud settings and accounts, then trace each one: was there a request, a risk note, a named approver, a test, a rollback plan and a before-and-after configuration? Was the diagram, IP plan or rule register updated afterward?

The result is a change-process gap list that shows where the trail breaks. Our pages on IT change management and network change management tools explain what a complete trail looks like.

Sample

A sample finding and scorecard

SAMPLE · Harborview Dental Group (fictional company) · illustrative data
Finding
HDG-F-07 · Domain 5, WAN and internet · Out of date
Evidence
The circuit register lists one circuit at the Irvine office (Fiber ISP A, HDG-FIB-0412). Firewall FW-HQ-01 shows a second WAN interface on a Cable ISP B link with no register entry, no support line and no addressing recorded.
Why it matters
During an outage, staff would not know the backup link exists, who to call or which public IPs it uses.
Recommendation
Add the circuit to the register with provider, circuit ID, bandwidth, handoff, addressing and support line; mark it as the failover path in the diagram.
Roadmap
0–7 days
DomainRatingDomainRating
1. Ownership and vendorsPartial8. CloudMissing
2. Sites and physicalPartial9. AssetsOut of date
3. Network topologyOut of date10. CredentialsPartial
4. IP addressingPartial11. Data flowsMissing
5. WAN and internetOut of date12. ProceduresPartial
6. Security devicesPartial13. Change recordsMissing
7. Servers and identityComplete

See how the finished records look in the sample documentation package, including the WAN circuit register.

Deliverables and price

What you receive

Both packages are $3,500 fixed, one-time. A common path is to start with the audit and decide on the build after the read-out.

Read-only review

IT Documentation Audit

$3,500
Fixed price · one-time fee

A scored review of your existing documentation and change process against the 13 domains.

  • Executive report in plain language
  • Technical findings with evidence
  • Domain scorecard for all 13 domains
  • Change-process gap list
  • Prioritized roadmap: 0–7, 8–30 and 31–60 days
  • Read-out meeting
Discovery and documentation

IT Documentation Build

$3,500
Fixed price · one-time fee

We produce the missing records and deliver them in your platform or an encrypted documentation package.

  • Network and data-flow diagrams
  • IP/VLAN plan and WAN circuit register
  • Firewall rule-justification register
  • Cloud settings record, asset inventory and credential index
  • Runbooks and change-log template
  • Walkthrough session and 30-day correction window
How it works

Five steps from scoping call to roadmap

STEP 1

Scoping call

A 30-minute call to confirm sites, systems, platforms and any upcoming audit or renewal. The price stays $3,500.

STEP 2

Read-only access

You share existing documents and grant read-only access to the consoles and exports we need.

STEP 3

Review and score

We compare each record to what is in place and rate all 13 domains.

STEP 4

Report

Executive report, technical findings, scorecard, change-process gap list and roadmap.

STEP 5

Read-out

We walk owners and IT through the findings and the 0–7, 8–30 and 31–60 day priorities.

OC Security Audit documents and audits; it does not administer client systems. Fixes can go to your IT team, your MSP or our implementation partner, IT Perfection. Ongoing quarterly review can be part of our vCISO service.
Who it is for

When an IT documentation audit pays off

The audit is most useful at a moment of change, when someone new needs to rely on the records.

01

New IT manager

Know what you inherited, and what is undocumented, in your first weeks rather than during your first outage.

02

Changing MSPs

Confirm what documentation the outgoing provider holds and what you own before the transition.

03

Before an audit

Find gaps before a HIPAA, PCI DSS, SOC 2 or ISO 27001 assessment. See the framework mapping.

04

Before insurance renewal

Check that your questionnaire answers match what your records show. Pairs with our cyber insurance readiness assessment.

05

After an incident

Find out which records were missing or wrong when the team needed them, and fix that first.

06

Mergers and acquisitions

Understand the IT environment you are buying or combining, documented to the same standard across both.

Related

Where to go next

IT documentation pricing

Both packages, what each includes and what is not included.

IT documentation checklist

Run a quick self-check against the same 13 domains before you call.

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. Audits are CISO-led and end with a read-out meeting, so findings come with the context behind them.

FAQ

Questions about the IT documentation audit

What does read-only mean in practice?

We view documents, consoles and configuration exports with read access you grant. We never change settings, rules or accounts, and you can remove our access when the review ends.

How is this different from a security audit?

A security audit tests how well systems are protected. An IT documentation audit tests whether your records describe those systems accurately and completely. Our security audits cover the first.

We have almost no documentation. Should we start with the build instead?

Possibly. If most domains would score Missing, the build may be the better first step. We will tell you which fits on the scoping call.

Will the audit make us compliant?

No. It shows where your documentation supports your compliance program and where it falls short. Closing the gaps and passing an assessment are separate steps.

Can our MSP be involved?

Yes. Including your MSP means the findings and roadmap go directly to the people who will act on them.

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
Leadership team meeting to discuss why accurate IT records matter

Find out where your documentation stands

A read-only review, a scored report and a clear roadmap for $3,500 fixed, one-time. Schedule a consultation.

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

Need the whole environment reviewed? The Internal Security Audit covers physical, logical and administrative controls for a fixed $3,500.