Quasar Scan user guide
SQL Configuration Options
An additional set of quasaragent.cfg options are used to tell Agents which SQL databases to scan, and how to connect to them. An example quasaragent.cfg including SQL DB connection info is as follows:
[db.Oracle]
dbtype = "oracle"
use_instant_client = true
instant_client_dir = "C:/ProgramData/QuasarScan/Agent/instantclient_23_6/"
[db.Oracle.connect]
user = "c##quasar"
password = "asdfasdf"
[db.MYSQL]
dbtype = "mysql"
[db.MYSQL.connect]
host = "demolin.test"
user = "demo"
passwd = "demo"
db = "testlab"
[db.Postgres]
dbtype = "postgresql"
[db.Postgres.connect]
host = "demolin.test"
port = 5432
dbname = "testlab"
user = "postgres"
password = "1234"
[db.MSSQL]
dbtype = "sqlserver"
connection_string = "DRIVER={SQL Server};SERVER=dbwin.test;Network Library=DBMSSOCN;DATABASE=testlab;UID=sa;Pwd=1234"
[db.MSSQL.connect]
timeout = 5
[db.MongoDB]
dbtype = "mongo"
[db.MongoDB.connect]
host = "demolin.test"
authMechanism = "MONGODB-X509"
tls = true
tlsCertificateKeyFile = "C:/ProgramData/QuasarScan/client.pem"
tlsCAFile = "C:/ProgramData/QuasarScan/ca.pem"
Scanner Settings
Common sql_scanner settings are as follows:
topnrows
Limits the number of rows to scan. This translates into ‘SELECT TOP n’ in MS SQL, for example.
Suitable values for this setting are best derived by your card data analysts and SQL DBAs working together to determine a sampling policy. It is not recommended to set this to an unduly high number or leave it out altogether as large tables could result in unrealistic scan times.
Database Settings
Database-specific settings (in scan_databases) are as follows:
db_scan_name
“quasar-centric” alias name for the database being scanned. This is user defined, and appears in hits paths and report outputs.
q_module
Type of database. Supported DB types are mysql, sqlserver, and msaccess.
connect
The database ODBC connection string.
See http://connectionstrings.com for more information.
topnrows
As above. This is a database-specific override of the common setting.