RedSeal Reviews

We run three different networks with multiple VLANs across each of them. We're using it internally but looking at potentially using it to support other companies.

Because we work a lot of assessments, RedSeal helps us to validate certain security practices that are required. They have 148 best practices that are laid out, and the combination of those best practices along with some of the other capabilities, such as network mapping where it lays out the tracking and identification of devices, supports a lot of the requirements from government or companies that work with government agencies.

RedSeal looks at where you correlate the different practices as it relates to those defined by the assessment requirements put in place by the government contractors. Once they've done that, it will ease the time. While there is a dashboard with all of the information, you've got to go to the right place to find it and validate it. With the consolidation done, you get that as output and it ultimately saves us time when it comes to determining compliance.

The most valuable features are network mapping and configuration. It definitely speeds up the identification of mismatches and issues related to configuration and provides a good way ahead for remediation of those deficiencies.

The scorecard in resiliencies is helpful because you can get a snapshot look of it based on taking all of the data in.

From a front-end perspective, it just a superb job. RedSeal brings a lot, but it also brings an understanding that you're adding to it in order to get the full picture.

Once you flush out your layer two and layer three by bringing in scans, you tie in RedSeal with your SIEM. The dashboard makes moving forward very easy as it relates to the operation, which is something that we're very happy with.

When you're pulling in all of the vulnerabilities using the scanning tool that has been used, it is overlaid on the structure and helps to build it within RedSeal. This gives you one entry point to get a pretty good look at a company.

The dashboard should be improved to make correlating data easier to do. As it is now, if I go into RedSeal then I may have to look at six or seven practices, plus go to a configuration tab and then look at the mapping to identify one security practice that's been defined within the CMMC model.

It would like to see a feature that gives specifics about different types of compliance. For example, different tabs for SCADA, HIPAA, CMMC, 800-53, and PCI, would be helpful for having everything available in one location. As it is now, I have to view Excel spreadsheets to get that answer. Also, these things change depending on whether you are dealing with a DOD compliance effort versus medical compliance.

We have been using RedSeal for more than six months.

I am comfortable with the product. We have not seen any issues at all, in terms of stability.

We are currently looking at building relationships with other companies to improve our supply chain, and it is definitely scalable enough to support that.

The technical support is really good. They have a personal touch and build a relationship with you that helps with integrating the product. They really help when it comes to having a full understanding of how it works and it makes a big difference because they don't just leave you stranded.

My experience is that the technical support is structured to make sure that you get what RedSeal can provide.

The initial setup is straightforward, although it is a matter of importing all of the other sources of info that really makes it work well. For example, you're getting network layer seven, part of layer three, and all of those things that are associated with them. But, when you want the full picture, it takes the additional step. You need to load the scans and get tie-in to the SIEM, as well as everything else, to get the full utility out of RedSeal.

The technical support provided really eases the setup process.

The pricing is based on the number of endpoints and devices, and we have seen it range from mid-five figures to low six figures.

My advice for anybody who is implementing this solution is to have a good understanding of what RedSeal brings to the table, as well as what it is that you need to bring to the table to get full usage out of it. RedSeal comes in and sets the foundation and gives you the front-end, and then you have to add things like your scanned data. If you don't already have a scanner such as Nessus then you won't get a full picture. The team at RedSeal makes it clear that these plugins are essential to get the full benefit of the product.

Overall, I am very happy with the way the product is working.

I would rate this solution an eight out of ten.

We had a distributing environment, and we used RedSeal to look into the gaps in existing network connectivities. We looked into if any of the forbidden accesses are open. We also looked at the points from where the traffic was going in and out and the policies that were configured on the network devices but were not as per compliance.

We had to provide the configuration of our network, and then we could see the routes that are being used to transfer the traffic from one point to another. Based on that, we could control how specific traffic should be transferred from one point to another. If a device was not declared as a perimeter firewall or a perimeter router but was configured to communicate with the internet or fiber links, we would block it.

RedSeal integrates the network and gives us a visual or graphical overview of our network. If an organization is geographically dispersed, for instance, with one office in Canada and one office in the Philippines, the whole network, including all devices, is integrated into RedSeal, and you can see from where the traffic is going in and out.

Sometimes, it required us to refresh the configuration. When we integrated any of the configurations into the device, sometimes, it could not detect the exact picture of that device. So, we had to reset the device to see that if it was giving true-positive results or false-positive results. In some cases, we were not able to get true-positive results. There was some kind of bug in that version.

Its interface is not user-friendly and needs to be improved. It takes time to understand the interface and various options. Skybox has quite a user-friendly interface.

They could provide a feature for compliance audit policy if it is already not there. A compliance audit policy ensures that all configurations are based on the best practices standards, such as CIS benchmarks standard or other similar standards. It provides visibility about whether your device configuration is based on best practices or not. Usually, such a feature is provided by other solutions such as Meteor or Tenable Nessus.

I have used RedSeal in my previous organization for one year.

Their technical support is good.

They were already using this solution when I joined that organization.

It is straightforward and not complex. You simply have to apply or provide the configurations of your devices. You can integrate a number of devices based on the running configuration and network configuration, or you can integrate all network devices.

Its implementation took around a month, and the implementation strategy was to first integrate all perimeter devices. We first covered those devices that were public-facing or connected with our clients in the data center. After configuring all of our perimeter devices, we started integrating our internal network at the distribution layer or the core layer. So, our implementation was divided into two phases. In the first phase, we integrated all devices deployed on the front line, and in the second phase, we moved to our distribution layer or the core layer.

We got assistance from the vendor who provided us the solution. In case of any requirement, we got assistance from them.

I would rate RedSeal a seven out of ten. It requires minor improvements in terms of the user interface and new features.