ORDR AI Protect platform

The product gives us a great visibility on our connected devices with pre-designed dashboards and a wide range of reports. In addition, Ordr system provides the flexibility to integrate with external systems which we already have in our network. We're well satisfied with Ordr customer support service as their support engineers are knowledgeable and responsive to our request.

It's extremely powerful. It does two things extremely well. 1. Profiling endpoints. This product is years ahead of any other profiling service I've used. It uses deep packet inspection in addition to traditional fingerprinting techniques to create a very accurate profile for each endpoint. In some cases it can even find the serial number for an endpoint. 2. Traffic flow analytics. It shows source/destination flows between different endpoints using the device sensors and netflow data in a single GUI interface. This gives great insights for creating network segmentation policies.

Easiest way to gain visibility and asset inventory along with ensuring you stay compliant.

I'd like to have a way to customize the visual dashboards and share custom search with team or individuals who are responsible for the certain type of devices.

1. Detail in the GUI can be lacking. For example, if Ordr classifies a device as an iPhone, I want to know all the attributes Ordr used to determine this, and what method (deep packet inspection, MAC OUI, http user agents etc...) it used to gathered this data. Knowing this information is important for troubleshooting and determining why an endpoint was classified incorrectly, and finding the root cause to fix it. Cisco ISE has offered this for years and it's a bummer not having more detail. 2. Documentation. The documentation that Ordr has is well designed and easy to read, but there have been a number of times where I've wondered how a particular function in Ordr operates, only to find no official documentation on the subject. For example, Cisco NetFlow is supported by ordr, but Ordr doesn't specify which netflow records it can actually digest and make viewable in the GUI. 3. Lack of self-service support. A number of administrative tasks that I would usually expect to be able to complete myself require Ordr support. For example: Provisioning a traditional Device Sensor required Ordr support for the default username/password. This just changed, but for months they wouldn't share the default credentials, which adds time and complexity when you want to provision a new sensor, something that could easily be done by our in house staff. There are also a number of bugs/quirks that we run into that rely heavily on Ordr support to correct them in the system back-end.

A lot of data to take in This tool, like any software tool, needs to be tuned to your environment with good effor- but the feedback you get once its setup is amazing.