Saint is a venerable product with its roots in the earliest days of automated vulnerability assessment. It has been dressed up in a new suit of clothes since becoming a commercial product, but retains its strong Unix roots.

Saint is, first and foremost, a vulnerability scanner. In that regard, it is very similar to Nessus, but its user interface is about as clean as one would expect and it is web-based, making any web browser the platform for the GUI.

Saint is available in a variety of configurations, including software for installation on a Unix or Linux computer, SaintBox, an appliance, and WebSaint, a remote scanning service that allows the organization to initiate scanning over the web and then log back in to view results.

Finally, an optional remote console, SaintManager, enables users to manage medium-to-large networks, including scan, policy and results management and reporting using an SQL database.

Support is acceptable and there is a strong web presence adding to the support in an on-demand fashion. Saint is generally easy to use, although not all Linuxes behave well. RedHat 7.2 went very smoothly, even in a VMWare environment, but Mandrake 10.2 did not allow a clean installation and Saint had to be uninstalled.

Features, considered in the contest of this type of scanner were very good. However, some additions, such as an API and scripting language that allows users to write vulnerability tests would be useful. We understand that is in the pipeline.

Generally, Saint is an extremely strong workhorse vulnerability assessment tool, quite scalable and true to its mature vulnerability assessment roots, while presenting an easy-to-use and configure user environment.

Performance was strong and the scanner made quick work of our test network, identifying all of the devices, real and virtual, and delivering a very credible scan report. Generally, we view Saint as a very strong, although plain vanilla, vulnerability assessment tool worthy of recommendation.