SQL/MP Installation and Management Guide

Planning Database Security and Recovery
HP NonStop SQL/MP Installation and Management Guide—523353-004
4-4
Guidelines for Security Schemes
authority to purge an object can drop that object, an authorization scheme should limit
the authority for purging.
For an authorization scheme, you should establish catalog boundaries along the lines
of application and user access requirements. Associate catalogs with sets of tables
logically associated or used together. With this scheme, security follows the catalogs
you choose.
Guidelines for Security Schemes
When planning a security scheme, consider these guidelines:
•
Security issues closely follow the use of three categories of SQL statements.
These categories and the most frequent users of each category are:
°
Data Definition Language (DDL) statements, issued by the database
administrator
°
Data Control Language (DCL) statements, issued by application users
°
Data Manipulation Language (DML) statements, issued by application users
•
The local owner of a table, view, index, collation, or program, the local group
manager, the local super ID, or the remote owner with purge authority generally
has the authority to perform DDL statements on these objects. Authority to purge
an object is required to drop a table, index, view, SQL program stored in a
Guardian file, or collation from the database.
•
A group manager (user 255) can read or write to any local table owned by a group
member and can execute an SQL program that runs in the Guardian environment
that is owned by any group member. Remote tables, views, and programs must be
secured for remote access. When a statement requiring access to an object is
compiled, the catalog that describes the object must be accessible by the group
manager. To alter attributes of a table, view, index, collation, or SQL program
stored in the Guardian environment, or to run a DDL statement, a group manager
requires purge authority.
•
SQL/MP security issues cover two areas:
°
Security of a catalog that contains descriptions of SQL objects
°
Security of SQL objects
Allowing access to the catalog does not automatically allow access to the objects
described in that catalog. Access to the catalog is required in addition to access to
the objects for execution of:
°
DDL statements
°
DML statement compilations for SQLCI or dynamic SQL
°
Most utility commands
°
SQL program compilations