The IBM Informix Dynamic Server (IDS) product is a relational database management system (RDBMS) sold as an application to be installed on a commercial operating system. The IBM IDS 11.5 is the current version of a prior release of the same product that had been previously evaluated. INFORMIX-Online/Secure 5.0, which has since been renamed Information Dynamic Server, was evaluated under the National Security Agency (NSA) Trusted product Evaluation Program (TPEP) at the C2 and B1 levels of the Trusted Database Interpretation (TDI) of the Trusted Computer System Evaluation Criteria (TCSEC) in 1994.
\r\n\r\n
The IDS is an RDBMS designed primarily to implement databases that can be manipulated using Structured Query Language (SQL) statements. The IDS is an application realized by a collection of cooperating processes. As an application, IDS depends on the underlying operating system for its execution environment and communication services as well as for storage mechanisms for itself, its configuration, and its databases. It also depends on the underlying operating system for protection of its resources for its own protection and also for the differentiation and protection of its clients.
\r\n\r\n
The IDS acts as a server servicing requests of local clients on the same host operating system and on other hosts using network communication mechanisms. The IDS offers a proprietary SQLI protocol to its own clients as well as Distributed Relational Database Architecture (DRDA) support for other clients
","evaluation_configuration":null,"security_evaluation_summary":"The evaluation was carried out in accordance with the Common Criteria Evaluation and Validation Scheme (CCEVS) process and scheme. The criteria against which the IBM IDS TOE was judged are described in the Common Criteria for Information Technology Security Evaluation, Version 2.3. The evaluation methodology used by the evaluation team to conduct the evaluation is the Common Methodology for Information Technology Security Evaluation, Version 1.0. Science Applications International Corporation (SAIC) determined that the evaluation assurance level (EAL) for the product is EAL 4 augmented with ALC_FLR.2. The product, when delivered configured as identified in IBM Informix Common Criteria Certification: Requirements for Informix Dynamic Server document, satisfies all of the security functional requirements stated in the IBM Informix Dynamic Server Version 11.5 Security Target (Version 1.0). The project underwent three Validation Oversight Review (VOR) panel reviews. The evaluation was completed in January 2009. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report, (report number CCEVS-VR-VID10192-2009, dated 17 February 2009) prepared by CCEVS.
","environmental_strengths":"The logical boundaries of IDS are realized in the security functions that it implements. These security functions are realized at the IDS interfaces that service client requests (SQLI and DRDA for both local and remote clients) and via the administrator commands. Each of these security functions is summarized below.
\r\n\r\n
Security Audit - The IDS has the ability to audit security relevant events related to its security functions. An authorized administrator, using the onaudit utility program, can enable and disable the audit feature and can select specifically which security relevant events should be audited based on event type and user.
\r\nAudit records are stored within files in the IT environment. The onshowaudit utility allows an authorized administrator to extract the audit records from the audit trail into a file that could potentially be viewed directly using tools available in the IT environment or alternately it can be loaded into an IDS database table, using dbload, so that the features of IDS can be used to more effectively review the audit records with searching and sorting capabilities.
\r\n\r\n
Access Control - The IDS associates privileges with each individual user. These privileges are associated with operations that can be performed on the objects (e.g., database) that are implemented by the IDS. The IDS uses identities, privileges, and access control lists associated with users and objects to determine whether specific operations will be allowed when attempted by client users.
\r\n\r\n
IDS implements a few roles, each having special privileges that are not available to normal users. These roles are associated with groups defined in the underlying operating system and users are assigned roles by virtue of their membership in those groups. Note that users in these roles can execute certain privileged SQL commands while ‘privileges’ are associated with access permissions for IDS objects. For this ST, references to the “authorized administrator” role are implemented in the IDS as any of the following roles: Operating System Administrator (OSA), Database System Security Officer (DBSSO), Database System Administrator (DBSA), Database Security Administrator (DBSECADM), or Audit Analysis Officer (AAO). While the IDS offers these different roles with distinct responsibilities, this ST does not make specific role separation claims and hence treats them all logically as a single role – the authorized administrator. References to the “user” role are implemented in the IDS as any user not a member of one of the administrative roles.
\r\n\r\n
In addition to using privileges and authorities to control access, IDS implements a label-based access control (LBAC) mechanism. The IDS DBSECADM can grant (or revoke) security labels and exemptions to (or from) users as well as create and drop LBAC security objects in order to define LBAC polices for specific database tables. Once a table is configured with a LBAC policy (i.e., the table is LBAC protected relative to either rows or columns), users must additionally satisfy the LBAC access rules in order to access or modify the applicable table rows or columns.
\r\n\r\n
Identification & Authentication - The IDS requires all users to be identified before allowing them access to IDS resources. The IT environment is responsible for user authentication while the IDS requires the user identity returned by the IT environment to associate IDS credentials (e.g., privileges) with the authenticated user.
\r\n\r\n
Security Management - The IDS includes the roles of authorized administrator and user implemented using IT environment groups, and associated IDS roles (see above) and (access control) privileges, and allows individual users to be assigned to those roles by virtue of the assignment of the applicable groups (in the IT environment) and privileges to their identity. Management of the IDS TOE, including the ability to select and review audit records, is restricted to authorized administrators and access to the TOE (e.g., the utility programs and associated data and configuration files) through its IT environment. Management of the IDS objects is restricted to those users that are assigned the appropriate privileges to do so.
\r\nNote that for the most part management of the TOE is accomplished via SQL statements that can be issued interactively using the dbaccess utility.
\r\n\r\n
TOE Protection - The IDS executes within processes provided by the host operating system. However, it is designed to not share its process space with non-TOE entities in order to ensure that its resources are protected. The IDS has been designed so that each of its interfaces performs the necessary access checks before allowing access to IDS resources.
","features":[]}