Home
Security
You can secure your Informix® database server and the data that is stored in your Informix databases. You can encrypt data, secure connections, control user privileges and access, and audit data security.
Security in HCL Informix®
The Informix® Security Guide documents methods for keeping your data secure by preventing unauthorized viewing and altering of data or database objects, including how to use the secure-auditing facility of the database server.
Securing data
Label-Based Access Control
You can use label-based access control (LBAC), an implementation of multi-level security (MLS), to control who has read access and who has write access to individual rows and columns of data.
Protecting Rows and Columns
Protect rows and columns by associating them with security objects by including clauses in the CREATE TABLE and ALTER TABLE statements.
Applying row-level protection
Protect row-level data by associating the table with a security policy and inserting an IDSSECURITYLABEL-type column.

Security
You can secure your Informix® database server and the data that is stored in your Informix databases. You can encrypt data, secure connections, control user privileges and access, and audit data security.
- Security in HCL Informix®
  The Informix® Security Guide documents methods for keeping your data secure by preventing unauthorized viewing and altering of data or database objects, including how to use the secure-auditing facility of the database server.
  - Securing data
    - HCL Informix® directory security
      utilities and product directories are secure by default.
    - Network data encryption
      Use network encryption to encrypt data transmitted between server and client, and between server and other server.
    - Column-level encryption
      You can use column-level encryption to store sensitive data in an encrypted format. After encrypting sensitive data, such as credit card numbers, only users who can provide a secret password can decrypt the data.
    - Connection security
      You can administer the security of the connections to the database server by using authentication and authorization processes.
    - Discretionary access control
      Discretionary access control verifies whether the user who is attempting to perform an operation has been granted the required privileges to perform that operation.
    - Label-Based Access Control
      You can use label-based access control (LBAC), an implementation of multi-level security (MLS), to control who has read access and who has write access to individual rows and columns of data.
      - Configuring Label-Based Access Control
        The general procedure involves a few SQL-based tasks that define precise but flexible database security objects.
      - How security labels control access
        Security labels rely on security label components to store information about the classification of data and about which users have access authority.
      - DBSECADM role in LBAC
        The database security administrator role (DBSECADM) is required to create and maintain label-based access control security objects.
      - Security label components
        Security label components are security objects for defining security policies. The elements of these components are used to define security labels, which control access to protected tables.
      - Security policies
        Security policies are database objects that you create and use to protect tables from unauthorized access.
      - Security labels
        Security labels are objects applied to rows and columns in order to protect these data, and granted to users to give them access to protected data.
      - Protecting Rows and Columns
        Protect rows and columns by associating them with security objects by including clauses in the CREATE TABLE and ALTER TABLE statements.
        Applying row-level protection
        Protect row-level data by associating the table with a security policy and inserting an IDSSECURITYLABEL-type column.
        Applying column-level protection
        Protect column-level data by associating the table with a security policy and attaching a security label to one or more columns.
      - Exemptions
        Exemptions modify security credentials of users by disabling one or more of the IDSLBACRULES for a component type in a security policy.
      - Maintaining a label-based access-control implementation
        Optimizing database performance can require adjusting the values of configuration parameters for security policies and user credentials.
      - HCL Informix® Security Considerations
        The wide range of Informix® capabilities requires certain precautions and planning to ensure protected tables can be accessed appropriately.
      - LBAC and other HCL Informix® features
        Informix® has non-security functionality that operates seamlessly with label-based access control.
  - Auditing data security

Applying row-level protection

Protect row-level data by associating the table with a security policy and inserting an IDSSECURITYLABEL-type column.

Before you begin

About this task

There are two methods for applying row-level protection:

Procedure

For a new table: Use the CREATE TABLE statement with the appropriate IDSSECURITYLABEL and SECURITY POLICY clauses, as described in Informix® Guide to SQL: Syntax.
For an existing table: Use the ALTER TABLE statement with the appropriate IDSSECURITYLABEL and ADD SECURITY POLICY clauses, as described in Informix® Guide to SQL: Syntax.

Example

The following example shows a statement that applies row-level protection when you create a new table (T1) by using the security policy named company and the security label named label2.

CREATE TABLE T1
   (C1 IDSSECURITYLABEL,
   C2 int,
   C3 char (10))
   SECURITY POLICY company;

The following statement provides an example of applying row-level protection on a table (T2) that already exists on the database, by using the security policy named company. The default value for C1 is label3.

ALTER TABLE T2
  ADD (C1 IDSSECURITYLABEL DEFAULT 'label3'),
  ADD SECURITY POLICY company;

What to do next