Avaya Secure Access Link 3.0 Meets Customers’ Security Needs
This past May I took on a new role here at Avaya, leading our team that engages with our amazing partner community. We’re working to improve the experiences customers receive from Avaya and Partner Services, and finding new ways for Avaya to partner to bring more value to the market. At the PCC EMEA event this week, I’m showcasing our partner programs and talking about how partners can help our mutual customers maximize the value of their support experiences—including through remote access solutions like Avaya’s Secure Access Link
I’ve blogged about the value of Remote Connectivity before, saying that the number one way to get more value out of an Avaya support agreement is to get all your Avaya assets connected. The Europeans I’ve been meeting with here at PCC EMEA understand this, but they are also cautious as they know customer IT organizations have concerns about the security of remote solutions like Secure Access Link. With each publicized security breach, there is heightened emphasis on security and vendor management. Here are common concerns raised by our customers:
- We want to control vendor access, to know why they are connecting into our environment, and to approve each connection. Avaya has answered this demand with Secure Access Link Gateway 3.0 and Policy Manager 3.0, which allows you to see the reason for human access into your environment and to approve or deny each access. Customers are reassured to know that every time a support engineer from Avaya or an Authorized Business Partner attempts to access a customer system, they will be notified with the reason for the access request and then can choose whether to allow the access or not.
- We don’t want the vendor hopping around from server to server within our environment. Avaya has answered this demand with Secure Access Link Gateway 3.0 and Policy Manager 3.0. The new Host Containment feature prevents SSH host-hopping from server to server. Furthermore, the customer can use these tools to prevent any number of commands from being executed by the remote engineer.
- We want an audit trail of who accessed our systems and what they did. Avaya has answered this demand with Secure Access Link Gateway 3.0 and Policy Manager 3.0. You will have log entries of who accessed which system on what day and time, and who within the enterprise permitted the access. Additionally, the new SSH Session Logging feature logs the whole SSH session—what was typed by the remote support engineer and what the product returned in response.
Plus, the Secure Access Link Gateway 3.0 and Policy Manager 3.0 servers (deployed on customer premises) use the latest technologies and security/encryption standards. Avaya has also updated the Secure Access Link 3.0 infrastructure in our data centers to provide those same updated security standards. As security requirements and regulatory mandates become more stringent, Avaya will continue to meet that demand with the latest technology and protocols in Secure Access Link 3.0.
I am honored to be attending the PCC EMEA event this week. This year we are expecting 200 people from 31 countries, representing 69 business partners. With all the positive energy coming from the changes at Avaya and all our partners, I feel we’re doing justice to the 50th PCC EMEA conference. Even if you’re not joining us in Nice this week, you can learn more about Avaya’s remote access technology and how to upgrade or migrate your Secure Access Link Gateway from 2.5 to 3.0. Just watch our Secure Access Link video, and read an Upgrade Notice.
Follow me on Twitter @CarlKnerr