✔️Security & Compliance
Implement security policies, enable encryption, manage call blocking, and ensure compliance with regulatory requirements for your Zoom Phone deployment.
⏱️ Estimated Time: 20-30 minutes to configure security settings
👤 Who's This For
Zoom Phone administrators responsible for security, compliance, and data protection policies.
💼 Use Case
Use this guide to harden your phone system security, protect sensitive communications, comply with industry regulations (HIPAA, SOC 2, etc.), and prevent unauthorized access or fraud.
✔️ Prerequisites
Admin access to Zoom web portal
Understanding of your organization's security and compliance requirements
Knowledge of applicable regulations (HIPAA, GDPR, etc.)
Emergency address information for all locations
Encryption & Call Security
Standard Encryption
All Zoom Phone calls use AES-128 bit encryption by default for:
Connections between Zoom Cloud and Zoom clients
Desktop app calls
Mobile app calls
Desk phone calls (supported SIP devices)
Note: Encryption is always enabled and cannot be disabled. This provides baseline security for all communications.
End-to-End Encryption (E2EE)
Enable E2EE for maximum call privacy. With E2EE, only call participants can decrypt audio—not even Zoom can access call content.
Enabling E2EE:
Account Level:
Navigate to Account Management > Account Settings
Click Zoom Phone tab
Under General, toggle End-to-End Encryption to enable
Click Enable to confirm
(Optional) Click lock icon to prevent users from disabling
Site Level (if using multiple sites):
Navigate to Phone System Management > Company Info
Click site name > Policy tab
Toggle End-to-End Encryption
Group Level:
Navigate to User Management > Groups
Click group name > Zoom Phone tab
Toggle End-to-End Encryption
Individual User:
Navigate to Phone System Management > Users & Rooms
Click user name > Policy tab
Toggle End-to-End Encryption
E2EE Limitations
When E2EE is enabled, these features are not available:
Call recording (automatic or ad-hoc)
Call flip between devices
Call monitoring (listen, whisper, barge)
In-call controls (merge, transfer)
DTMF codes
Hold music
Park/unpark
Shared line appearance
Switch to carrier
Elevating call to meeting
Use Case: Enable E2EE for executives, legal teams, or sensitive departments. Keep disabled for support teams needing call recording or monitoring.
Emergency Address Management
Setting Up Emergency Addresses
Emergency addresses are provided to first responders when users dial emergency numbers (911, 999, etc.).
Account/Site Level:
Navigate to Phone System Management > Company Info
Click Account Settings or site name
Click Settings tab
Under Emergency Address, click Edit
Enter complete street address
Verify address is validated by system
Click Save
Individual User:
Navigate to Phone System Management > Users & Rooms
Click user name > Profile tab
Under Emergency Address, click Edit
Enter or update address
Click Save
Emergency Address Best Practices
Remote Workers:
Set emergency address to their home office location
Update when they relocate
Train users on how to update their own address
Multi-Floor Buildings:
Include floor/suite number in address
Consider separate sites for each floor for accurate routing
Mobile Users:
Set default emergency address
Educate users that address doesn't update based on location
Encourage users to use their mobile carrier for 911 when traveling
Desk Phones:
Assign emergency address based on physical phone location
Update if phones are moved between offices
Critical: Emergency address accuracy can save lives. Audit addresses quarterly and after office moves.
Call Blocking & Spam Protection
Managing Blocked Numbers
Block unwanted callers at the account, site, group, or user level.
Account-Level Blocking:
Navigate to Phone System Management > Settings
Under Security, locate Block List
Click Manage Block List
Click Add to create blocking rule
Blocking Options:
Prefix Match: Block all numbers with specific country code and area code
Example: Enter
1905to block all calls from +1 (905) area codeUseful for blocking entire regions or known spam sources
Phone Number Match: Block specific phone number
Example: Enter
19051231234to block +1 (905) 123-1234Include country code before the number
Type Selection:
Inbound: Prevent blocked number from calling/texting your users
Outbound: Prevent your users from calling blocked number
User-Level Blocking:
Navigate to user's settings
Under Others, locate Block List
Click Manage Block List
Add blocked prefixes, numbers, or SMS short codes
Users can also manage their own block list from Zoom app
Spam Call Protection
Enable Spam Detection:
Zoom automatically identifies potential spam calls
Users see spam warning before answering
Caller checkmark icon identifies verified calls
Block Calls Without Caller ID:
Navigate to user settings
Toggle Block Calls without Caller ID to enable
Blocks all anonymous/hidden caller ID calls
Handling Spam Tagged Calls:
Educate users to report spam calls
Monitor call logs for spam patterns
Add repeat spam numbers to block list
Access Control & Authentication
Managing User Permissions
Policy Settings:
Navigate to Account Management > Account Settings > Zoom Phone tab
Configure which features users can access
Lock settings to prevent users from changing them
Key Security Policies:
Prevent External Calls:
Block all inbound external calls for sensitive users
Limit to internal-only communication
Useful for reception, internal support lines
Restrict International Calling:
Navigate to Phone System Management > Settings
Under Calling, configure international calling restrictions
Prevent fraud and control costs
Require Feature Access Codes:
Force users to enter PIN for certain features
Adds authentication layer for sensitive operations
Role-Based Access Control
Admin Roles:
Assign minimum necessary privileges
Use role management for delegation
Create queue admins for call queue management only
Limit full admin access to IT leadership
User Groups:
Create groups by department or security level
Apply different security policies per group
Simplify policy management at scale
Recording & Data Retention
Call Recording Compliance
Recording Consent:
Enable recording prompts for legal compliance
Configure consent options (one-party vs. two-party)
See Call Recording Setup article for details
Data Retention:
Set retention policies for recordings
Configure automatic deletion after X days
Balance compliance requirements with storage costs
PII Redaction:
Enable automatic redaction of sensitive data
Protects credit cards, SSNs, etc. in transcripts
Configure PII groups for your industry
Recording Access:
Limit who can access recordings
Use role-based permissions
Audit recording access regularly
Voicemail Security
Voicemail PIN Codes:
Require PINs for voicemail access via phone
Set complexity requirements
Force periodic PIN changes
Voicemail Transcription:
Enable for searchability
Apply PII redaction to transcripts
Consider disabling for highly sensitive environments
Compliance Frameworks
HIPAA Compliance
For healthcare organizations handling protected health information (PHI):
Requirements:
Sign Business Associate Agreement (BAA) with Zoom
Enable E2EE for calls discussing PHI
Enable automatic call recording with consent prompts
Configure PII redaction for transcripts
Implement access controls and audit logs
Train staff on HIPAA-compliant usage
Zoom Trust Center:
Access compliance documentation at zoom.us/trust
Download SOC 2, HIPAA, ISO certifications
Review security whitepapers
GDPR Compliance
For organizations handling EU citizen data:
Data Subject Rights:
Ability to export user call logs
Process for data deletion requests
Document data processing activities
Data Residency:
Configure data storage location if required
Review Zoom's data center locations
Understand where call data is processed
Industry-Specific Compliance
Financial Services:
Enable call recording for regulated activities
Implement retention policies per regulations
Configure trade surveillance if required
Legal:
Use E2EE for attorney-client privilege
Enable recording for evidence preservation
Implement secure voicemail access
Education:
FERPA compliance for student data
COPPA compliance for calls involving minors
Configure age-appropriate security policies
Security Monitoring & Auditing
Call Logs for Security
Monitor for Anomalies:
Unusual call volumes
Calls to blocked countries
Repeated failed authentication attempts
Spam call patterns
Export Logs Regularly:
Monthly security audits
Compliance reporting
Incident investigation
Quality of Service Monitoring
Security Indicators:
Sudden quality drops may indicate network attacks
Monitor for unusual latency patterns
Track failed calls that could indicate system issues
User Activity Monitoring
Track Adoption:
Identify users not using Zoom Phone (security bypass risk)
Monitor for policy violations
Review recording access logs
💡 Security Best Practices
🚀 Quick Wins
⚠️ Common Security Issues
🎯 Security Checklist
✨ Essential security measures:
Immediate:
First Week:
First Month:
Ongoing:
Last updated
Was this helpful?
