Each Sybase record identifies account login credentials, database information and target hosts (IPs) for authenticating to Sybase Adaptive Server Enterprise (ASE) instances.
do I get started?
- Go to Scans > Authentication.
- Check that you already have a record defined for each host running database instances.
- Create a Sybase record for the database instance. Go to New > Databases > Sybase.
login credentials are required?
Provide basic login credentials (username and password) to be used for authentication or get the password from a supported password vault.
Tell us the database name to authenticate to and the port the database is running on. The installation directory name is required only for Unix based hosts.
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.