Each Sybase record identifies account login credentials, database information and target hosts (IPs) for authenticating to Sybase Adaptive Server Enterprise (ASE) instances.
login credentials are required?
You'll need to supply a user name and password, the database name you want to authenticate to and the port the database is on. We'll find the instance based on the port number that you enter. For scanning Unix hosts, you'll also need to provide the database installation directory.
Note - You cannot create multiple records with the same database name and port combination.
Tip - It is strongly recommended that you create one or more dedicated user accounts to be used solely by the scanning engine to authenticate to Sybase database instances.
to enable password encryption?
Enable this option when your Sybase database instance requires an encrypted password for successful login. If password encryption is required and you do not enable this option then authentication will fail.
us to Auto discover database names?
Enable this option and we'll find all Sybase database names on each host for you. This means you no longer have to create a separate Sybase record for each database name. Create one record with Auto Discover Databases enabled to authenticate to multiple databases on the same host. To create a record you must either specify the database name or select Auto discover. These are mutually exclusive.
IPs should I add to my record?
Select the target compliance hosts (IPs) to authenticate to.
We support integration with multiple third party password vaults. Just go to Scans > Authentication > Vaults and tell us about your vault system. Then choose Authentication Vault in your record and select your vault name. At scan time, we'll authenticate to hosts using the account name in your record and the password we find in your vault.
When a Unit Manager edits a record, the Unit Manager only sees the IPs in the record that they have permission to. Any changes made by the Unit Manager to the record settings will apply to all hosts defined in the record, regardless of whether all hosts belong to the user's business unit. The record may contain more IPs that are not visible to the Unit Manager.