Separate Video Conferencing and IP Telephony Traffic From Other Data
Keep video conferencing and internet phone (IP telephony) traffic separated, either by physical cabling or by logical network controls, from your normal data traffic.
Plain language
This control says your video calls and internet-based phone calls (IP telephony, meaning phone calls carried over your computer network rather than a traditional phone line) should travel on their own part of the network, kept apart from your everyday data like emails, files and web browsing. You can do this physically (separate cables and equipment) or logically (using network settings such as a separate virtual network). Separating this traffic protects call quality and stops a problem on one part of the network from spilling over and exposing or disrupting your calls.
Framework
ASD Information Security Manual (ISM)
Control effect
Preventative
Classifications
NC, OS, P, S, TS
ISM last updated
June 2026
Control Stack last updated
18 June 2026
E8 maturity levels
N/A
Topic
Traffic SeparationOfficial control statement
Video conferencing and IP telephony traffic is physically or logically separated from other data traffic.
Why it matters
If video and IP telephone traffic shares the same network as general data, a breach or overload on the data network can intercept, degrade or knock out calls, and vice versa.
Operational notes
Re-check the separation whenever phones, video units or network hardware are added or replaced, and confirm new devices land on the correct voice/video segment rather than the data network.
Implementation tips
- The IT team should set up a separate virtual network, called a VLAN (virtual local area network, a way to split one physical network into isolated logical sections), and place all video conferencing and IP telephony devices on it so their traffic does not mix with general data traffic.
- The IT team or network provider should configure the network switches and routers so that traffic from phones and video units is tagged and routed on its own segment, and confirm general computers cannot reach the voice and video segment without authorisation.
- The business owner or office manager should ask the supplier who installed the phone or video system to confirm in writing whether the separation is physical (its own cabling and hardware) or logical (separate VLAN), and keep that confirmation on file.
- The IT team should apply traffic priority settings, known as Quality of Service, on the separated voice and video network so calls stay clear and uninterrupted even when the data network is busy.
- The IT team should document the network design in a simple diagram showing the voice and video segment kept apart from the data segment, and review it whenever new phones, video units or network equipment are added.
Audit / evidence tips
- Aska current network diagram and the configuration of the switches or routersLook atwhether video conferencing and IP telephony devices sit on a separate segment or VLAN from general computersGoodshows a clearly labelled voice/video segment distinct from the data network
- Askhow the separation is achieved, physically or logicallyLook atcabling records or VLAN configuration filesGoodnames the specific method (for example, dedicated cabling, or a named VLAN with its ID) rather than a vague claim that traffic is 'kept apart'
- Askto see the access rules between the voice/video segment and the data segmentLook atfirewall or switch rules that control traffic between themGoodshows that general data devices cannot freely reach the voice and video network without explicit, authorised rules
- Askevidence that the separation is tested or verifiedLook atnetwork scans, port tests or a supplier's commissioning reportGoodincludes a dated test result confirming the segments are isolated as designed
- Askhow the design is kept current when equipment changesLook atchange records and an updated diagramGoodshows the diagram and configuration were reviewed after the most recent phone, video or network change
Cross-framework mappings
How ISM-0549 relates to controls across ISO/IEC 27001, ISO/IEC 42001, Essential Eight, and ASD ISM.
ISO 27001
| Control | Notes | Details |
|---|---|---|
layersPartially meets(1)expand_less | ||
| Annex A 8.22 | ISM-0549 requires video conferencing and IP telephony traffic to be separated physically or logically from other data traffic | |
These mappings show relationships between controls across frameworks. They do not imply full equivalence or certification.
Related ASD ISM controls in Communications systems
See all Guidelines for communications systems controls, or browse the full ASD ISM library.