TrustRadius: an HG Insights company

Ivanti Security Controls Reviews & Insights

Score7.3 out of 10

9 Reviews and Ratings

Ivanti Security Controls Reviews

3 Reviews

Server Patching made easy

Rating: 7 out of 10
Incentivized

Use Cases and Deployment Scope

We use Isec (Ivanti Security Controls) for our monthly security patching of all servers in the environment (on-prem). This allows us to keep our servers up to date with the monthly release cycles from Microsoft and other vendors. It's also used for ad-hoc patching as needed for zero-day threats as well as keeping our template builds up to date.

Pros

  • Patching large numbers of servers.
  • Keeping audits of patching process.
  • Flexible configuration options with regards to selecting machine groups.

Cons

  • Performance of the console when using agentless machines.
  • The console layout is a bit cumbersome - would be better if all functions were accessible from one screen.
  • Common deployment examples to assist with deployment types.

Likelihood to Recommend

Great for deploying patches to large groups of machines.
Vetted Review
Ivanti Security Controls
2 years of experience

Ivanti Review

Rating: 8 out of 10
Incentivized

Use Cases and Deployment Scope

We went through an evaluation of patch management tools, and Ivanti was the tool we choose to go with. Ivanti offers a wide range of security tools that it has purchased over the years. Ivanti Security Controls is a great tool that offers both agent and agentless patching. We opted not to go for the whole security suite that they offer because we were only interested in the patch management tool. Our environment consists mainly of Windows and a few Linux servers. We also have a decent sized workstation pool that can all be patched and managed under a single patching software.

Pros

  • Live status update on patch deployments with an agent and also agentless deployments.
  • A large 3rd party patching inventory.
  • Easy to navigate and troubleshoot.

Cons

  • The email functions of reports could be better.
  • Combining the functions of the patching using agentless servers and workstations to allow for a seamless environment.
  • Lowers cost

Likelihood to Recommend

Agentless patching is the best of all the products I've used. The real-time updates that don't require re-scanning after each step is great.

Ivanti Security Control: Make your Environment more Secure

Rating: 10 out of 10

Use Cases and Deployment Scope

We implement Security Controls for companies looking for a patch/security solution. We also implement Security Controls for companies that have used Application Control as a standalone solution (we have many years of experience in this area) and are looking for a patch solution. With our customers, Security Controls is mainly used because of the increased security through Application Control. The implementation is very simple and the Config can be set up quickly to implement Trusted Ownership checking. Customers usually first use the product in a VDI / terminal server environment and then extend it to mobile clients and fat clients. The greatest benefit is the efficient security against unknown malicious code and the low maintenance effort during operation.

Pros

  • Trusted ownership checking is a good way to implement effective basic protection.
  • Patching is important today to react quickly to security problems. With Security Controls, it's easier than ever before.
  • One console for whole security.

Cons

  • Better search in the application control configuration
  • User rights management for modern user interface settings dialog.
  • For patching, a more intuitive console. Some features are hidden or not easy to find for users who are accessing the console for the first time.

Likelihood to Recommend

Security Controls is particularly suitable for customers who are looking for a patch solution and need security to protect themselves from unknown malicious code. For customers who are already using the Workspace Manager Suite, we don't think the solution is that suitable. A patch for Windows would be sufficient.