Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.7

Alvaria Prophecy

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:	The Alvaria Prophecy software is a standards-based communications technology for speech, Interactive Voice Response (IVR), Voice Response Units (VRU), and Session Initiation Protocol (SIP) Voice-over-Internet Protocol (VoIP) applications. This technology is built natively on VoIP and integrates into contact centers built on Internet Protocol communications to create applications to interact with humans through voice and Dual Tone Multi-Frequency (DTMF) tones input via a phone keypad. Alvaria Prophecy supports both inbound and outbound IVR applications, has built-in conferencing and call recording capabilities, and has a full-features Application Program Interface (API). This technology can utilize a Microsoft Structured Query Language (SQL) Server, Oracle, H2 or PostgreSQL database. Note: This technology was rebranded from Aspect Prophecy to Alvaria Prophecy following the vendor rebrand to Alvaria, Inc in May 2021. 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 v22.10
Decision Date:	10/18/2022 at 16:18:08 UTC
Aliases:	Voxeo Prophecy, Aspect Prophecy, Automated Agent
Introduced By:	TRM Request
Vendor Name:	Alvaria

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
14	08/25/2014	05/30/2017	05/30/2019
14.5	12/01/2015
16.x.x	05/06/2016
18.x	06/15/2018
19.x	12/03/2019
20.x	07/14/2020
22.x	06/24/2022

Current Decision Matrix (10/12/2022)

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

CY2023

CY2024

CY2025

Future>

Release

Unapproved

14.5

Unapproved

16.x.x

Unapproved

18.x

Unapproved

19.x

Divest
[4, 16, 18, 20, 22, 23, 24]

Divest
[4, 16, 18, 20, 23, 24, 25]

Unapproved

20.x

Divest
[4, 16, 18, 20, 22, 23, 24]

Divest
[4, 16, 18, 20, 23, 24, 25]

Divest
[4, 16, 20, 23, 25, 26, 27]

Unapproved

22.x

Approved w/Constraints
[4, 16, 18, 20, 22, 23, 24]

Approved w/Constraints
[4, 16, 18, 20, 23, 24, 25]

Approved w/Constraints
[4, 16, 20, 23, 25, 26, 27]

Decision Constraints


[1]	Veterans Affairs (VA) users must ensure VA sensitive data is protected properly in accordance with VA Handbook 6500 and the Federal Information Security Management Act (FISMA). Per VA Handbook 6500, Federal Information Processing Standards (FIPS) 140-2 certified encryption must be used to protect and encrypt data in transit and at rest if Personally Identifiable Information/Protected Health Information/VA (PII/PHI/VA) sensitive information is involved. If FIPS 140-2 certified encryption is not used, additional mitigating controls must be documented in an approved System Security Plan (SSP). In addition, the technology must be implemented within the VA production network (not in a Demilitarized Zone (DMZ)), unless the specific uses and instances of the technology are approved by the Enterprise Security Change Control Board (ESCCB). All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. In cases where the technology is used for external connections, a full ESCCB review is required in accordance VA Directive 6004, VA Directive 6517 and VA Directive 6513. Cloud versions of this product are not permitted without a waiver from the Architecture and Engineering Review Board (AERB) and expressed authorization. Product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines.

[2]	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.

[3]	Due to potential information security risks, cloud based versions of this product are not permitted without a waiver signed by the Deputy CIO of ASD based upon a recommendation from the Architecture and Engineering Review Board (AERB). In addition, cloud based features of this software may not be used without an Enterprise Security Change Control Board (ESCCB) approval to ensure that confidential organization and/or PII/PHI data are not compromised (ref: VA Directive 6004, VA Directive 6517 and VA Directive 6513). Use of public cloud storage requires documented Federal Risk and Authorization Management Program (FedRAMP) compliance and a Memorandum of Understanding / Interconnection Security Agreement (MOU/ISA) between the vendor and VA prior to ESCCB review.

[4]	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.

[5]	This technology is downloaded with and can interact with H2 Database, which is an unapproved technology. Users must disable and remove H2 Database and use an approved database technology like Microsoft Structured Query Language (SQL) Server. VA requires Federal Information Processing Standards (FIPS) 140-2 compliant cryptographic modules for encryption of data at rest and in transit. Ensure underlying infrastructure and application access are configured to provide FIPS 140-2 encryption for web access supporting Aspect Prophecy. The H2 database is used by Prophecy internally, with no user access. Adherence to VA guidelines on approved web browsers when using this product is required. If there is a business need for alternative browsers, such as Mozilla Firefox, or nonstandard versions of Internet Explorer or Google Chrome a STAT waiver must be granted to the project team or organization that wishes to use the alternative browser. It is advised that a custom usage policy be created at the Aspect Prophecy entry point and users required to accept it before they are allowed to access the site. It should be stated explicitly that discussing and posting of VA sensitive information is prohibited. If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

[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]	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]	This technology is downloaded with and can interact with H2 Database, which is an unapproved technology. Users must disable and remove H2 Database and use an approved database technology like Microsoft Structured Query Language (SQL) Server. VA requires Federal Information Processing Standards (FIPS) 140-2 compliant cryptographic modules for encryption of data at rest and in transit. Ensure underlying infrastructure and application access are configured to provide FIPS 140-2 encryption for web access supporting Aspect Prophecy. The H2 database is used by Prophecy internally, with no user access. Adherence to VA guidelines on approved web browsers when using this product is required. If there is a business need for alternative browsers, such as Mozilla Firefox, or nonstandard versions of Internet Explorer or Google Chrome a STAT waiver must be granted to the project team or organization that wishes to use the alternative browser. It is advised that a custom usage policy be created at the Aspect Prophecy entry point and users required to accept it before they are allowed to access the site. It should be stated explicitly that discussing and posting of VA sensitive information is prohibited. If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

[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]	This technology is downloaded with and can interact with H2 Database, which is an unapproved technology. Users must disable and remove H2 Database and use an approved database technology like Microsoft Structured Query Language (SQL) Server. VA requires Federal Information Processing Standards (FIPS) 140-2 compliant cryptographic modules for encryption of data at rest and in transit. Ensure underlying infrastructure and application access are configured to provide FIPS 140-2 encryption for web access supporting Aspect Prophecy. The H2 database is used by Prophecy internally, with no user access. Adherence to VA guidelines on approved web browsers when using this product is required. If there is a business need for alternative browsers, such as Mozilla Firefox, or nonstandard versions of Internet Explorer or Google Chrome a STAT waiver must be granted to the project team or organization that wishes to use the alternative browser. It is advised that a custom usage policy be created at the Aspect Prophecy entry point and users required to accept it before they are allowed to access the site. It should be stated explicitly that discussing and posting of VA sensitive information is prohibited. If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users must ensure that Microsoft Structured Query Language (SQL) Server is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) This technology must use the latest version of Java Development Kit (JDK) - Oracle.

[11]	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 with the Project Special Forces (SPF) team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[12]	This technology is downloaded with and can interact with H2 Database, which is an unapproved technology. Users must disable and remove H2 Database and use an approved database technology like Microsoft Structured Query Language (SQL) Server. VA requires Federal Information Processing Standards (FIPS) 140-2 compliant cryptographic modules for encryption of data at rest and in transit. Ensure underlying infrastructure and application access are configured to provide FIPS 140-2 encryption for web access supporting Aspect Prophecy. The H2 database is used by Prophecy internally, with no user access. Adherence to VA guidelines on approved web browsers when using this product is required. If there is a business need for alternative browsers, such as Mozilla Firefox, or nonstandard versions of Internet Explorer or Google Chrome a STAT waiver must be granted to the project team or organization that wishes to use the alternative browser. It is advised that a custom usage policy be created at the Aspect Prophecy entry point and users required to accept it before they are allowed to access the site. It should be stated explicitly that discussing and posting of VA sensitive information is prohibited. If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users must ensure that Microsoft Structured Query Language (SQL) Server, PostgreSQL, and Oracle Database are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) This technology must use the latest version of Java Development Kit (JDK) - Oracle.

[13]	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.

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

[15]	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 with the Project Special Forces (SPF) team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[16]	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. If PostgreSQL is selected for use with this product, these factors must be considered especially when an instance of this product will be considered a Moderate or High-Risk system. See PostgreSQL Database TRM entry for more details.

[17]	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 with the Project Special Forces (PSF) team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[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 with the VA OIT Product Engineering team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[19]	This technology is downloaded with and can interact with H2 Database, which is an unapproved technology. Users must disable and remove H2 Database and use an approved database technology like Microsoft Structured Query Language (SQL) Server. VA requires Federal Information Processing Standards (FIPS) 140-2 compliant cryptographic modules for encryption of data at rest and in transit. Ensure underlying infrastructure and application access are configured to provide FIPS 140-2 encryption for web access supporting Aspect Prophecy. The H2 database is used by Prophecy internally, with no user access. Adherence to VA guidelines on approved web browsers when using this product is required. If there is a business need for alternative browsers, such as Mozilla Firefox, or nonstandard versions of Internet Explorer or Google Chrome a STAT waiver must be granted to the project team or organization that wishes to use the alternative browser. It is advised that a custom usage policy be created at the Aspect Prophecy entry point and users required to accept it before they are allowed to access the site. It should be stated explicitly that discussing and posting of VA sensitive information is prohibited. If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users must ensure that Microsoft Structured Query Language (SQL) Server, PostgreSQL, and Oracle Database are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) This technology must use the latest TRM-approved version of Java Development Kit (JDK) - Oracle.

[20]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users must ensure that Microsoft Structured Query Language (SQL) Server, PostgreSQL, and Oracle Database are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) Users must not utilize the H2 Database Engine, as it is unapproved for use on the TRM. This technology must use the latest TRM-approved version of Java Development Kit (JDK) - Oracle. Per the Initial Product Review, users must abide by the following constraints: VA requires Federal Information Processing Standards (FIPS) 140-2 certified cryptographic modules for encryption of data at rest and in transit. Ensure underlying infrastructure and application access are configured to provide FIPS 140-2 certified encryption for web access supporting Aspect Prophecy. The H2 database is used by Prophecy internally, with no user access. It is advised that a custom usage policy be created at the Aspect Prophecy entry point and users required to accept it before they can access the site. It should be stated explicitly that discussing and posting of VA sensitive information is prohibited. System owners should review the One-VA TRM entries for the approved versions of databases and Oracle Java SDK. Due to potential information security risks, SaaS/PaaS solutions must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Project Special Forces (PSF), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS/Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by PSF.

[21]	Users should check with their supervisor, Information Security Office (ISO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not approved and the user should take the proper steps to decline those installations.

[22]	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.

[23]	Users should check with their supervisor, Information System Security Officer (ISSO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not approved and the user should take the proper steps to decline those installations.

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

[25]	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.

[26]	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.

[27]	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 22.1 is the most current version.

The following reference(s) are associated with this entry:
Type	Name	Source	Description
Vendor Provided*	Document Portal		This area contains information to get started using the Automated Agent technology.
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

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
ASR	The ASR component converts caller speech into text for computer processing.
Call Control Extensible Markup Language (CCXML) Browser	The CCXML Browser is responsible for requesting, interpreting and rendering CCXML documents.
Database	The Database component assists with rovisioning database for server and application data, and Prophecy logging.
Hypertext Transfer Protocol (HTTP) Application Server	The HTTP Application Server provides business logic for applications.
Media Resource Control Protocol (MRCP) Server	The MRCP Server is used to provide Automatic Speech Recognition (ASR) and Text-to-Speech (TTS).
Media Server	The Media Server is responsible for requesting, processing, and rendering of media content such as audio .wav files.
Prophecy Commander	This component provides a graphical user interface for controlling your Prophecy deployment.
Session Initiation Protocol (SIP) Application Server	The SIP Application Server provides call control, such as routing, transfer, and call progress analysis.
Telephony Browser	The Telephony Browser connects to the telephone network via SIP or VOIP.
TTS	This component provides digitized audio rendering.
Voice Extensible Markup Language (VoiceXML)	The VoiceXML browser is responsible for requesting, interpreting and rendering VoiceXML documents.


Collaboration and Electronic Workplace Collaboration Software	Unified Messaging

- The information contained on this page is accurate as of the Decision Date (10/18/2022 at 16:18:08 UTC).

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

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

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