We're sharing our Best Practices, starting with one of the most important topics, security.

When you onboard devices into Phonism, provisioning and management just work. Our infrastructure is set up in AWS with firewalls, bot-detection, and more. Phonism has features that help you protect and lockdown your environment even more, some of which you may already be using! Here are steps you should apply to secure and lock down your devices, tenant locations, and configurations:

• Enable mTLS for Supported Devices
  For Yealink, Poly, and Cisco (MPP) devices, enable mutual TLS (mTLS) to ensure both devices and Phonism servers validate each other before exchanging data.
  Note: If you don’t see Brand Security Settings in your Tenant view, contact us to enable it.
  See brand-specific security settings ›

• Whitelist IP Addressing
  Restrict tenant access to approved IP addresses, you can even use dynamic DNS hostnames. This is especially useful for legacy devices that may not be using or support TLS/mTLS.
  Set up Whitelist IPs ›

• Enable Tenant Provisioning Credentials
  Once your tenant is onboarded, enable tenant provisioning credentials to add another protective layer around provisioning.
  Manage tenant security settings ›

• Lock Down Configurations with Templates
  Use the Enforce option in Templates to lock critical values so lower-level users cannot override them.
  Read more about Templates ›

• Control Firmware with Software Rules
  Apply Software Rules to automatically upgrade or downgrade devices to the approved firmware version.
  Explore Software Rules ›

Wrapping Up 

Best practices for VoIP device security are an ongoing journey. Phonism helps you reduce risk, lock down your tenants, and keep devices compliant and protected.

This is just the beginning of our Best Practices series. Next up, we’ll explore more best practice strategies for managing devices with Phonism.

‍

Need help applying these best practices? Open a ticket and we’ll walk you through it.

‍