Separate Video Call Traffic from Other Data
Keep video calls and internet phone traffic apart from regular data for security.
Plain language
Conducting video calls and making internet-based phone calls on the same network as regular internet activities can lead to disruptions and security risks. This control suggests keeping them separate, either physically or virtually, to maintain their quality and safeguard sensitive information from being accessed or slowed down by other internet traffic.
Framework
ASD Information Security Manual (ISM)
Control effect
Preventative
Classifications
NC, OS, P, S, TS
ISM last updated
Sept 2019
Control Stack last updated
19 Mar 2026
E8 maturity levels
N/A
Guideline
Guidelines for communications systemsTopic
Traffic SeparationOfficial control statement
Video conferencing and IP telephony traffic is separated physically or logically from other data traffic.
Why it matters
Without separating VoIP and video call traffic, these streams can be intercepted or disrupted, reducing confidentiality and call quality/availability.
Operational notes
Regularly review VLAN/VRF and QoS settings to keep VoIP/video on dedicated segments, and investigate any mixed traffic or routing leaks promptly.
Implementation tips
- IT team should physically separate network infrastructure: Set up distinct hardware, such as different routers, for video calls and phone traffic to prevent interference with other internet activities. This can be done by installing a separate line dedicated solely to handling your call traffic.
- System administrator should configure logical network separation: Use network settings to virtually split your traffic. Implement VLANs (Virtual Local Area Networks), which can segment your calls from other data without needing physical wires, if new hardware isn’t feasible.
- Business manager should prioritise resources for traffic separation: Ensure your IT budget accounts for bringing in either new hardware or software solutions that facilitate this separation. Discuss with your IT provider or team about the costs and tools available for securing video and call traffic.
- Procurement officer should liaise with service providers: Contact your internet and telephony service providers to discuss dedicated services for handling video traffic separately. They can offer solutions or accounts that keep all types of traffic efficiently separated.
- IT lead should monitor and maintain separated networks: Regularly review your systems to make sure the separation remains effective. Use monitoring tools, which give alerts if traffic starts to mix, so that any issues can be rapidly addressed.
Audit / evidence tips
- AskNetwork design documentation: Request diagrams or documents showing how the network is split to separate video calls and phone data from other internet data GoodClear separation indicated, with no crossover between different network streams
- GoodSeparate logs confirming different paths and no mingling data
- GoodClear terms that indicate service providers segregate traffic on their backend
- AskMonitoring and performance reports: Request reports that detail the performance of the separated networks over time GoodConsistent metrics showing stable and isolated performance for video/call traffic
- GoodA regular, documented practice of reviews ensuring configurations remain effective and up-to-date
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 |
|---|---|---|
| layers Partially 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.