Centralized asset tracking has transformed governance and now speeds incident response
What is our primary use case?
My main use case for Axonius is config management and asset inventory. I use Axonius to maintain the asset inventory up to date and also to identify the owners quickly; these are the primary requirements, and it will help us build governance across all the assets that we have provisioned in different AWS accounts and the on-premises environment.
Our team especially leverages Axonius for asset tracking and ownership. In terms of security incidents, it was really challenging for us to identify who created the asset, who the owner is, and how we can track what changes happened over the period; those are the big challenges in the past. Now with this solution in place, we can quickly track what the asset is, who is the owner, what changes have happened, and what caused a real incident or changes that really impacted the system, which can be easily tracked and identifiable, enabling us to reach out to the owner to fix things quickly.
What is most valuable?
The best features Axonius offers are inventory and tracking of the changes. The tracking of changes feature works for my team through recording all config changes as they happen over the period, showing who made the change and when, giving us visibility especially when someone made a change with associated reference information such as IT or Jira tickets, providing insights on the reasons behind the change.
The main appreciation I have with this tool is the governance, as we had a big gap for the NIST and other compliance programs where we didn't have a good asset inventory or maintain the config database. With this solution in place, we are now 100% compliant along with security functions or operations area management.
Axonius has positively impacted my organization, with one great improvement being the compliance program, which has centralized everything in one place. Additionally, with this solution in place, we can track quickly, helping us accelerate the incident response process.
The acceleration of our incident response is notable because in the past, identifying assets and their ownership was really difficult. Now with this solution, we could quickly log into the system, identify the asset, and see the owner, allowing us to reach out to the right people and identify the group the asset belongs to. Having tags assigned helps indicate the application or environment it is currently running on, enabling us to quickly revert changes or mitigate issues that arise due to recent changes, which significantly improves our incident response process, especially containment and remediation.
What needs improvement?
I would add that currently, the tool supports some integrations, but we would expect it to support broader integration with other security tools, observability, or any other cloud integrations.
One area Axonius can be improved is its integration process, as it is not straightforward; there is a lot involved in cloning the instance and other hard changes that I expect to be fully automated, suggesting an agentless method instead of utilizing agents, which feels somewhat legacy but could be improved.
The user interface needs improvement because it is a bit laggy sometimes, making it not straightforward when we want to identify things quickly, leading us to go in different directions which could be better tied together in one place.
For how long have I used the solution?
I have been using Axonius for the last couple of years.
What do I think about the stability of the solution?
Axonius is stable so far.
What do I think about the scalability of the solution?
The scalability of Axonius is good; sometimes we see some lag, but apart from that, it is performing okay. I feel we can improve a bit in that area, but overall we are doing okay.
How are customer service and support?
The customer support has been good.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
Previously, I was using a custom in-house solution that was not performing well, as well as an AWS solution that did not provide full insights and was more manual.
How was the initial setup?
I purchased Axonius through the AWS Marketplace.
What was our ROI?
I have seen a return on investment, with time saved being the measurable metric I would highlight.
What's my experience with pricing, setup cost, and licensing?
I think I am good so far with the pricing, setup cost, and licensing; I do not see any disturbances there, but it is working well.
Which other solutions did I evaluate?
Before choosing Axonius, I did not evaluate too many options, but I looked at Precise as one of them.
What other advice do I have?
My advice to others looking into using Axonius is to focus on centralized asset inventory, governance, and ownership. I do not have any business relationship with this vendor other than being a customer. I think Axonius is doing well overall. I would rate this review an eight out of ten.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Integrates with ServiceNow and provides alerts for deviations
What is our primary use case?
The tool's main use case is connecting multiple IT systems using various adapters. It helps identify device registration, uptime, usage, and deviations from expected performance. When deviations are detected, you get alerts and can take necessary actions. A major use case is its integration with ServiceNow, which provides a landscape of your devices and allows you to see them and write policies accordingly.
What is most valuable?
The most valuable feature of Axonius is its ability to deduplicate records and identify which ones are old and stale versus those more relevant. For example, if you haven't logged in today but a system somewhere else mentions you have, Axonius can detect this through various logs like Active Directory, file logging, or Wi-Fi connections. Traditionally, someone would have to make numerous calls and spend a lot of time to find out if you are on-site or connected to a Wi-Fi network. The tool simplifies this process.
From my experience, onboarding and adding connectors was pretty easy, especially when integrating with the ServiceNow environment. It worked well for my use case, but the ease of use can depend on the customer's specific needs and what they are trying to achieve.
What needs improvement?
For Axonius, I would suggest supporting more ticketing platforms and enhancing API integration directly into the platform rather than just the connector. This would allow for better integration from different systems, possibly into workflows, which I think is currently lacking.
For how long have I used the solution?
I have been using the product for three months.
What do I think about the stability of the solution?
The tool is stable, and I haven't encountered any bugs.
What do I think about the scalability of the solution?
The solution is a scalable product. You can install and provision it on the largest available cloud instance. It scales based on demand and licensing and is monitored by the vendor's platform, so it definitely scales based on your use case.
How are customer service and support?
The tool's support is responsive.
What other advice do I have?
I use the tool's SaaS version. As an IT operations professional, you should know what you're doing before using this tool. It's not an end-user tool; it's meant for IT engineering, operations management, or developers. It depends on what you're trying to accomplish. So, I would advise understanding your goals clearly before integrating this tool into your operations.
Ensure you label and use tags appropriately. Tagging can get out of hand, so everyone must agree on the tagging system. This approach will help you scope your reports and policies effectively.
I rate the overall product an eight out of ten.
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)