Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.11

PageGate

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:	PageGate allows for network messaging or network wide Short Message Service (SMS) messaging through a combination of the following methods: email, webpage, command line, text file, Internet, serial port, modem, mobile phone, wireless modem, direct database access and windows client. This entry covers the Desktop Edition of this technology and not any mobile versions. Please note that the implementation of mobile technology applications that operate on Mobile Operating Systems must be reviewed and authorized by the Mobile Technology and Endpoint Security Engineering Team: http://vaww.eie.va.gov/SysDesign/CS/MT/default.aspx
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 been assessed by the Section 508 Office and found non-conformant. 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. Please see reference tab for more information concerning product versions.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v23.5
Decision Date:	05/03/2023 at 03:31:11 UTC
Introduced By:	TRM Request
Vendor Name:	NotePage, Inc.

Vendor Release Information

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

You must be logged into the RSAA website prior to clicking the Attestation URLs or the URLs won't open.

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
5.x
6.x
7.x	06/02/2014
8.x	06/14/2017
9.x
10.x	03/15/2023

Current Decision Matrix (04/14/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 VAIT 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.

Legend:

White	Authorized: The technology/standard has been authorized for use.
Yellow	Authorized 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	Authorized w/ Constraints (POA&M): 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	Authorized w/ Constraints (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 unauthorized may be found on the Decision tab for the specific entry.
Black	Unauthorized: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Authorized w/ Constraints (PLANNING/EVALUATION): 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 authorized 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 authorized 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.

Any major.minor version that is not listed in the VA Decision Matrix is considered Authorized w/ Constraints (POA&M).

<Past

CY2019

CY2020

CY2021

Future>

Release

5.x

Unapproved

6.x

Unapproved

7.x

Unapproved

8.x

Approved w/Constraints
[3, 6, 7, 8, 10]

Approved w/Constraints
[3, 6, 7, 11]

Approved w/Constraints
[3, 6, 7, 12]

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

DIVEST
[3, 13, 14, 15]

9.x

Unapproved

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

10.x

Unapproved

Decision Constraints


[1]	Vendor offers a 30-day free trial period of PageGate. If it is utilized, the software must be purchased or removed at the end of the trial period. Product is used primarily to send texts to mobile equipment. Users must avoid transmitting Personal Identification Information (PII)/Personal Health Information (PHI) or VA sensitive information.

[2]	In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process.

[3]	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 authorized and the user should take the proper steps to decline those installations.

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

[5]	Security Engineering (SE) conducted a pre-assessment and security requirements verification of PageGate. It is advised that if this product is used within the Department of Veterans Affairs (VA) that the following constraints be applied: 1. Ensure to leverage use of a FIPS 140-2 validated cryptographic module to secure VA sensitive data in applications, workstations and devices that utilize PageGate. 2. In addition to the use of FIPS 140-2 encryption, users should have adequate and periodic Security Awareness Training (AT) to prevent sending of PII/PHI or VA sensitive information in plain text messages. 3. At the end of free trial, PageGate should be removed or a full software license purchased to mitigate unwanted application and threat vector on the VA network. 4. When establishing Admin credentials for PageGate, ensure that all VA password requirements are met with regard to length and complexity. VA Handbook 6500 Control IA-5: Authenticator Management sets a standard of at least 8 non-blank characters. They must contain characters from three (3) of the following four (4) categories: o English upper case characters o English lower case characters o Base-10 digits o Non-alphanumeric special characters Six of the characters must not occur more than once in the password. Product is used primarily to send texts to mobile equipment. Users must avoid transmitting Personal Identification Information (PII)/Personal Health Information (PHI) or VA sensitive information.

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

[9]	In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process.

[10]	According to the Initial Product Review, users must abide by the following constraints: Ensure to leverage use of a FIPS 140-2 validated cryptographic module to secure VA sensitive data in applications, workstations and devices that utilize PageGate. In addition to the use of FIPS 140-2 encryption, users must have adequate and periodic Security Awareness Training (AT) to prevent sending of PII/PHI or VA sensitive information in plain text messages. When establishing Admin credentials for PageGate, ensure that all VA password requirements are met with regard to length and complexity. VA Handbook 6500 Control IA-5: Authenticator Management sets a standard of at least 8 non-blank characters. They must contain characters from three (3) of the following four (4) categories: o English upper case characters o English lower case characters o Base-10 digits o Non-alphanumeric special characters In accordance with National Institute of Standards and Technology (NIST) SP 800-53 and SP 800-70, Information Security is an important business process that must be considered in all phases of the acquisition process to ensure data and information technology (IT) systems are adequately protected against risk of loss, misuse, and unauthorized access. In accordance with FISMA, government information or government IT systems require compliance with the agency IT Security Policy. All information technology acquisitions must meet the requirements outlined in the Federal Acquisition Regulation (FAR) Part 39.101 (d) policy ensuring the use of common security configuration checklists in the management of risk.

[11]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. According to the Initial Product Review, users must abide by the following constraints: Ensure to leverage use of a FIPS 140-2 validated cryptographic module to secure VA sensitive data in applications, workstations and devices that utilize PageGate. In addition to the use of FIPS 140-2 encryption, users must have adequate and periodic Security Awareness Training (AT) to prevent sending of PII/PHI or VA sensitive information in plain text messages. When establishing Admin credentials for PageGate, ensure that all VA password requirements are met with regard to length and complexity. VA Handbook 6500 Control IA-5: Authenticator Management sets a standard of at least 8 non-blank characters. They must contain characters from three (3) of the following four (4) categories: o English upper case characters o English lower case characters o Base-10 digits o Non-alphanumeric special characters In accordance with National Institute of Standards and Technology (NIST) SP 800-53 and SP 800-70, Information Security is an important business process that must be considered in all phases of the acquisition process to ensure data and information technology (IT) systems are adequately protected against risk of loss, misuse, and unauthorized access. In accordance with FISMA, government information or government IT systems require compliance with the agency IT Security Policy. All information technology acquisitions must meet the requirements outlined in the Federal Acquisition Regulation (FAR) Part 39.101 (d) policy ensuring the use of common security configuration checklists in the management of risk.

[12]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. According to the Initial Product Review, users must abide by the following constraints: Ensure to leverage use of a FIPS 140-2 validated cryptographic module to secure VA sensitive data in applications, workstations and devices that utilize PageGate. In addition to the use of FIPS 140-2 encryption, users must have adequate and periodic Security Awareness Training (AT) to prevent sending of PII/PHI or VA sensitive information in plain text messages. When establishing Admin credentials for PageGate, ensure that all VA password requirements are met with regard to length and complexity. VA Handbook 6500 Control IA-5: Authenticator Management sets a standard of at least 8 non-blank characters. They must contain characters from three (3) of the following four (4) categories: o English upper case characters o English lower case characters o Base-10 digits o Non-alphanumeric special characters

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

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

[15]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. According to the Initial Product Review, users must abide by the following constraints: Ensure to leverage use of a FIPS 140-2 validated cryptographic module to secure VA sensitive data in applications, workstations and devices that utilize PageGate. In addition to the use of FIPS 140-2 encryption, users must have adequate and periodic Security Awareness Training (AT) to prevent sending of PII/PHI or VA sensitive information in plain text messages. When establishing Admin credentials for PageGate, ensure that all VA password requirements are met with regard to length and complexity. VA Handbook 6500 Control IA-5: Authenticator Management sets a standard of at least 8 non-blank characters. They must contain characters from three (3) of the following four (4) categories: o English upper case characters o English lower case characters o Base-10 digits o Non-alphanumeric special characters

Note:

At the time of writing, version 10.0.10 is the most current version, released 03/15/2023.

Type	Name	Description
Vendor Provided*	Manuals & Documentation	This links to the Server and Client Manuals for PageGate.
Vendor Provided*	Steps to Write Directly to PageGate Database	This links to the steps required to write directly to the PageGate Database.
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

Name	Description
No components have been identified for this entry.


Application Technology Integration Software	Messaging Oriented Middleware (MOM)
Collaboration and Electronic Workplace Collaboration Software	Electronic Messaging

General Analysis

Adoption Benefits

This technology has a comprehensive set of documentation.
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.

Adoption Risks

This technology has a free trial period, which carries the potential for the disruption of service delivery and inaccurate financial planning.
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.
PageGate is not Federal Information Processing Standards (FIPS) 140-2 certified.
PageGate Admin credential is required to be set up.
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 potentially use Secure Sockets Layer (SSL), an unapproved protocol.
This technology can connect to a database.
PageGate can be used to send any type of text messages (potentially PII/PHI or VA sensitive information).
PageGate uses the Microsoft Jet database by default, which is not authorized for use within the Department of VA.
PageGate is offered as a free trial that expires in 30 days.
PageGate Admin credentials are required to be set up.
The technology requires the purchase of licenses from vendor, which could potentially lead to vendor lock-in.
This technology can integrate with and alter database technologies.

Architectural Benefits

This technology can use a VA-preferred database.

Architectural Risks

This product supports a very limited number of platforms (Windows only).

- The information contained on this page is accurate as of the Decision Date (05/03/2023 at 03:31:11 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.11

General Information

Vendor Release Information

Current Decision Matrix (04/14/2023)

Decision Constraints

References

Technology Components

VA Categories

View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional 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.11

General Information

Vendor Release Information

Current Decision Matrix (04/14/2023)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES

VA Categories

View the VA Categorization Framework