Rally Software

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:	Rally Software, formerly CA Agile Central, is a project management utility for agile and lean processes. This technology provides a framework to scale and mature agile practices in a step-wise fashion. For an on-premises installation, Rally Software is installed on a server within the organization`s Information Technology (IT) infrastructure. Rally Software uses VMware software to create a self-contained environment that includes its own virtual hardware, operating system, application servers, application software, and proprietary database management system. Once installed, Rally Software is accessible through the local intranet or virtual private network (VPN). This product is also available as Software as a Service (SaaS). Rally Software is available in three editions: Community Edition, Enterprise Edition, and Unlimited Edition. Each edition is fundamentally similar, with the Unlimited Edition including additional features and modules that are unavailable in the Community and Enterprise editions. The scope of this entry is limited to all editions of an on-premise installation. 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 v23.12
Decision Date:	12/14/2023 at 13:36:53 UTC
Aliases:	CA Rally; Rally; Rally On-Premises; CA Agile Central
Introduced By:	TRM Request
Vendor Name:	CA Technologies

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	Vendor Desupport Date
13.3	08/21/2014
2016.x	02/18/2016
2017.x	09/25/2017
2018.x	02/22/2018
2019.x	01/31/2019
2020.x
2023.x

Current Decision Matrix (12/12/2023)

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

CY2017

CY2018

CY2019

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

13.3

Approved w/Constraints
[1]

Approved w/Constraints
[1, 2, 3, 4]

Approved w/Constraints
[1, 2, 5, 6]

Approved w/Constraints
[1, 2, 6, 7]

Approved w/Constraints
[2, 6, 7, 8]

Divest
[2, 6, 7, 8]

2016.x

Unapproved

Approved w/Constraints
[1, 2, 3, 4]

Approved w/Constraints
[1, 2, 5, 6]

Approved w/Constraints
[1, 2, 6, 7]

Approved w/Constraints
[2, 6, 7, 8]

Divest
[2, 6, 7, 8]

2017.x

Unapproved

Approved w/Constraints
[1, 2, 3, 4]

Approved w/Constraints
[1, 2, 5, 6]

Approved w/Constraints
[1, 2, 6, 7]

Approved w/Constraints
[2, 6, 7, 8]

Divest
[2, 6, 7, 8]

2018.x

Unapproved

Approved w/Constraints
[2, 6, 7, 8]

2019.x

Unapproved

Approved w/Constraints
[2, 6, 7, 8]

2020.x

Unapproved

2023.x

Unapproved

Decision Constraints


[1]	This product is no longer approved for information technology (IT) projects that are or will be mandated to follow standardized processes and tools governing IT activity critical to VA`s implementation of the Veteran-focused Integration Process (VIP).

[2]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

[3]	Due to potential information security risks, cloud based technologies may not be used without an Enterprise Security Change Control Board (ESCCB) approval. This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[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]	Due to potential information security risks, cloud based technologies may not be used without the approval of the VA Enterprise Cloud Services (ECS) Group. This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[6]	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).

[7]	Due to potential information security risks, cloud based technologies may not be used without the approval of the Enterprise Cloud Solution Office (ECSO). This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[8]	Technology must remain patched and operated in accordance with Federal and Department security policies and guidelines in order to mitigate known and future security vulnerabilities.

Note:

At the time of writing, version 2023 Q4 is the most current version.

The versioning schema of this technology changed with the release of version 2023.

References

The following reference(s) are associated with this entry:
Type	Name	Source	Description

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
Advanced Security and Administration	This module is used to authenticate with existing Single Sign-On (SSO) systems, limit access to CA Agile Central through Internet Protocol (IP) ranges, and restrict attachment types. This module is included with an Unlimited Edition subscription.
Idea Manager	This module provides one or more websites that may be used to gather customer feedback. End users may access a website to submit and vote on new ideas. Proposed new ideas and features may be converted to CA Agile Central user stories. This module is included with an Unlimited Edition subscription.
Portfolio Manager	This module enables users to connect long term strategy with development execution by providing an additional planning layer with executive reporting utilities. This module is included with an Unlimited Edition subscription.
Quality Manager	This module provides users with a way to create independent test cases that are not associated to user stories or defects. Users may also organize and schedule groups of test cases with this module. This module is included with an Unlimited Edition subscription.
Support Manager	This module connects the Salesforce.com environment with user stories and defects in CA Agile Central. Users may connect Salesforce support cases to CA Agile Central defects, for example, to track how many customers have reported a specific issue. This module is included with an Unlimited Edition subscription. Note: As of September 30, 2017, the vendor is no longer updating or providing technical support for this module.
Time Tracker	CA Agile Central Time Tracker provides timesheet functionality for accounting purposes. Employees and contractors may enter billable hours against assigned user stories, defects, and tasks. This module is included with an Unlimited Edition subscription.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Application Technology Development Tools	Software Change and Configuration Management Tools

Operating Systems Supported by the Technology

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

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

This vendor is a Federal Risk and Authorization Management Program (FedRAMP) authorized vendor.
At the time of writing, no National Institute of Standards and Technology (NIST) vulnerabilities had been reported and no VA Cyber Security Operations Center (CSOC) bulletins had been issued for the latest versions of this technology.
This product supports role-based authentication and authorization capabilities.
This is a well-documented technology.

Adoption Risks

This product can be configured with a PostgreSQL Database, which currently has TRM constraints limiting its use to Red Hat Enterprise Linux (RHEL) only due to its many known security issues on other platforms.
This technology may utilize external data connections.
This technology can potentially use Secure Sockets Layer (SSL), an unapproved protocol.
Although this technology uses 256-bit Advanced Encryption Standard (AES) algorithms for encryption, there is no indication based on the Cryptographic Module Validation Program (CMVP) that it is Federal Information Processing Standards (FIPS) 140-2 certified.
Due to the rapid release schedule of this product, VA may be unable to update to the most recent patch and may require a deployment model requiring the use of specific versions.
System scans indicate that this technology is no longer in use within the VA network.
This technology can integrate with and alter database technologies.
This software has a free trial period, which carries the potential for the disruption of service delivery and inaccurate financial planning.

Architectural Benefits

This technology is portable as it runs on multiple TRM-approved platforms.
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 (12/12/2023)

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 (12/12/2023)

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