IBM Records Manager (IRM) is an electronic records technology that manages enterprise electronic records and records of physical objects, such as documents and media, throughout their life cycle from creation to disposition. Within the IRM, the two types of record are treated the same. IRM is used to store descriptive metadata about the objects, and track that information within the object’s profile. It provides life cycle records retention management for various applications, such as e-mail, document management, workflow, imaging, and groupware. In addition, Records Manager can use IBM® DB2® Content Manager to serve as a document repository, but this is not required in the evaluated configuration.
\r\nRecords Manager does not include a predefined file plan (specifying how records are organized), or a predefined user interface and workflow. This means that administrators of organizations that employ records management procedures are able to use the TOE to design their own custom file plan and determine the users that will have access to the file plan.
\r\nThe file plan structure comprises file plan components. There are two types of file plan component:
\r\nThe Records administrator creates file plan component definitions, which specify the types of file plan component that will exist in the file plan. Each file plan component in a file plan is an instantiation of a file plan component definition.
","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® Records Manager V8.4 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 2.3. Science Applications International Corporation (SAIC) determined that the evaluation assurance level (EAL) for the product is EAL 3 augmented with ALC_FLR.2 family of assurance requirements. The product, when configured as specified in the IBM Records Manager Version 8 Release 4 Planning and Installing Your Records Management System and the IBM Records Manager System Administration Guide Version 8 Release 4, satisfies all of the security functional requirements stated in the IBM® Records Manager V8.4 Security Target, Version 0.85. Two Validators on behalf of the CCEVS Validation Body monitored the evaluation carried out by SAIC. The evaluation was completed in November 2008. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report, (report number CCEVS-VR-VID10222-2009, dated 25 February 2009) prepared by CCEVS.
","environmental_strengths":"The TOE is a commercial product whose users require a low to moderate level of independently assured security. IBM® Records Manager V8.4 is targeted at a relatively benign environment with good physical access security and competent administrators. Within such environments, it is assumed that attackers will have little attack potential. The security environment also assumes that the TOE components are physically protected.
\r\nIBM® Records Manager V8.4 supports the following five security functions:
\r\nSecurity Audit
\r\nThe TOE generates audit data and provides an interface, IRM Web Admin, to review audit logs. Audit information generated by the TOE includes date and time of the event, type of event, the identity of the user that caused the event to be generated and the outcome (success or failure) of the event. The TOE restricts the ability to search and review audit data to authorized administrators and provides authorized administrators with the capability to select what auditable events will be audited. The TOE also provides an interface for purging audit records, which is restricted to authorized administrators. The audit records are stored and protected by the underlying database in the IT environment. The IT environment also provides the timestamp for the audit records
\r\nUser Data Protection
\r\nThe IRM Engine component enforces an Access Control Security Function Policy (SFP) which restricts access to the file plan components. This protection requires that users of the TOE be authenticated before any access is granted to file plan components. The Access Control SFP can be configured as either an ACL-based policy or as a Role-based policy. The ACL-Based policy uses an Access Control List (ACL) to determine what users and groups can access a file plan component and with what permissions. The Role-based policy also uses ACLs to identify which users and/or groups can access a file plan component, but the access permissions granted to the user are based on defined records management roles that the user is associated with.
\r\nBoth the ACL-Based and the Role-based policies can also provide additional access controls based on hierarchical security classifications and on non-hierarchical security markings (called security descriptors in the TOE). Note, however, that the TOE does not enforce a full mandatory access control policy. In particular, while a user cannot read a file plan component that has a higher classification than the user’s assigned clearance level, a user with appropriate permissions can create and update file plan components with a lower classification level—the TOE does not prevent “write down” operations.
\r\nIdentification and Authentication
\r\nAll users of the TOE must have a user account defined in the TOE. The TOE supports two types of users—local and host. A local user is created within the TOE and can log on to the Administrator Web client to perform administrative tasks. A host user is created and exists within the host application. Host users can access the TOE in two ways: from within the host application; and by logging on to the TOE. From the host application, the TOE needs only to know the identity of the host user. It assumes that the host application has already authenticated the user. Host users can also directly log on to the TOE. When logging on, host users must select the host they belong to and use their host user name and password. The TOE authenticates the user name and password with the host application before allowing the user to log on.
\r\nSecurity Management
\r\nThe IRM Web Admin provides authorized administrators the capability to manage the security-related functions and attributes, such as the audit function, management of users and their associated data.
\r\nProtection of the TSF
\r\nRecords Manager provides the mechanisms to enforce the access control policy ensuring that only authorized users with the appropriate privilege(s) are given access to the resources.
","features":[]}