What is our primary use case?
I used Nmap to identify and track specific communication protocols on a restricted government network to verify claims of illegal activity and ultimately prove that the network was not being used for that purpose.
The area we operate in is very restricted. It's a hilly area for telecommunications, and it's a restricted area.
So, as we operate there for one of the government projects, we implemented the setup for communication purposes. However, the authority received a claim from a third party that someone was using VIP on this network, and being a purely government entity, does not have any intention of that. The spectrum authority claimed that this was the situation, and they initiated a letter and established a team to verify this. At that time, they weren't aware of any software that could track the communication protocols they were using.
So, I used the Nmap solution there. We found every single port, and all the communications, and we proved that there was no VIP-related activity because security-wise, it's illegal.
How has it helped my organization?
Nmap is used for inventory purposes. It is primarily employed for in-depth network monitoring.
Unlike SolarWinds, which doesn't detail each port, Nmap can provide comprehensive insights into traffic, including VPNs, by leveraging SNMP protocols.
Nmap significantly improves network monitoring by providing detailed insights into network activities.
It helped to improve scanning procedures. It can be very helpful for forensic tasks and penetration testing. It's a great tool for those purposes.
Nmap functions help to detect network vulnerabilities. Nmap can identify the source and destination of network traffic, along with the protocol (like TCP or UDP) and port numbers used.
What is most valuable?
The real-time reporting feature of Nmap is particularly valuable. It generates detailed reports on the source and destination IP addresses, the protocols used, and the types of traffic.
This feature is crucial for law enforcement agencies to monitor and analyze network connectivity effectively.
It also has traffic analysis. For example, assessing bandwidth usage and configuring the tool to track specific types of traffic is crucial. Unlike SolarWinds, which requires configuration for this, Nmap has built-in functionality that allows it to check all 4,000 computer ports. It identifies the type of traffic each port is using and can easily generate reports on network communications between computers, whether there are 100 or 1000 in the network.
What needs improvement?
Port scanning can be effectively done with alternative tools. While Nmap is an open-source program, SolarWinds and other commercial products invest in their development. If Nmap could receive similar investments, it could perform better.
Their program development relies heavily on the contributions of the open-source community, like myself.
Many contributors contribute to Nmap by creating Object Identifiers (OIDs) and other elements. So, while Nmap relies on the community, there is definitely potential for commercially viable features that could be added to the public version, differentiating it from the open-source product.
What do I think about the stability of the solution?
The stability of this product is very good, but comparing it directly to something else isn't fair. Nmap has unique features and works differently than other tools.
It runs reliably on Linux platforms. However, on Windows platforms, you might encounter issues like freezing after an hour or three of continuous use.
What do I think about the scalability of the solution?
This product has built-in features. So, the scalability depends on the sizing of the servers.
The logging features, for example, depend on how much storage you have to keep the logs. That, in turn, depends on your application and server size requirements.
Moreover, Nmap is supposedly moving from a free license to a commercial platform.
It is suitable for very small companies. It is a good tool for forensic test purposes.
Which solution did I use previously and why did I switch?
For commercial projects, we can't use Nmap due to potential liabilities. Nmap is typically utilized in scenarios where the client lacks the budget.
It's an open-source tool used for monitoring systems, not just for tracking bandwidth but also for detailing the negotiation levels between client and server protocols.
How was the initial setup?
The initial setup is straightforward.
On Linux, installation is just one command. You type it in, and it's installed and ready to use.
But the user had to know how it operate it. If somebody doesn't have an idea about how to operate, then it will be complex for him.
What's my experience with pricing, setup cost, and licensing?
Nmap is very good. It's an open-source solution. Commerically, only the support service is available.
What other advice do I have?
Overall, I would rate the solution an eight out of ten. Customization is not very user-friendly in Nmap. That's the main reason I wouldn't give it a perfect score.
It is not like SolarWinds. It's not for full network, like, it only does traffic, only monitors types of traffic.
Which deployment model are you using for this solution?
On-premises