Pitney Bowes DeviceHub

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:	This technology operates on an independent device to allow optimal service, upkeep, and performance of networked printers on a VA network. Administrators would be able to set up a cloud printing service that would direct printer traffic to the appropriate printer based on location, volume, or other factors. Note: This assessment covers only the software component of this system. No hardware is evaluated or approved by the TRM. 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.2
Decision Date:	02/16/2024 at 17:19:45 UTC
Introduced By:	TRM Request
Vendor Name:	Pitney Bowes

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
1.x	05/15/2020

Current Decision Matrix (02/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

CY2024

CY2025

CY2026

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

1.x

Approved w/Constraints
[3, 5, 7, 8, 9, 10, 11, 12]

Decision Constraints


[1]	Users must ensure that Microsoft .NET Framework and VMWare vSphere are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) This technology requires using a Universal Service Bus (USB) technology to transfer data into the records. As such, proper precautions need to be taken to protect data. Per the Security Assessment Review, users must abide by the following constraints: Pitney Bowes DeviceHub version 1.9.X default installs off the root of c:\. To mitigate, administrators shall install Pitney Bowes DeviceHub version 1.9.x into the program’s files directory. Per Pitney Bowes, install will default to Program Files directory in future dot release. Device Hub uses AWS IoT. IoT devices require separate authorization and must be securely isolated behind the Specialized Device Isolation Architecture (SDIA) VLAN. To mitigate, VA Network-connected SPS-OT devices are required to go through the Enterprise Risk Analysis (ERA) Process. The ERA risk assessment review process enables cybersecurity teams to identify, evaluate, and address unique network connection requirements for Specialized Devices/Systems in accordance with VA and federal policies and guidelines. SPS-OT ERA requirements can be located on System Security Support Risk Analysis Portal. The user’s guide for how to submit an ERA request can be found at ERA Joint Users Guide under Risk Analysis Guidance and Special Purpose Systems headings. Once an SPS-OT device receives an approved ERA the SPS-OT device will be securely isolated behind the Specialized Device Isolation Architecture (SDIA) VLAN. The SDIA ruleset and the Specialized Device Isolation Architecture Guidance documents outlines specific SDIA requirements. Device installation required the disabling of the Windows 10 SmartScreen security feature. Group Policy Objects (GPO) are set nationally by Solution Delivery Desktop and Device Engineering (DDE). To mitigate, Administrators must submit GPO or computer registry setting changes to Desktop and Device Engineering. Requests (sharepoint.com) DeviceHub installs an outdated Open-Source Software - Python 3.8.6, with multiple CVE’s. To mitigate, administrators must apply the latest security patches to mitigate CVE’s. To mitigate, maintenance and support will be provided for the Open Source Software used within DeviceHub version 1.9.x as per the applications lifecycle. DeviceHub installs Open-Source Software - 7-Zip 19.00. To mitigate, maintenance and support will be provided for the Open Source Software used within DeviceHub version 1.9.x as per the applications lifecycle. DeviceHub installs Open-Source Software – Poppler 21.10.0. To mitigate, maintenance and support will be provided for the Open Source Software used within DeviceHub version 1.9.x as per the applications lifecycle. DeviceHub includes outdated versions of OpenSSL Libraries. To mitigate Open SSL will be updated when Python is updated in next dot release of Device Hub. Maintenance and support will be provided within DeviceHub version 1.9.x as per the applications lifecycle.

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

[4]	This product includes a Bluetooth capability. If that capability is leveraged, the implementer must conform to the Bluetooth Standard. 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]	New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a WAN impact review (yourIT Service Portal:[SNOW Service Requests]) prior to implementation to ensure proper compliance to VA network design and usage requirements.

[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 ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500.

[7]	This product includes a Bluetooth capability. If that capability is leveraged, the implementer must conform to the Bluetooth Standard. 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.

[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 ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500.

[9]	Users must ensure that VMWare vSphere is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) This technology requires using a Universal Service Bus (USB) technology to transfer data into the records. As such, proper precautions need to be taken to protect data. Per the Security Assessment Review, users must abide by the following constraints: Pitney Bowes DeviceHub version 1.9.X default installs off the root of c:\. To mitigate, administrators shall install Pitney Bowes DeviceHub version 1.9.x into the program’s files directory. Per Pitney Bowes, install will default to Program Files directory in future dot release. Device Hub uses AWS IoT. IoT devices require separate authorization and must be securely isolated behind the Specialized Device Isolation Architecture (SDIA) VLAN. To mitigate, VA Network-connected SPS-OT devices are required to go through the Enterprise Risk Analysis (ERA) Process. The ERA risk assessment review process enables cybersecurity teams to identify, evaluate, and address unique network connection requirements for Specialized Devices/Systems in accordance with VA and federal policies and guidelines. SPS-OT ERA requirements can be located on System Security Support Risk Analysis Portal. The user’s guide for how to submit an ERA request can be found at ERA Joint Users Guide under Risk Analysis Guidance and Special Purpose Systems headings. Once an SPS-OT device receives an approved ERA the SPS-OT device will be securely isolated behind the Specialized Device Isolation Architecture (SDIA) VLAN. The SDIA ruleset and the Specialized Device Isolation Architecture Guidance documents outlines specific SDIA requirements. Device installation required the disabling of the Windows 10 SmartScreen security feature. Group Policy Objects (GPO) are set nationally by Solution Delivery Desktop and Device Engineering (DDE). To mitigate, Administrators must submit GPO or computer registry setting changes to Desktop and Device Engineering. Requests (sharepoint.com) DeviceHub installs an outdated Open-Source Software - Python 3.8.6, with multiple CVE’s. To mitigate, administrators must apply the latest security patches to mitigate CVE’s. To mitigate, maintenance and support will be provided for the Open Source Software used within DeviceHub version 1.9.x as per the applications lifecycle. DeviceHub installs Open-Source Software - 7-Zip 19.00. To mitigate, maintenance and support will be provided for the Open Source Software used within DeviceHub version 1.9.x as per the applications lifecycle. DeviceHub installs Open-Source Software – Poppler 21.10.0. To mitigate, maintenance and support will be provided for the Open Source Software used within DeviceHub version 1.9.x as per the applications lifecycle. DeviceHub includes outdated versions of OpenSSL Libraries. To mitigate Open SSL will be updated when Python is updated in next dot release of Device Hub. Maintenance and support will be provided within DeviceHub version 1.9.x as per the applications lifecycle.

[10]	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 ISSO (Information System Security Officer) can advise on the ESCCB review process.

[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, visit the Product Marketplace. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[12]	The Federal Information Processing standards (FIPS) 140-2 certification status of this technology was not able to be verified. This technology will require a 3rd party FIPS 140-2 or 140-3 certified solution for any data containing PHI/PII or VA sensitive information, where applicable. More information regarding the Cryptographic Module Validation Program (CMVP) can be found on the NIST website.

Note:

At the time of writing, 1.10.29.22 is the most current version released 01/10/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
7-zip	This technology is used as a file archiver.
Device Agent	The DeviceHub Agent is a Windows-based software component that runs on the customer’s premises. It is installed via a single MSI file.
Poppler	This is an open-source software used to render portable document files (PDF).

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Collaboration and Electronic Workplace Productivity Software	Miscellaneous Productivity Tools and Utilities

Operating Systems Supported by the Technology

Windows Client - Approved w/Constraints

Technologies/Standards Relationships

Runtime Dependencies:

Chocolatey - (required for some configurations)
Microsoft .NET Framework
Node.js
Visual C++ Redistributable Package
VMware vSphere
Wireshark - (required for some configurations)

Comparable Technologies:

Samsung Cloud Print

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

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 technology may improve productivity for specific staff whose responsibilities include printer administration and maintenance.
This is a well documented technology.
This technology supports several industry standard file formats.

Adoption Risks

Although this vendor utilizes Federal Information Processing (FIPS) 140-2 encryption, there is no indication based on the vendor documentation or the Cryptographic Module Validation Program (CMVP) that this technology is Federal Information Processing Standards (FIPS) 140-2 certified.
This technology involves the use Bluetooth connections and proper security precautions must be taken when used.
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 may utilize external data connections.
DeviceHub uses AWS IoT. IoT devices require separate authorization and must be securely isolated behind the Specialized Device Isolation Architecture (SDIA) VLAN.
There is no publicly available documentation regarding the Pitney-Bowes Device Hub. All information was obtained directly from the vendor.
DeviceHub may require access to VA Wireless Network.
DeviceHub client software requires several dependencies that are listed in the TRM at different approval status.
Pitney Bowes DeviceHub version 1.9.X default installs off the root of c:\.
Device installation required the disabling of the Windows 10 SmartScreen security feature.
DeviceHub installs an outdated Open-Source Software - Python 3.8.6, with multiple CVE’s.
DeviceHub installs Open-Source Software - 7-Zip 19.00.
DeviceHub installs Open-Source Software – Poppler 21.10.0.
DeviceHub includes outdated versions of OpenSSL Libraries.
This technology involves the use Universal Serial Bus (USB) connections and proper security precautions must be taken when used.

Architectural Benefits

This technology is compatible with virtual machines, therefore consistent with the enterprise Server Virtualize First Policy (VAIQ 7266972 08-27-2012).
This technology is compatible with multiple other Technical Reference Model (TRM) technologies and standards used by the organization.

Architectural Risks

This technology includes cloud-based functionality which has potential information security risks.
This technology is not portable as it runs only on Windows platforms.

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 (02/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 (02/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