Security considerations for the Rational solution for Collaborative Lifecycle Management
- Enabling secure communication between multiple applications
- Enabling security during installation
- Auditing the security infrastructure
- Ports, protocols, and services
- Customizing security settings
- Setting up user roles and access
- Privacy policy considerations
- Deleting sensitive data
- Restricting read access to certain files with sensitive information
- Non-admin users can view some server configuration parameters
- Security limitations
- Users are not logged out after the LTPA timeout period is reached
- Sensitive information in work item links
Enabling secure communication between multiple applications
Enabling security during installation
Several WebSphere Application Server security settings, such as administrative security, application security, and securing cookies must be enabled before deploying CLM applications. For more information, see Setting up WebSphere Application Server.
To be compliant with U.S. government Special Publications SP800-131 standards that is used to accredit cryptographic modules, you must configure your servers, clients, and browsers. For detailed information, see Support for National Institute of Standards and Technology (NIST) Special Publication (SP) 800-131.
Auditing the security infrastructure
You can use the Auditing Facility to report and track auditable events to ensure the integrity of your system in a WebSphere Application Server environment. For more information, see the WebSphere Application Server documentation.
Ports, protocols, and services
Customizing security settings
Setting up user roles and access
To understand the authentication mechanism that Jazz Team Server uses, see this Jazz.net article: TN0013: Jazz Team Server Authentication Explained
Privacy policy considerations
Depending on the configurations that are deployed, this software offering might use cookies that can help enable you to collect personally identifiable information. For information about this offering’s use of cookies see the Notices topic.
To secure LTPA cookies, you can enable the Requires SSL setting in the WebSphere Application Server Console. For more information, see Setting up WebSphere Application Server
- user name
- email address
- picture
By design, CLM does not process any special categories of personal data (data revealing health, racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, biometrics, sexual orientation, etc.).
Deleting sensitive data
You can remove sensitive data from applications. Scrub these items to recover from data spills and to remove information that is now confidential but wasn't before, or to delete information that should not be revealed to a wider audience. Information is permanently deleted from the application and cannot be recovered.
You might have data from one or more of these applications:
- Lifecycle Query Engine and the Link Index Provider (LQE and LDX): Removing sensitive data from LQE and LDX.
- Requirements Management (RM): Deleting artifacts from the RM repository.
- Change and Configuration Management (CCM): Deleting work items in the web client and Deleting work items in the Eclipse client.
- Quality Management (QM): Permanently deleting sensitive QM data and Deleting test artifacts.
- Design Management (DM): Finding and resolving data spills.
- Global Configuration Management (GCM): Finding sensitive data and data spills in global configurations and components and Deleting sensitive data from global configurations and components.
Restricting read access to certain files with sensitive information
There are certain files or directories in Report Builder, Data Collection Component and other CLM applications that contain sensitive information. These files or directories should have their read access restricted to the user or admin that is going to start up the CLM server. The files and directories containing sensitive information are:
Report Builder
- \server\conf\rs\db directory
- \server\conf\rs\app.properties
Data Collection Component and other CLM applications
- \server\conf\dcc\teamserver.properties and all its backup versions
- \server\conf\dcc\indices\ [index_name], for example \server\conf\dcc\indices\yNb0YZoVEeaftY0i9ahkQg
Non-admin users can view some server configuration parameters
It is possible for a user without administrative privileges to view some server configuration parameters from the web UI. However, a non-admin user cannot modify any of these configuration parameters. If this is a security concern for your organization, complete the following steps to enable the enhanced admin security:
- Go to the Jazz_Install_Dir/server directory and open server.startup for editing.
- Add the following line to the JAVA_OPTS
section:
Linux
JAVA_OPTS="$JAVA_OPTS -Dnet.jazz.ajax.disableEnhancedAdminSecurity=false"Windows
set JAVA_OPTS=%JAVA_OPTS% -Dnet.jazz.ajax.disableEnhancedAdminSecurity="false" - Save and close the server.startup file.
- Restart the server for changes to take effect.
- Log into the WebSphere Application Server Integrated Solutions Console.
- Click .
- Under Server Infrastructure, click .
- Under Additional Properties, click and then click Custom properties.
- Click New and add the following custom property:
- Name: net.jazz.ajax.disableEnhancedAdminSecurity
- Value: false
- Click OK, and then Save directly to the master configuration.
- Restart the server for changes to take effect.
Security limitations
- Default passwords
By default, when creating a user, generated passwords are the same as user IDs. For security reasons, it is recommended to change the default password and use a strong password policy.
- Unsuccessful log in attempts
The default application server for the Rational solution for CLM products is WebSphere Liberty, which does not lock out users after multiple unsuccessful attempts to log in. Many external LDAP directories offer this functionality. You can set up an external directory to use with WebSphere Liberty.
- Installing with Security-Enhanced Linux
If Security-Enhanced Linux (SELinux) is enabled, you must either disable it or change the security context of the Java™™ Runtime Environments (JREs) that are used for installing and running the server to allow text relocation. For more information, see Installing with Security-Enhanced Linux.
Users are not logged out after the LTPA timeout period is reached
When the IBM Lightweight Third Party Authentication (LTPA) timeout value is set in IBM WebSphere Application Server, the Jazz Team Server for the Requirements Management application does not log out users after the timeout period is reached. This is due to the fact that the LTPA timeout setting in WebSphere Application Server and OAuth access token timeout in Jazz Team Server do not have the same value. For more information about setting these two values, see this technote.
Sensitive information in work item links
The work item summary is displayed as a link when work items are shared between private and public project areas. A user from the public project area might not have access to the work item in the private project area by clicking the link, but the summary of the private work item is displayed and viewable by all users. The best practice is not to include any sensitive information in the work item summary.
|
Jazz.net channel User Education channel |
Agile learning circle Learning circles |
developerWorks forums |
Deployment wiki Support blog |
