Account level security

 

All actions performed on the server are performed by an account. Some accounts, such as ADMIN and Server Admin accounts can perform any task on any object. Lower-level accounts, such as owner and user accounts, can perform tasks only on objects that they own or for which they have been granted privileges. There are five types of accounts:

ADMIN

Server Admin (SA)

Database Admin (DBA)

Owner Account (Schema)

User Account

 

ADMIN account

ADMIN-level security (ALS) a special security type that is available only to the ADMIN account. There is only one ADMIN account and it has the case insensitive name "admin". ADMIN has the ultimate authority. It can do everything without restriction.

Unlike other accounts, ADMIN cannot be removed or altered by any other account. This makes ADMIN the ultimate failsafe account. Because it is all powerful, it should have a very secure password.

The ADMIN account should be used only to create Server Administrator accounts. After that, it should not be used except to recover from an attack or a severe misconfiguration by a lower-level account.

 

Server Administrator Account

A Server Admin Account (SA) can do everything except modify the ADMIN account or modify other Server Admin Accounts. This means a Server Admin Account cannot create other Server Admin Accounts, delete the ADMIN account, or change the password for ADMIN or other Server Admin accounts.

The primary purpose of a Server Admin Account is to authorize Owner Accounts to create and own objects in specific databases. Allowing applications and analysts to create and own database objects is a core purpose of a FairCom server.

A Server Admin Account should be used only to create and manage security for User Accounts, Owner Accounts, Groups, and Databases. This allows the Server Admin Accounts to be used infrequently by a small group of trusted users.

 

Database Administrator Account

A Database Administrator (DBA) Account manages database-level privileges including all the objects in a database and their privileges. This includes table-level, row-level, field-level, and value-level privileges. A DBA can grant and revoke all database-level security privileges to other accounts – including granting and revoking the DBA privilege.

 

Owner/Schema Account

An Owner Account has privileges to create objects. The account that creates an object is the sole "owner" of the object. Being the owner automatically gives the account full control over all privileges for the objects it creates.

An Owner Account is typically given to an application to create and manage its own objects. It is also given to an analyst role to create, alter, and delete tables and objects that they use.

An Owner Account has limitations, which enhance security. Unless an owner account has been granted specific privileges to do more, it only has access to the objects that it creates. Thus, an Owner Account cannot alter or delete objects created by other Owner Accounts, and it cannot access another owner’s objects.

Each Owner Account is also a schema that contains all objects created by the account. An Owner Account can be used purely as a schema, which exists only to contain objects for use by user accounts. In this case, a Schema Account is not allowed to log into the server. Instead, a Server Admin account impersonates a Schema Account and creates objects on its behalf. This allows the schema to exist purely to contain objects and to protect its objects from being modified by user accounts.

 

User Account

A User Account is used to log into the server to perform tasks on objects for which it has privileges. A User Account can be used by people, software, and machines.

A User Account is a non-owner account. It does not have privileges to create objects. A user account is not a schema because it does not own objects and is not a logical container of objects.

If a Server Admin grants the create privilege to a User Account, the account becomes an Owner Account and a schema.