I use the system to collect background data, identify cybersecurity issues, and catch exceptions in systems like NetSuite.

I like that the tool has a user-friendly interface. It helps organizations and big companies improve business requirements and control processes.

Adding more detailed descriptions or YouTube videos about specific features would help improve the application.

I have been using the product for two years.

I don't recall any exceptional stability issues, but I assume they've improved with new versions.

I rate the product an eight out of ten.

We use it for reporting, noncompliance reporting, and identifying gaps. We use it for API monitoring within our company.

And we also use it as a CMDB. Our security team, people within the SOC team, and people within other IT departments use it as a CMDB. We have integrated Axonius with a few of our solutions, so it has good inventory mapping. It provides information like installed software, running services, file shares, patches, and more. We have integrated it with many different solutions that we use internally.

We refer to Axonius as a CMDB, but the tool was actually onboarded for KPI monitoring and to alert against noncompliances. For example, if a device is running with an out-of-date agent or if a device is missing an agent it is supposed to have, Axonius helps us find unauthorized software installations within corporate devices. We use it for various KPI metrics and send out automated alerts to the relevant IT personnel to address and fix those noncompliances.

Right now, we use it mainly as a CMDB, but the tool was onboarded for KPI monitoring and metrics.

It's the agentless solution. It doesn't rely on specific agents. We integrate Axonius with APIs, which are called adapters or connectors. Essentially, it's API connectivity between different platforms. Getting Axonius up and running only takes a few days. If you have a server or solution, you create firewall rules to integrate with other platforms. This way, Axonius can communicate and collect data from them without needing much infrastructure. It sits on a device and collects data from multiple environments and sources, aggregating everything into a single console.

It also creates multiple dashboards. Axonius provides preconfigured dashboards that can be customized to your needs. What I like is that everything is in one solution, and you don't need agents running on every process to collect information. Other platforms like ServiceNow rely on agents installed on assets, but Axonius doesn’t.

Axonius is agentless and can easily integrate with other platforms. It uses API access accounts with other security solutions. They support a lot of different solutions. When we first started using Axonius, they supported around 400 IT solutions. Now, I think they support more than 600 or 700. I've lost count.

When we started working with them, Axonius was a small company with just a few engineers, but now they’ve grown into a large enterprise. They’ve been great at fixing issues and customizing solutions for clients. They maintain all of that really well.

It is a good solution; it lets you customize the solution based on customer requirements. They can even create custom adapters. For example, if you have a legacy platform or a new solution that doesn’t have official support yet, Axonius can deliver quick fixes by developing custom adapters. I’ve worked with them when we needed to integrate a solution that wasn't in their supported integrations. They gathered the requirements, asked us what data we wanted to pull, and quickly delivered a custom adapter. They also added that adapter to their product timeline, ensuring it would become an official integration in future releases.

In that sense, Axonius has been fantastic at delivering these solutions. We’ve had no issues with them.

Axonius can improve on delivering compliance-related features, like PCI DSS, and different dashboards that work with various compliances. For example, if a company follows ISO, they can create a dashboard that shows the gaps within that compliance framework. They have started delivering some of these features, but the tool still needs to mature for companies that heavily rely on certain standards, like payment compliances or cloud security guidelines.

In those cases, the tool might need further development. However, I haven’t had specific issues because they are really good at fixing things. Whenever we report or escalate something, they are quick in providing solutions.

I think they are very flexible in terms of working with them. But at the same time, they are customizing the solution too much based on client requirements. This might cause issues in the future because if they keep customizing the solution for every single client’s requirement, they might face difficulties in future releases. Integrating every customer’s options within the platform might be challenging to handle.

That might be a risk they are taking. But we have had good communication with them, and overall, it’s been positive.

I have been using it since 2021, so it has been three years. It’s been cruising through so far fine. We didn’t have any issues with the platform.

During that time, they didn’t have the SaaS options. Now they have started offering SaaS models. We used on-premise deployment, which is hosted within our company data center. But, it’s been going good.

I would rate the overall stability a ten out of ten. But Axonius has a few things they need to integrate. They need to move forward to get more mature in the current IT world. So I’d like to give it an eight out of ten. In terms of working with them and the company’s flexibility, I’ll give ten out of ten for getting things done, customizing solutions, or providing quick fixes for issues we face. For all of that, I’ll give ten out of ten.

All IT people who work on maintaining assets, ordering new assets, and compliance managers will be looking into it. IT directors and anyone who works with IT, but not the end users. End users don’t have access to the platform, but anyone who works in IT and manages the platforms and infrastructure, as well as compliance people who want to monitor KPI metrics and view reports, use it. So, there are 500 to 700 users within my organization.

They’re really great people to work with. Every customer has a dedicated technical account manager. We usually have weekly calls with them to check on everything. When we onboarded the platform, we had regular calls, and they were always available. That was a great experience working with them.

Since it’s an OVA package, it’s a virtualization package that you can just deploy on your VMware, ESXi, or whatever virtualization solution that your company internally uses. It’s just, like, import it, and then they’ll provide you with a license key. If you do a POC, they’ll provide you with a license key for a month so you can try it out and see how the product is going. Once you’re happy, they can provide you with a proper license for however many years you are going to sign the contract with them.

But, the initial setup is pretty straightforward. It’s not like you need to change a lot of things in your environment. It runs in a standalone installation. They also provide a cluster-based solution. If your IT presence is across the globe and you have huge latency that you want to reduce, you can have multiple instances in your different data centers and then aggregate that information in a centralized cluster and show it in a single dashboard. They started offering this around the same time we began working with them.

In terms of onboarding, it only takes a couple of days. It's mostly dependent on your organization's RFCs, change requests, and approval processes. There aren't a lot of configurations needed. You just need to open a few firewall ports for product updates.

The product runs on a Debian-based operating system, and you can scale it based on your requirements. If you're trying to pull 50,000 assets, the requirements will be a bit different. You'll need something like 8 cores, 16 or 32 gigs of RAM, and probably 5 terabytes of storage to store the data.

One of the good features of the product is snapshots. You can go back to specific dates and check the inventory status at that time. Axonius has an option to take daily snapshots within the product.

Axonius collects data from other platforms, and you can configure it to take snapshots at specific times. It keeps the snapshots for as long as you want, impacting your storage. You can keep the snapshots for ten years and still go back to a specific date to check how many assets you had, how many were identified for a specific noncompliance, and when it was fixed. You can check all of those details going back to a specific point in time and still get that information.

Lots of other products, like CMDB products or cyber asset management products, don’t have that functionality. Other platforms give you live data but don’t provide an option to go back and check how it was ten months or a year ago. Axonius gives you historical information and keeps it as long as you want. You can configure it to store the data for one year or ten years based on your storage capacity.

That’s one of the good features we heavily rely on internally.

Axonius is quite a bit cheaper compared to other solutions. And the amount of value they provide is really huge compared to other vendors. So, it’s based on the actual requirement and how you want to use the product within your IT department.

You can get insights within the platform and see how you can integrate Axonius with your current setup. You can make a decision to go with the POC or something like testing. But I don’t think they provide a free download option. You need to request access to a test engine and then get the software.

Probably, if you have other solutions like ServiceNow, because a lot of companies already have ServiceNow, you might not find much value in moving to Axonius. Whatever Axonius provides, ServiceNow also provides it. So, you need to assess what you’re planning to use it for and check the features that Axonius provides.

See whether you want to move platforms. They have a few unique features within the platform. But if a company already has a proper CMDB or an asset management solution, you should review your current internal solutions and see the benefit of moving toward Axonius. It might be a financial decision or just a couple of features that Axonius provides additionally on top of the CMDB.

At this stage, I would rate it an eight out of ten. The product needs to mature a little bit more in terms of following up on compliances.

Axonius is a US-based company. We had a few difficulties in getting the legal documents signed when we started working with them. If they had an EU presence, our legal department might have directly worked with them, and it would have been much easier. But since they are completely US-based, we had to sign a lot of data processing agreements and deal with transferring data between the EU and US. The legal department had a few hiccups, and it took some time to go through all those processes.

In the future, if they have a regional headquarters in the EU or where there is no data transfer from the EU region to other regions, it would be much easier for companies to start working with them quickly. In the initial days, we had to sign a lot of contracts because when we started working with them, we had to provide some sample data, and they had to sign a lot of DPA (Data Processing Agreements) between both companies and the legal team. It was a back-and-forth conversation, editing that legal agreement, and putting it in place between both companies.

We had a few issues in getting the single agreement signed in the initial days. But apart from that, no issues.

It’s pretty much company-focused decision to choose a solution. If you don’t have any solution for CMDB, I think it’s good to go with Axonius because they have good integration. They support a lot of different tools. Within their platform, you have a separate section per adapter where they’ve mentioned probably 600 to 700 IT solutions that they can integrate and work with. You can also check within the description what kind of use cases you can get from that integration. For example, if you have some kind of vulnerability management solution or MECM or a BitLocker administration tool, Axonius will give you information on what kind of data it will pull from the individual sources. You can create reports, check BitLocker statuses, and see what kind of encryption has been applied and how it is maintained.

It will give you those use cases as well, showing what you can get out of that particular integration between Axonius and whatever solution you are looking for. You can list down all the solutions you use internally within your company and then check the Axonius portal or website to see what use cases you can integrate with the platform. You can at least get an idea before you even try to speak with the Axonius team and start working with them yourself to see the benefits of utilizing the platform.

We don't use it to the fullest. We just use it for a few pieces because we have other solutions for that. But they have a lot of different features within the platform. We are not actually replacing everything. We just use a few bits and pieces, like enforcement center actions, CMDB, and a few other features within the platform.

In my company, we did a production pilot in my environment where I work to evaluate the tool's capabilities, and our use case was looking for unmanaged endpoints, like workstations that may have fallen out of management by their management server, like McAfee, Tanium, SCCM, or similar things.

The tool's query wizard isn't bad. Suppose you have ever used or even talked to anybody about other products that use vendor-specific queries, like Splunk, which is supposed to be one of the harder ones to use and master. Compared to Splunk, Axonius has made the tool a little more user-friendly where it is a little easier to use, and that is really the bread and butter of the product because that is where you get all your reporting from on your assets to make determinations on what you are looking for, like security or and if you wanted to use it for asset management, you could. As it pulls so much data, there are other options in the query that you could choose from depending on what information you were trying to obtain about your environment.

There was an issue with the tool, and sometimes, the biggest problem was that there was a need to determine if one machine was the same machine. Sometimes, you would have to go into the interface, and Axonius realized that after which it offered tools that you can run, erase, or remove certain assets that didn't duplicate to have them rediscovered again or to see if that may help or aid. Sometimes, when you redeploy servers or make changes to servers, Axonius may pick that up as another entity when it's really not, and then you could have multiple records for the same server, in which case that can be confusing when you are trying to run reports and queries to get information. Axonius hasn't really been around that long. I think it's only about five years old. It was originally an Israeli company. I believe the tool was developed in Israel. I work as a government contractor. We use it in the government, and the tool had to actually stand up as a federal government agency relationship management here in the United States to be able to even use it to meet the requirements of the government because it is a foreign company. In the beginning, it was a little slow going because the tool was still getting established to be able to have the government as a customer of the US government. Axonius has continually improved that product throughout the process. When my company started to use the tool, it was in its infancy, and it was a virtual appliance. Axonius evidently had two different appliances at a time. I don't know if it has them today because it has been a little while now. Axonius had one tool for the private sector and then one for the government with more hardened security features that met certain what they call STIGs or security baselines that the government operates under. Axonius would try to give you a hardened or pre-hardened appliance, which was good. In such a case, they know as well if you want to apply certain security parameters to their servers to meet requirements. The tool is usually aware of what will cause an issue, and the product works with you pretty well.

I have been using Axonius for two years.

Basically, what the tool does is that the more endpoints you have to manage, the more you scale the platform up. For instance, the tool has benchmarks; if you go out to their website, it lists how many assets you are going to manage and what kind of server resources you would need to configure. For instance, if you are going to do all our stuff in VMware, you can go to the VMware shop. All these servers are basically virtual appliances, and if you are familiar with the ones that are pre-configured with the OS and the app, and if you import those into your VMware environment, then you can have the option to configure how many front-end CPUs you are going to use and how much memory you are going to allocate to the virtual machines. The core node itself usually gets the beefiest or the most resources because it hosts the database. It initiates a lot of all of the fetches or queries that you run against your database. You set all that up in advance based on the number of endpoints you think you are going to be managing. You can scale it up afterward, so if you end up having more environments that you wanna add to it that you didn't initially plan for, then you can go in and change the resources on the server, like add a few more CPUs or more memory. The tool has it all broken down on its website as far as the scale that you would need is based on the number of endpoints that you want to manage, and even the licensing is based on it. Everything is based on how many endpoints you want to manage.

My company probably had 60,000 endpoints and about 20,000 or 30,000 users as it integrated with Active Directory. You can get user information, too, even though it is really about assets and endpoints. The tool can gather so much other stuff because it's really pulling all kinds of data to correlate, and that is what it does. It correlates with data. We had multiple Active Directory domains, which had thousands of users, and you can connect it to each individual Active Directory domain so that it can reach into that domain and retrieve. All the read-only stuff, like I was saying before. If you do the read-only implementation, it is a lot safer because it is just read-only. You only need to grant the service account read-only access in a typically read-only role, which is offered by a lot of different solutions. Axonius has a typical read-only role that you can implement on the back-end server for the service account, so it can't go beyond read-only unless you will be taking actions, remediating, and doing automation. When things need to change, you need something greater than read-only for your service accounts to be able to take action.

The solution's technical support was good. The tool has a technical account manager and then an engineer. Both of them worked with you, and they were very responsive and quick to help us fix any issues that we had with the tool. At some point in time, I know that the product will mature. When you go to patch the product or upgrade the product, it was being developed when we were using it, so we weren't able to use it yet because it was still under development, and it was, like, a patching server, which is almost like what Microsoft WSUS server is, where you have a server in your environment that you can use potentially, or you could even go across the internet. There are machines that are more air-gapped where they can't talk to the internet directly. You could potentially have a server like in your DMZ, and it could talk to Axonius and pull down patches. Then, your servers inside could talk to that to automate patching, and Axonius was working on it. As it is going to be a year in December, I think the tool is probably up and running, and it might even be using it now. There were different kinds of initiatives that Axonius was working on at the time to improve the product, and now the tool is getting more cloud integration as well. The tool has its Azure and AWS offerings. If you know anything also about the architecture, the main server is called the core server, and it has a database known as MongoDB, which basically collects and stores all the data. We have the other server role. We used a couple of server roles, and one was the core server because you have to have that since it is where the GUI is hosted. When you connect to the GUI, you are actually connecting to the core node. It's presented from the core node, and then they have what they call collectors. You can take those collectors and place them throughout your environment, and what is nice about the collectors is that they only use a single TCP port. You could place the collector in an environment that may collect several different types of data from different assets. In such a case, if you didn't use the collector, you would have to have multiple firewall rules. If you are collecting data from Microsoft servers, like Active Directory and SCCM, DHCP, and certain Microsoft services or Linux services or other products as well, Axonius integrates with a ton of tools. The tool had around 700 adapters that it had developed, and some of them were better than others as far as their maturity and what they gathered because we would go into it, and we would connect one of these adapters thinking that we were going to get all the data. Axonius publishes what you can collect. It is good to go out and look at the adapter and what kind of data it can gather before you use it. It may not give you what you are looking for. We connected to probably ten or twelve different connections or adapters to different products in our environment. We had multiple collectors deployed, and it was nice because you just had to get one firewall rule implemented, as it would collect everything locally in that subnet where all those back-end servers lived. Then, all those ports and protocols were there because it was in a VLAN, and they were already opened anyway, so you didn't need any firewall rules there. The tool saves you time with firewall rules because where I work, firewall rules can be a headache because you have to go through change management and do all this stuff to get them implemented, and that can take time as it all gets scrutinized. It is nice to be able to just have one port open or one TCP port, really, for the collector node, which is the communication from the core node to the collector node to actually pump that data back from the collector to the core node to be put into the database. I rate the support a ten out of ten.

Gartner classifies Axonius as a CASM tool. I am not familiar with the tool's competitors. I don't know because that is kind of a newer thing and not brand new, but probably within the last two or three years. It is the first time I have heard of it. I know there are other tools that offer a similar capability. Axonius is an attack surface type tool, and what is cool is that when you have a known vulnerability, like, a day zero, and there's no real fix for it just yet or the vendors are working on it, and they may have to have some workarounds, you can run queries against your whole environment to find those assets that may be affected so that you know right away what your security posture would be in the event of a day zero for whatever asset we're talking about. In this case, then you would have a clear picture of the number of assets that I need to perform this workaround until the vendor can come up with a patch. In that instance, it kind of serves as an asset manager because you are looking at it for assets. The confusing thing to people about the product is that it grabs so much data about your environment that you can use it for a multitude of purposes, and asset management, which could definitely be one of them, but they don't market the product as an asset management tool. We used it as a CASM tool.

The product's initial setup phase is pretty straightforward. My company operates in a VMware environment, so we get the pre-configured VMware servers that are offered. We just import those into VMware, the servers, and basically figure them out for our environment with TCP/IP and DNS. NTP and all the normal stuff that you would do for servers to deploy are good for working with, but they don't give you full SSH access. The tool has a menu-driven tool that you can use too, and it has been maturing over time because when the product was first rolled out, and we started using it, we had a lot of interaction with their security and their engineers because they don't want you to go in and have full SSH access because you could cause issues as you won't know what you are doing. You could break their product, and so they limit your access on purpose so that you won't cause any issues. If you need anything that requires more access, then they give you access, after which you have to get with them. They are responsive and help you troubleshoot with Microsoft Teams so that they can see what we are doing. We can have sessions where we can share stuff, and they just tell us what to do. And they'll send us, you know, syntaxes that we need to input, you know, stuff like that. As we have gone along, the menu-driven tool they call the toolbox, or Axonius toolbox, is what you use for, like, day-to-day administration to do the basic back-end server stuff, and that toolbox is actually reachable through SSH access on the back-end servers on the CLI. You don't see that in the user interface where the regular users would be doing queries and using the product as a user. I am talking about administrative stuff here.

For us, the product's deployment phase was a little challenging because we had to deal with other departments and business units. We were dependent on the tool's team because they had the keys to their kingdom, so we had to work with them to get the product deployed and get it connected to their systems because they had to, in some cases, make a service account for us and configure it to be read-only, give us the password, and then we would input that on our side to be able to connect to their system their back end system. There was change management involved. There were server firewall rules. Typically, we did that collector, which was a server role, and we would implement a collector in the environment, and then we would just the collector in that environment would just fetch the data from those different servers with those pre-configured accounts. Sometimes, they could be domain accounts if whatever solution it was was domain joined. It was able to have a Windows service account if it wasn't a Windows system. Windows systems are pretty much domain-joined, and you could use an Active Directory service account on those systems that we could set up. Then, we would tell them what we made, and then they would add it on their side, and then it would work. There were some hiccups here and there, of course, getting that stuff straightened out. It probably took about six months for us to get everything working just because of the scale of our environment and all the different people that we had to work with. It really becomes a delay because they own those systems.

I never heard anybody bulk at it because we have other products, such as security products, as well. The product's price is more in line with or maybe a little lower in price than some of the other tools. It is kind of what I heard mentioned, but I don't know for sure because I didn't really deal in dollars and cents.

Axonius is used in our company's daily security operations to manage and secure assets, and it has its own query analyzer. You can run queries against the data that has been retrieved in the database to make assessments of your environment on a daily basis. The tool has what is known as adapters, and those adapters connect to systems within the environment to pull data into a central repository to basically crunch data and deduplicate it down to what is called a master endpoint record, which is a single entity that represents basically one machine across multiple management platforms as a client machine, and then you can do queries against it. The tool pulls in so much data that you could actually use it for other things. The first thing that comes out of anybody's mouth when they hear about the product is that it is an asset management tool, but our use case really wasn't associated with it, and we didn't get it for that. The tool is more secure than some other products. The tool is all about security. We have high-level security audits where someone will randomly come in and evaluate your environment by surprise, so you don't have time to prepare because they want to see what your operating stature is and if you have a normal operating stature. When someone comes in to evaluate our environment, and they look for machines that are not being managed by their servers, and they could actually present a vulnerability, then it can definitely hurt your security score in the end when they are coming in to evaluate your security posture.

The tool has automated capabilities that can remediate machines. It can. The tool definitely has automation capability, but we didn't use that. We were just basically using it to pull data from our management servers about the clients they manage to make determinations on our endpoints. You won't always know sometimes if your endpoint is functioning or not if you have so many of them. Basically, what it does is that it just connects you to all your management servers that manage those clients, and you can see graphically because, in the interface, it actually shows for the entity in question, like, say, it is just a workstation. It will show each management tool and the icon for that management tool, as well as the vendor's icon next to it, to show you that it is checked in with that server and that it's actually communicating with that server as a client machine to give you an idea if you have any endpoints that aren't being managed from any one of your management servers for your management tools.

When it comes to integrations, the tool uses service accounts to do it, and they have a notion of a read-only service account, which is what we use. Or you can have one that has more authority or rights where it can actually take action. We did a production pilot because we needed real data. Originally, we did a pilot in a lab environment, but those servers in our lab environment don't really have a lot of data that is meaningful to us. We did a production pilot, which was accepted because we used read-only accounts, and all they will do is just pull data, and all the system needs, the management servers need, or all the service account needs is a read-only role on the servers so that it can just read the data and pull that data. It was a safer bet for us because we were just doing the production pilot. We needed real data to evaluate the product and see if it would meet our needs. The accounts were actually just read-only, which was the safe way to go in a production environment. The only thing that you had to worry about was that Axonius advertises that certain systems can take a performance hit when they get when that job runs, and they call it a fetch, and it runs periodically, and you can control that. You are in complete control of what time it fetches. We did it off hours, and we actually worked with the different teams to schedule it because if they had any operations that they ran off hours, we didn't want to interfere with that. We worked within the individual teams that manage those servers, like SCCM's team, McAfee's team, and Tenable's team, to be able to make sure that we were optimizing our fetches around their schedule that was good for that platform.

The performance issues in the tool have been optimized to a level by Axonius, where the tool can tell by the stream of data what kind of performance they are getting across the wire, like the network. The tool knows the network bandwidth that is being used and things like that, and it will actually adjust that on its own. There are only really a couple of systems that advertise, and one of them was SCCM, which is now MECM. I believe that Microsoft has changed SCCM to MECM. I think it was Tenable because Tenable can have multiple repositories that you can configure for the product to use, and we can schedule those off hours. I just think that certain systems, depending on how much data they are going to fetch, can take a hit depending on how busy they are and stuff like that. In the end, we really didn't have any problems once we worked with the individual teams to polish and schedule the right fetch for the platform because they were SMEs who knew about the product. SMEs have worked with the tool, and we really didn't have any issues in the beginning because we worked with those individual teams where there was some coordination with the tool.

The tool does have AI initiatives, but we have not yet integrated the product with any AI features. We didn't get the funding to continue our pilot as well. In December, I think it will be a year since the product has been turned off. Users have liked the product, and it is possible that it may receive funding in the future, in which case it could be powered back on and then brought back to life because, basically, they are virtual machines in VMware on-premises. Axonius does have a SaaS offering that you can run on AWS and Azure. We had an on-premise solution, and we managed everything completely. For more infrastructure as a service, we have a little private cloud.

I would recommend the tool to others because it is kind of unique in what it does. I have never seen another tool do this before where it doesn't talk to any clients itself, so it is agentless. It pulls from your back-end servers and then correlates the data that it receives on those servers to create what I was saying before is what they call a master endpoint record, which represents a single entity across all those servers that may be like a workstation that is being managed that is definitely communicating and getting its updates to its management servers with all you know, and it could be because it is a client with multiple servers. I don't know any other tool that really does that in that fashion where there is no impact on the endpoint itself.

I have been out of the loop for a little while now, and I haven't been using the tool. There are probably all kinds of new capabilities in the tool that I am not even aware of because when we were on it, I was working on it day to day for, like, a couple of years. So we were pretty up to date on all the new features that were coming out, some of their roadmap items, and where they were going with their product. Now, I have kind of been out of the loop for a little bit. I guess what you would probably think about is whether or not you would use it on-premise or in the cloud environment, depending on what kind of assets you have. As I understand, I think now it can reach back from the cloud through a gateway of some kind that you may have in your environment so that it could potentially get your on-premise stuff and cloud stuff altogether to where you didn't have to have separate installations. The tool does have integrations where you can have multiple sites, and they roll up all their data to a server in the cloud. You could just report right from the cloud on all the assets that were on-premises across your enterprise. The tool has a lot of capability. The product that we had was actually used on Rocky Linux, which is a Red Hat tool. The tool would release patches periodically or a monthly patch that was a security patch that they would give you that you would install for security. The tool would also have updates or upgrades where you could roll out upgrades, which is something that we usually did during the evenings when we had a maintenance window so that the user base wouldn't be using it.

I am not really a security person. I am more of a virtualization engineer, so I work with VMware stuff and infrastructure and stuff like that. Our security people loved it because it did what the vendor said it would do, as they were able to find workstations and even other devices that weren't being managed. Not only that, it is good to find network devices that you may not be aware of that may be causing you a problem or could be security-related. One of the things with Axonius was that in some environments, it could find these little networks, like a Raspberry Pi or something like that, plugged into the network or something that shouldn't be plugged into the network. It would be able to find these devices where nothing else really could. The tool really kinda does work as they say, and it could help you with your security posture.

I rate the tool a ten out of ten.

We've got we've got a ton of use cases for the solution. However, a lot of companies will use it primarily on the IT asset management side, which it does a terrific job of. We do use it for specific use cases tied to that. That said, being in the security realm, we really use it as a cyber attack surface and security control gap tool.

For us, on the security side, we connect our EDR solution, like CrowdStrike and Carbon Black or any access control like Azure Active Directory and regular Active Directory, et cetera. It allows you to identify whether or not what you consider the asset source of truth in your environment is actually doing a good job or not. A CMDB, for example, a lot of folks want to rely on that as a source of truth for all assets.

However, when you connect these disparate sources to Axonius, you're able to see and identify the gaps that you might have in that inventory. If you've got a vulnerability scanner scanning an asset or EDR on a specific tool that you can see but don't see in your CMDB, you've identified a gap. You can use that for a number of cases. You can, for example, see stuff that's in your CMDB that you don't have malware coverage for. That's really where the power of Axonius comes in - to be able to identify those gaps. That's one major use case, and that's a really big one in our space.

For a security outfit, you are constantly trying to do a good job of ensuring you've got your organizational controls in place enterprise-wide. If you don't know what you're protecting, chances are you've got gaps in your protection. That visibility that we now get from Axonius gives us enormous peace of mind that if it's out there in our environment, we know we can see it in some way using this tool. From there, it's just a matter of what appetite we have to address your gaps. The knowledge they provide, from a security professional perspective, is invaluable.

Axonius has been the most effective in enhancing our security posture. When it comes to something like Axonius, the tool is only as effective as the source connections that you provide. Essentially, what Axonius does is it connects to a number of disparate sources in your environment, whether on-prem or SaaS applications, via API connections. Right now, Axonius has upwards of 900 or so of those out of the box. It comes down to what sources you want to connect to it to identify gaps in your ecosystem.

The automation capabilities in Axonius have streamlined our security operations. You're bringing all this data in, and Axonius does a great job of taking all this data, normalizing it, and correlating it together. It does all the deduplication and stuff for you. Then, you can build queries in the tool to see what you want to see.

For example, if I want to see everything that's not being scanned by a vulnerability scanner that's part of my Linux server population, I can do that. On top of that, Axonius has what's called an enforcement action feature. You can take action on the data you build in these queries. A good example of how to use this might be if you've got geolocation data coming in. You can build enforcement to say, "If I see someone logging in from anywhere outside of the continental US, I want CrowdStrike to go out there, and network isolate that machine, and cut it off from the network." You can orchestrate all of that from Axonius.

There are some machine-learning pieces at the back end of the tool. There is a feature that we're not currently using right now for query building. When you construct queries in Axonius, you don't need to learn any sort of query language or anything like that. It's got a logic builder that you can use. However, to make things even simpler, you can integrate it with OpenAI and ChatGPT, and you can use Axonius' company license for that, or you can use your own enterprise license. That allows you to really just text the questions, and it gives you it gives you the answers. It's as simple as it gets.

They move so fast that there's a new release almost every week. Probably the biggest benefit that I've seen in terms of support from Axonius is that they don't charge you to improve their application.

You can easily request new features. For example, if there's data that I'm not seeing or if I want a new feature in the tool, it really is just as simple as putting a request in and speaking to your technical account manager. Depending on the complexity, it can be in there in a matter of weeks.

It's hard to say what is lacking as it continues to grow and allow you to put in new requests. If you need something, they don't charge you for it, and they can make the change in a hurry. It's all a part of their support contract.

I've been using the solution for two years now.

We sometimes have issues with the UI. We can have fetch cycle issues. That's probably been our biggest headache with Axonius, and they've continued to work on it for us. There's a balance between how much computing power they give you for your instance versus all the sources that you're trying to connect to. If you're trying to fetch all of this data every single day, it requires a lot of juice to go out there and do it. Your instance can be slow sometimes if that drags into the next day.

The scalability potential is huge. It's virtually limitless. They are working to become a one-stop-shop type of application, which is almost unheard of these days.

We have a few hundred users on the product.

I have never dealt with a better technical support team ever.

The deployment was straightforward for us. There are a number of deployment methods. There's a strictly on-prem one. There's a hybrid deployment. We went with vendor-managed deployment. As far as deploying the instance, it took them a matter of minutes to turn it on.

In terms of deploying it with connecting sources to it, that's largely dependent upon your organization's speed. That said, they make the adapter connections really easy to connect. It's pretty simple.

If you have experience with APIs, the setup is pretty easy.

The pricing is a bit subjective. Compared to other major enterprise tools, what is on offer is very reasonable. It's cheaper than other IT asset management tools on the market, like ServiceNow.

I'm a customer.

I'd rate the solution eight out of ten. I'd recommend the solution to others.

People need to keep in mind that the data that Axonius provides is only as good as the data you give it. So, if you've got a messy environment, be prepared to come up with inventive ways to look at the right scope of resources or assets in the tool to facilitate cleaning up your environment. That can be challenging at the outset.

We use Axonius as an asset monitoring tool. Our adapters and assets are tagged into Axonics using an AD group. We have segregated into region-wise assets, and it's easy to look at the dashboard and see if an investment is down in a particular region.

Within the system life cycle, Axonius does its eCheck. The best feature I found in Axonius is that it shows us the duration of eCheck, and it shows us what device is down and in which part of the system life cycle or the checking part the system is down in. So, investigating makes it a lot easier because we can pinpoint the exact time and location of the asset. And then, when you customize your queries, you can also figure out the reasons. I'm not very familiar with the customization of queries, but I've seen seniors do it, and it's quite brilliant to find or have a tool like that.

Regarding the improvement of Axonius, it goes halfway for both the tool and the user. If we set it up quickly from our end, and if the AD groups and all other groups assigned to tag the assets have been tagged correctly, Axonius could not show an error. But we are still sorting out our segregation for assets as well. However, Axonius can't pull out the exact reports, but there is a way around this, where we can use the built-in queries. For example, we have CentOS systems, and within CentOS, we have tagged assets with vulnerabilities, but these assets do not appear in Axonius. As an alternative, what we do for this is write a query to find the vulnerability of assets that are tagged within CentOS systems. I would say both the tool and the user must work together to get good results.

I have been using Axonius for the past year.

Stability-wise, Axonius has failed once, but it was an error on our part and not the solution. I would rate the stability of Axonius a ten out of ten.

The Axonius customer support team is excellent, and they resolved our queries within minutes.

I was not involved in the initial setup process. But as per the deployment team, it is a relatively straightforward tool, especially if you're good at writing queries. Axonius has all the information so neatly documented that if a non-technical person looks at the dashboard, they can set it up. The solution was deployed on-premises, but now we are migrating to the cloud.

We are on a subscription model.

I would advise the new users that Axonius is an asset management tool. If you have a lot of assets that are not registered or have not been assigned, then Axonius is one of the tools you could use to tag your assets individually. Axonius makes your entire life easier when you want to know where each asset is.

We have a policy in place regarding the usage of AI. We have yet to figure out the security measures for how our data will be fed into Axonius and how it will be used to train the model; hence, we will not be using AI for now. Another piece of advice is that the reporting feature is brilliant. You'll have one of the best reports if you know how to get what you want from the query tools.

Overall, I would rate the solution a nine out of ten.