What is our primary use case?
We use Ivanti Security Controls for mainly two purposes. One is for scanning vulnerability and the other one is for patch management. The process involves scanning all servers. Once they are scanned, we start deploying patches based on the vulnerability, as well as based on the missing patches. That is how Ivanti Security Controls works.
What is most valuable?
Ivanti Security Controls is an agentless tool which means we do not need to install any agent on the server or endpoint. Through agentless capabilities, it can install software, install patches, and control over the server, including asset management. It is a very good tool feature that we appreciate for organizing our patch management as well as asset management. These are the two main features we are using in Security Controls.
Ivanti Security Controls has mainly categorized into two different types when it comes to patching: agent and agentless. With agentless, we scan the server based on scan results to get output. Once we receive all results from the server, we immediately schedule a patch. We may have different environments that require DevOps, development, pre-production and production environment where we scan initially and start deploying patches. Once deployment is completed, we check stability. Based on the results, we proceed with production. We schedule it all together, and it has capability of running PowerShell scripts where special handling is required for servers. Based on requirements, we provide pre-required PowerShell scripts to run, such as stopping a service before rebooting.
The main capability of Ivanti Security Controls is being agentless, which is the key aspect everyone uses. The second part is its capability of running scripts in the back end. If something goes wrong in any machine and we need to stop or add any registry, it has capability of running scripts as well as scanning the complete machine. It provides output of all applications and OS security, giving a clear picture of all vulnerabilities.
What needs improvement?
This solution does not have capability of managing applications. It is only used for asset management and patch management.
Regarding analytics for Ivanti Security Controls, it does not have extensive capabilities. It is a basic tool from Ivanti for scanning and deploying. It does not have analytics features such as EDR or security tools available in the market. It only has capability to check missing patches, find them, and deploy them.
When it comes to reports, compliance reports or similar types of reports are not user-friendly. Expertise is required for handling these aspects.
The asset management in Ivanti Security Controls needs more visibility. Additionally, it can be improved to handle in-house applications, which currently cannot be installed. It can only handle existing applications, unlike Ivanti's Endpoint Manager. It should have additional features in this area that need improvement.
For how long have I used the solution?
I have been working with Ivanti Security Controls for the past six years. Before, the name was different, but the tool was the same.
What do I think about the stability of the solution?
It is highly stable, which I can guarantee. It uses its local SQL server and stores minimal database. When we have a proper structure with backups, it is much more stable compared to other tools.
What do I think about the scalability of the solution?
It is not highly scalable, but it works well for mid-sized companies with 1,000 to 2,000 nodes. It is not recommended for large scale deployments with 10,000 to 20,000 nodes.
How are customer service and support?
We encounter issues while upgrading or sometimes face different errors which can be difficult to identify and resolve. Their technical team is very responsive and supportive. Their support is top-notch.
How would you rate customer service and support?
How was the initial setup?
The main issue we faced initially with Ivanti Security Controls relates to its vast features. During initial installation, networking team and multiple other teams must be involved. This is one drawback because with agentless deployment, certain ports must be enabled by the networking team to analyze and complete tasks. The agent version is not as capable, so we planned using agentless. Multiple teams have to be involved in initial installation. Once everything is familiar, it becomes the best tool for patch management.
What other advice do I have?
For mid and large enterprises, the pricing of Ivanti Security Controls is reasonable compared to other patching tools. However, for small enterprises, it will be very expensive.
Based on requirements and costing, people decide on Ivanti Security Controls. If companies want vast features, they will choose a different tool. However, if they want only patch management, they will choose Ivanti Security Controls based on pricing and user-friendly aspects. While it requires expertise, this tool can achieve much more compared to other products.
In AWS and Azure or any applications where servers are present, minimum testing typically uses two core and 4 GB of RAM for basics. If any agent is installed, not only for Ivanti but for any patching tool, it will consume CPU. Therefore, people plan using agentless to avoid agent installation and consumption. It is suitable for small organizations or light servers with 1,000, 2,000, or 3,000 servers who do not want to invest heavily in hardware.
My rating for Ivanti Security Controls is 9 out of 10.
Which deployment model are you using for this solution?
On-premises
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other