By Mike Runda, Senior Vice President and President, Avaya Client Services
Recently, an Avaya customer—a major global financial institution—encountered a pretty disruptive network issue. Avaya support technicians encountered roadblocks in resolving the issue, and the customer's IT personnel were unhappy. As the issue escalated through Avaya support channels, it quickly became apparent that the customer's internal security policies were thwarting Avaya efforts to look into the customer's system to solve the problem.
You see, their IT personnel were not allowed to give Avaya technicians network access to capture the information necessary to properly diagnose and repair the issue. Cybersecurity was the concern. Avaya and the customer struggled for nearly a week without resolution.
To break the stalemate, a senior Avaya executive called their CIO and explained that without proper access, Avaya couldn't resolve the issue. Once we explained how we secure the connection, the CIO gave permission, our remote access solution was brought online, the issue was diagnosed within 30 minutes, and then it was immediately resolved.
Similar scenarios can be avoided if customer decision makers ask important questions upfront, before they buy technology solutions, about the measures their vendors take to provide both high-quality support services and security. Typically that will involve some sort of solution that provides remote network access. At Avaya, we call it Secure Access Link (SAL). Our SAL Gateway is the remote connectivity method that enables us to deliver rapid problem resolution, problem prevention and solution optimization.
But not all solutions are equal. As you consider your next technology solution, consider the three key attributes of secure remote access:
First, it should be smart. There should be flexible deployment options with minimal hardware and software requirements. It should enable efficient and timely delivery of service packs for software updates and easily integrate with automated and advanced diagnostics solutions. And when support is required, it should allow your personnel to connect with the vendor's experts with a single click.
You should have complete control. The solution should give you total approval/denial control over who accesses your network. If you do grant access, the solution should track and provide a detailed log of support activity so you see which vendor personnel did what and when while logged onto your network.
It should provide high-level security. The solution should have no inbound connections into your enterprise—all connections should be strictly outbound from your datacenter so you have the ultimate control. The solution should feature "host containment," to automatically prevent support personnel from "host-hopping" from server to server. Each support session should be encrypted and then quickly be torn down when concluded. And, finally, the solution should require two-factor or multi-factor authorization by any vendor support personnel who request a support session.
In today's cyber threat environment, CIOs can't take chances with the security of their networks, yet they still need rapid and responsive technical support. By asking important questions upfront, you can be assured that your communications solutions are smart, give you control, and provide the level of security you need. So when an issue arises, you can get the support you need, without unnecessary delays.
Is your company making full use of the Avaya SAL Gateway to optimize and protect your Avaya solutions? I encourage you to attend Session #505 - Deep Dive into Avaya Diagnostic Server 3.0: SAL and SLA Mon to find out about the upcoming enhancements of Avaya SAL Gateway.
Released: February 13, 2017, 2:42 pm
| Updated: February 13, 2017, 2:43 pm