- [Presenter] Let's first, take a look at some of
the commercial tools that are available for
automated scanning of databases.
Some of these, we mentioned in earlier lessons
and they are related to automated scanning of servers
and clients on networks, but so many of them
also, have database functionality, as well.
So, let's start with Nessus.
Nessus scans for a variety of different database issues.
It supports Oracle MS SQL server, MYSQL,
PostgreSQL, as well as MongoDB.
Nexpose, is also able to scan for
a variety of database issues,
like default passwords, default configurations,
missing patches, buffer overflows, listening ports,
privilege escalation, things like that.
It supports Oracle MS SQL and MYSQL.
Qualys can remotely detect,
more than 540 database vulnerabilities.
It supports Oracle, MS SQL, MYSQL and postgreSQL.
Imperva Scuba is actually, a purposely built tool
for database testing.
So, let's take a quick look at how
automated scanners would work against databases.
Now, the truth is, they work much the same
that they would, against a server or a client workstation,
that you're scanning for vulnerabilities.
Again, the automated scanner is just an application
that's running on your client machine.
So, let's say, this one is Nessus.
We have our database server,
which is our target
and essentially, what we're gonna do is,
we're gonna tell Nessus, scan this database server,
look for vulnerabilities in the database.
The first thing, that Nessus is gonna do,
or the first thing any automated scanner is gonna do,
is it's gonna send probes to the database server,
to try and find out some information of
what type of server it's running,
what type of database it's running,
so, that it can then send the correct attacks.
Once it finds out the information,
so, let's say, it determined it
MYSQL was running, and it was running version 247,
from there, Nessus is going to
identify in its database, which vulnerabilities
might apply to that specific database version.
Then, it's going to try and send some attacks
against the database server, to see if they actually work.
Based on the responses from the database server,
Nessus will record in its own database,
whether or not, it's a vulnerability or not.
Of course, in the end, it will output a report
telling you if there are high, medium or low vulnerabilities
and then, from there, of course, we need to validate those.