International Business Machines (IBM) FileNet P8 Platform

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	FileNet P8 Platform is the foundation for the integrated International Business Machines (IBM) FileNet products and is required by all IBM Enterprise Content Management software products. It provides a unified enterprise foundation for content management, business process management, and document and process compliance capabilities. This technology has the capability to import, export, and store data in different types of databases, including Oracle Database, Microsoft Structured Query Language (SQL) Server database, and DB2. The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This includes technologies deployed as software installations on VMs within VA-controlled cloud environments (e.g. VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed by an external Cloud Service Provider (i.e. SaaS) are not in the purview of the TRM. For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at: https://dvagov.sharepoint.com/sites/OITECSO
Technology/Standard Usage Requirements:	Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:	This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v24.5
Decision Date:	05/13/2024 at 16:17:11 UTC
Introduced By:	TRM Analysis
Vendor Name:	International Business Machines (IBM)

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

Version	Release Date	Vendor End of Life Date
4.0	03/15/2007	09/30/2011
4.5	10/03/2008	04/30/2014
5.0	12/16/2010	04/30/2016
5.1	08/26/2011	04/30/2017
5.2.x	04/12/2013
5.5.x	12/07/2017

Current Decision Matrix (05/09/2024)

Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.

The VA Decision Matrix displays the current and future VA IT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported. Any major.minor version that is not listed in the VA Decision Matrix is considered unapproved for use.

Legend:

White	Approved: The technology/standard has been approved for use.
Yellow	Approved w/Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Unapproved: This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Divest: VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unapproved may be found on the Decision tab for the specific entry.
Black	Prohibited: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Planning/Evaluation Constraint:The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology approved with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology approved with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

<Past

CY2022

CY2023

CY2024

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

4.0

Unapproved

4.5

Unapproved

5.0

Unapproved

5.1

Unapproved

5.2.x

Divest
[2, 8, 9, 10]

Divest
[10, 11, 12, 13]

Unapproved

5.5.x

Approved w/Constraints
[2, 8, 9, 10]

Approved w/Constraints
[10, 11, 12, 13]

Approved w/Constraints
[11, 12, 13, 14]

Approved w/Constraints
[12, 13, 14, 15]

Approved w/Constraints
[12, 14, 15, 16]

Approved w/Constraints
[12, 15, 16, 17, 18]

Decision Constraints


[1]	Projects should ensure that adequate technical support services are available to sustain the implementation on the project`s platform due to the expansive capabilities of the product.

[2]	Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISO can provide assistance in reviewing the NIST vulnerabilities.

[3]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[4]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[5]	Projects must ensure that adequate technical support services are available to sustain the implementation on the project`s platform due to the expansive capabilities of the product.

[6]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[7]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[8]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[9]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[10]	Projects must ensure that adequate technical support services are available to sustain the implementation on the project`s platform due to the expansive capabilities of the product. This technology must use the latest TRM-approved version of Java Runtime Environment (JRE) - Oracle. Users must ensure that DB2 and Microsoft Structured Query Language (SQL) Server are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)

[11]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500.

[12]	Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISSO (Information System Security Officer) can provide assistance in reviewing the NIST vulnerabilities.

[13]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[14]	Projects must ensure that adequate technical support services are available to sustain the implementation on the project`s platform due to the expansive capabilities of the product. Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM. Users must utilize approved internet browsers, as Microsoft Internet Explorer has reached End of Life status. See Category Tab for details. This technology must use the latest TRM-approved version of Java Runtime Environment (JRE) - Oracle. This technology must use the latest TRM-approved version of Java Development Kit (JDK) - Oracle. Users must ensure that Microsoft Edge, Google Chrome, Firefox, Oracle Database, and Microsoft Structured Query Language (SQL) Server are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)

[15]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500.

[16]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 or its successor to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 or 140-3 compliant full disk encryption (FOE) must be implemented on the storage device where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). By September 22, 2026, all FIPS 140-2 certificate validations will be placed on the Historical List, please refer to FIPS Transition Effort for further guidance and timeline of changes.

[17]	Projects must ensure that adequate technical support services are available to sustain the implementation on the project`s platform due to the expansive capabilities of the product. Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM. Users must not utilize International Business Machines (IBM) Case Foundation, as it is at the time of writing, unapproved in the TRM. This technology must use the latest TRM-approved version of Java Runtime Environment (JRE) - Oracle. This technology must use the latest TRM-approved version of Java Development Kit (JDK) - Oracle. Users must ensure that Microsoft Edge, Google Chrome, Firefox, Oracle Database, and Microsoft Structured Query Language (SQL) Server are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)

[18]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request, visit the Product Marketplace. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

Note:

At the time of writing, version 5.5.12 is the most current version, released 01/25/2024.

References

The following reference(s) are associated with this entry:
Type	Name	Source	Description
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

Technology Components

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.
Name	Description
Content Management Interoperability Services (CMIS)	Content Management Interoperability Services (CMIS) is an open standard that allows different content management systems to inter-operate over the Internet. Specifically, CMIS defines an abstraction layer for controlling diverse document management systems and repositories that use web protocols.
Content Platform Engine (CPE)	Content Platform Engine (CPE) manage enterprise-wide workflow objects, custom objects, and documents by offering powerful and easy-to-use administration tools. Using these tools, an administrator can create and manage the classes, properties, storage, and metadata that form the foundation of an enterprise content management (ECM) system. Marking records that have passed the retention period (Sweep) and their automatic destruction is performed by CPE.
Content Search Services (CSS)	Content Search Services (CSS) consists of index and search servers that are created and registered at the FileNet P8 domain level. The Content Platform Engine’s text search dispatcher passes index and search requests to Content Search Services servers.
International Business Machines (IBM) Content Collector (ICC)	International Business Machines (IBM) Content Collector consists of several components, which interact with components of Microsoft Exchange, Lotus Domino, New Technology File System (NTFS), distributed file system (DFS), and Novell file systems, Microsoft SharePoint and IBM Connections environments, and Content Platform Engine object stores.
International Business Machines (IBM) Content Navigator (ICN)	International Business Machines (IBM) Content Navigator (ICN) is a web client that provides users with a console for working with content from multiple content servers. Content Navigator also enables users to create custom views of the content on the web client by creating team spaces, which provide a focused view of the relevant documents, folders, and searches that a team needs to complete their tasks. Content Navigator also includes API toolkit that you can use to extend the web client and build custom applications.
International Business Machines (IBM) Enterprise Records (IER)	International Business Machines (IBM) Enterprise Records is used to create and maintain records for both electronic and physical information, regardless of the storage media or format.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Application Technology Development Tools	Process Management Tools
Collaboration and Electronic Workplace Collaboration Software	Content Management

Operating Systems Supported by the Technology

Red Hat Enterprise Linux (RHEL) - Approved w/Constraints
Windows Client - Approved w/Constraints
Windows Server - Approved w/Constraints

Technologies/Standards Relationships

Runtime Dependencies:

Db2 - (required for some configurations)
Hasura Graph Query Language (GraphQL)
International Business Machines (IBM) Semeru Runtime - (required for some configurations)
Java Runtime Environment (JRE) - International Business Machines (IBM)
Java Runtime Environment (JRE) - Oracle
JBoss Enterprise Application Platform (EAP)
JDK - Oracle Java Standard Edition (SE) Development Kit
Microsoft .NET Framework
Microsoft Edge. - (required for some configurations)
Microsoft Structured Query Language (SQL) Server - (required for some configurations)
Oracle Database - (required for some configurations)
Visual C++ Redistributable Package
WebLogic Server
Websphere Application Server (WAS)
WildFly

Comparable Technologies:

No comparable entries have been identified.

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

This technology may improve productivity for specific staff whose responsibilities include enterprise content management.
This technology can gather both content and process into a single repository. This base of content and process then becomes the foundation for other applications and uses, such as case management, forms management, or records management.
This technology supports role-based authorization and authentication (A&A) capabilities.
The vendor of this technology is an industry leader in the subject matter.
This is a well-documented technology.
At the time of writing, this technology provides functionality not available through other approved TRM options.
This technology is Federal Information Processing Standard (FIPS) Publication 140-2 Certified and Advanced Encryption Standard (AES) 128-bit encrypted.

Adoption Risks

This technology relies on Java Runtime Environment (JRE) - Oracle, which has a rapid release and update schedule.
This technology can potentially use Secure Sockets Layer (SSL), an unapproved protocol.
The technology requires the purchase of licenses from vendor, which could potentially lead to vendor lock-in.
This technology can potentially use International Business Machines (IBM) Case Foundation, an unapproved technology.
This technology relies on Java Development Kit (JDK) - Oracle, which has a rapid release and update schedule.
Due to the rapid release schedule of this technology, the VA may be unable to update to the most recent patch and may require a deployment model requiring the use of specific versions.
This technology can integrate with and alter database technologies.
The potential exists to store Personally Identifiable Information (PII), Protected Health Information (PHI) and/or VA Sensitive data and proper security standards must be followed in these cases.
There are known Common Vulnerabilities and Exposures (CVEs) associated with this technology. Please see https://nvd.nist.gov/vuln/search for more details.

Architectural Benefits

This technology is portable across several VA approved platforms.
This technology`s architecture provides interoperability across standard organization applications, file stores, and data repositories.
This technology can be extended through the use of other Technical Reference Model (TRM) approved technologies for additional functionality.
This technology can use a VA-preferred database.
This technology supports AES Encryption.

Architectural Risks

This technology includes cloud-based functionality which has potential information security risks.

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (05/09/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (05/09/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES