EDAcS collects, archives, and reports remote user connections for security monitoring and investigations by using the RADIUS protocol (RFC 2866). EDAcS consists of two parts, the "edacsdb" database loader and the "edacsweb" reporting CGIs. The two parts can be installed independent of each other, and can reside on different systems. Both need connectivity to Oracle as the backend database system, using Oracle OCI with libsqlora.
INOVASC is an independent, Web-based scan client for the OpenVAS vulnerability assessment system. The development goals were pure simplicity, using basic Web CGI technology written in 'C'. INOVASC connects directly to the OpenVAS scan server (openvassd) using the OTP protocol. It allows you to define a scan configuration, to initiate the scan, and to display the returned scan results. The benefit is an easy to use, centrally located scan client that keeps all scan results in one place. The design is kept simple; even a non-IT person can start a scan.
NessusWC provides a simple HTTP Web interface to the Nessus Security Scanner. It connects to local or remote Nessus version 2 daemons via SSL (using OpenSSL libraries), retrieves the plugins, configures a scan for a single target host, and saves the results in HTML format. As a result, even users with limited security knowledge can scan their machines. Scan results are stored in a central place.
NessusWC failure when plugin list reached 20000 It just happened that the Nessus plugin count went over 20000. No need to worry. Please adjust in nessuswc.h the parameter #define MAXPLUGS 20000 to,...
Re: Password Bug This is fixed in Version 1.2.1 (http://www.frank4dd.com/nessuswc/nessuswc-v1.2.1.tar.gz). Thanks for reporting, Marcelo.
Re: Error While compiling Dear Ritesh, There seems to be a problem with your OpenSSL installation. The compiler complains about a missing header file krb5.h (used for OpenSSL Kerberos 5 suppor...
FIXED: Bug in "List of Scan Results" does not correctly display target IP 127.0.0.1 Done.
Bug in "List of Scan Results" does not correctly display target IP 127.0.0.1 The scan result file itself has the correct IP, just the listing is incorrect.