Push Security

We ran into a problem during deployment that was caused by a bug. The bug prevented us from being able to onboard additional users. Our support team moved immediately to provide a sufficient workaround with true longevity until properly corrected. Again, anyone that's ever had to deal with most saas vendors & providers knows that's usually when to expect a stall. We barely had a misstep. Anyone can be great when its working; how you respond when it's gone awry is what counts. Push proved themselves on this point. Also, their built-in integrations work with little fuss and their APIs are fantastic! From inception to integration was very simple for us.

Push has helped protect our company multiple times by being the first service to alert us to detections and bring it to our attention in a format that we can easily action. The service has also grown considerably in its offerings since we started using it and our feedback has helped shape what it is today. The roadmaps they provide have been followed and any issues we've had have been resolved exceptionally fast. It's honestly surprising how often we'll get notified of something new being released and it makes complete sense as to why it was added to their platform.

1. It's very simple to install on a browser, set up an account and doesn't require much configuration or monitoring. 2. Phishing detection and blocking is the main value, but it has also helped us discover a ton of shadow IT, weak/re-used passswords, shared accounts and otherwise difficult to detect problems.

From a product performance pov: It's really just the finer details in regard to how identities are correlated and unified. Which they're paying a lot of attention to and have been improving. So the accuracy of identities-to-humans and vice versa has only improved. This, coupled with better SAML support will definitely improve the product's effectiveness and ultimately their platform capabilities. From an observability pov: There's currently no built-in extension/agent health feature to determine the state of your deployment.

This is a hard one to figure out. Push is limited based on what they have access to. Push is limited to the browsers it's installed on, so if your deployment of the extension isn't successful, you're not going to get the insights the platform can offer. While the Events page provides exceptional information, you're going to need a SIEM to investigate information about a specific employee over a timeline. There is a lack of branding available to show that alerts are being authorized by the company and not some third party.

Deployment is a bit more difficult in scenarios where employees can pick their own browsers and where you might see personal account logins. Sometimes I notice the browsers are not fully integrated or have gone outdated. With the API I managed to set up automation to detect that though.