If you use VoIP, manage it as a real system — secured, restricted, and monitored.
What it actually means
Voice over IP introduces network risk. Control and monitor it: restrict who can use it, secure the configuration, segment voice traffic where practical, and monitor for misuse. If you don't use VoIP, document that it's not applicable.
Pass or fail — an assessor needs a "yes" to each
- Is VoIP usage authorized, secured, and monitored (or documented as not used)?
- Is voice traffic segmented or restricted where practical?
What to have ready
- VoIP configuration and monitoring evidence
- Network segmentation for voice, or an N/A justification
Where teams trip up
- Treating the VoIP system as out of scope without documenting why
- Default, unhardened VoIP configurations
See where this control puts your score
Run all 110 requirements free in about 10 minutes — or draft your SSP language for this control. No signup.
Calculate your SPRS score →Draft your SSP language →Connected requirements
More in System & Communications Protection (3.13)
3.13.1 — Protect your boundaries3.13.2 — Build security in by design3.13.3 — Separate user and admin functions3.13.4 — Stop data leaking through shared resources3.13.5 — Wall off your public-facing systems3.13.6 — Deny all, permit by exception3.13.7 — Block split tunneling on VPNs3.13.8 — Encrypt CUI in transit3.13.9 — Drop idle network sessions3.13.10 — Manage your encryption keys3.13.11 — FIPS-validated cryptography3.13.12 — Control cameras and microphones3.13.13 — Control mobile code3.13.15 — Protect session authenticity3.13.16 — Encrypt CUI at rest