Appgate SDP vs. Cisco Meraki vMX vs. remote.it

I would recommend AppGate SDP to anyone that has fairly clear cut use cases for systems with user access with less than 5K resources per user. We found it works well in those cases and fully as advertised. The application can easily hide applications and resources from unauthorized access and is a reliable tool in your ZeroTrust arsenal.

Incentivized

We are a heavily invested Meraki environment, from our corporate locations to APs. Using a vMX as apposed another solution is a no brainer. It integrates well, has the same benefits as the rest of the Meraki stack, and you can leverage your favorite cloud platform

Incentivized

• Software-Defined perimeter
• Hide resources to non-authorized/authenticated users.

Incentivized

• It handles load really well.
• It brings simplification to the whole piece of networking network, so it makes it simple for us to diagnose and troubleshoot issues put in place as changes.
• It has pretty good site to site firewall control.
• It works well in Azure, so it ticks all our boxes.

Incentivized

• Live logging in the client. Currently you have to "download" the logs into a zip file and then open that zipfile to look at the logs. There's no logfile to tail or watch.
• Load balancing between controllers could be better. Currently relies on round robin DNS and sometimes a browser will pick a different IP than previous and you'll get a big "LOST CONNECTION TO CONTROLLER" message.

Incentivized

• Client VPN: Cisco Meraki vMX in general needs to implement multiple VPN profiles/ group policies for client VPN
• Alerts: Cisco Meraki vMX in general should be more consistent in sending alerts. We should receive alarms instantly.
• Event logs: More in-depth event logs for all Meraki products, such as system crashes, etc.

Incentivized

The company has been supportive overall of our needs and desired features. I have not personally called the support services, but I've heard no direct complaints either.

Incentivized

The existing system was FortiGate. The management of the system was a hassle. Because IT personnel had to manually create VPN accounts, user passwords were known to who created them and the end user did not have a way to change them. This created a security issue in the event an IT engineer left the company.

Incentivized

In terms of the Cisco suite, we also have Cisco Webex Calling IP deck solution right out across our centers. That has proven to be phenomenal in terms of performance and stability. With that alone, we've cut back our incident rate of telephony related issues by half essentially, which used to be our top rated issue previously. So the WebEx IP deck solution would be another product I would recommend.

Incentivized

This question is hard. A chain of retail or gas stations hypothetically that have simple networks in nature would flourish and scale quite well with Meraki. A chain of banks or something more complex that has more complex requirements doesn't scale very well or at least presents many caveats. Routing has always been a big setup with Meraki but I've always managed to 'get by'.

Incentivized

• It freed up IT personnel time. No longer did they have to manually create the account on the VPN endpoint and manually install the client or create VPN profiles on the employees computer.

Incentivized

• Standardizing: We can use the same "template" setup for multiple customers
• Management: Easy to manage along with the rest of the Meraki products
• Stability: Using Cisco Meraki vMX instead of VNGs in Azure provides better stability with auto-VPN between the Cisco Meraki vMX and other networks

Incentivized