NetBrain is a very simple tool, however, it's not an NDR. It doesn't have the capabilities to run PCAPs and so on. The solution could integrate more automation. If the product has to be evolved, it should have more added functionality in the sense of adding PCAPs functionality and looking at the L7 kind of traffic. Also, NetBrain could be very useful if it supported OT (operational technology). I hear a lot of industrial customers, mainly belonging to oil and gas, running the SCADA systems. NetBrain is very good when it comes to IT, however, if they built in the OT part as well, so that we can look at some SCADA systems, HMI, PLCs, and things like that, it would be ideal. It would also give full visibility of what is happening in and around the OT side. Maybe down the line, they will need to add these capabilities.
Senior System Engineer at a healthcare company with 10,001+ employees
Real User
2020-09-21T06:33:00Z
Sep 21, 2020
Creating the parsers and QFs from model to model show that the IP interface brief isn't consistent. From a 6500 to a 3750 to a 9300 Cisco switch models, the show IP interface brief is different. There's extra columns and you have to parse for those. Setting those up is a bit of a challenge on this particular version. From what I've been able to gather, the next version, 8.X, is better at that and has more of those, but my perception is that building the parsers out is a bit of a challenge. I've done it but it's a challenge. Then there's a similar function again with the POE that didn't have the show power in line command and I had to figure that out. Again, that table comes out in a very unique state and then requires parsing down and pulling that out. It's basically using a CLI scraping which should be simplified and a more intuitive process. I don't know if the newer version does APIs or not and if that would have been any easier or better to manipulate, I have no idea.
Director at a tech services company with 1-10 employees
Reseller
2019-09-22T06:41:00Z
Sep 22, 2019
The pricing needs to be improved. It would be nice if the setup was a little simpler. Also, if the solution could provide more training materials for new people coming into our company so they can quickly learn how to use the functionalities.
Senior Network Architect at ZAG Technical Services
MSP
2019-07-02T06:57:00Z
Jul 2, 2019
The product could be improved with easier, better cataloging of the license within a network. Right now it seems a little cumbersome to actually be able to see just a lifting of the devices that are discovered or devices that weren't discovered and why. Better cataloging would resolve that issue.
Managing today’s networks with yesterday’s manual processes is no longer a viable solution. NetBrain’s network automation platform provides actionable insights into your network to help you make better and faster decisions - particularly when you’re troubleshooting, securing, and making changes to the network.
NetBrain is a very simple tool, however, it's not an NDR. It doesn't have the capabilities to run PCAPs and so on. The solution could integrate more automation. If the product has to be evolved, it should have more added functionality in the sense of adding PCAPs functionality and looking at the L7 kind of traffic. Also, NetBrain could be very useful if it supported OT (operational technology). I hear a lot of industrial customers, mainly belonging to oil and gas, running the SCADA systems. NetBrain is very good when it comes to IT, however, if they built in the OT part as well, so that we can look at some SCADA systems, HMI, PLCs, and things like that, it would be ideal. It would also give full visibility of what is happening in and around the OT side. Maybe down the line, they will need to add these capabilities.
Each device needs to be configured to allow NetBrain to poll for the information it needs, which can be very time-consuming for a large network.
Creating the parsers and QFs from model to model show that the IP interface brief isn't consistent. From a 6500 to a 3750 to a 9300 Cisco switch models, the show IP interface brief is different. There's extra columns and you have to parse for those. Setting those up is a bit of a challenge on this particular version. From what I've been able to gather, the next version, 8.X, is better at that and has more of those, but my perception is that building the parsers out is a bit of a challenge. I've done it but it's a challenge. Then there's a similar function again with the POE that didn't have the show power in line command and I had to figure that out. Again, that table comes out in a very unique state and then requires parsing down and pulling that out. It's basically using a CLI scraping which should be simplified and a more intuitive process. I don't know if the newer version does APIs or not and if that would have been any easier or better to manipulate, I have no idea.
The pricing needs to be improved. It would be nice if the setup was a little simpler. Also, if the solution could provide more training materials for new people coming into our company so they can quickly learn how to use the functionalities.
The product could be improved with easier, better cataloging of the license within a network. Right now it seems a little cumbersome to actually be able to see just a lifting of the devices that are discovered or devices that weren't discovered and why. Better cataloging would resolve that issue.