FMAudit Onsite

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:	FMAudit Onsite is a software solution that automatically performs print assessments, monitors consumable levels and printer status. The solution leverages a central website repository and client agents. Print job data captured is sent to the central website (FMAudit Central Server) using HyperText Transfer Protocol Secure (HTTPS) or HyperText Transfer Protocol (HTTP). Central repository deployment options include vendor hosted, on-premise and hybrid. Note: FMAudit Onsite is part of the FMAudit suite of technologies. Note: FMAudit has been acquired by Toshiba from ECi Software Solutions, inc. 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.3
Decision Date:	03/27/2023 at 15:43:23 UTC
Aliases:	Managed Print Service (MPS)
Introduced By:	TRM Request
Vendor Name:	Toshiba

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
3.0	12/06/2013
3.1	10/19/2015
3.5	01/04/2016
3.6	02/01/2017
3.7.x	06/22/2018
4.1.x	11/09/2021

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

3.0

Divest
[2, 3]

Divest
[2, 3, 4]

Divest
[2, 4, 5]

Unapproved

3.1

Approved w/Constraints
[2, 3]

Divest
[2, 3, 4]

Divest
[2, 4, 5]

Divest
[4, 5, 6, 7]

Unapproved

3.5

Approved w/Constraints
[2, 3]

Approved w/Constraints
[2, 3, 4]

Approved w/Constraints
[2, 4, 5]

Divest
[4, 5, 6, 7]

Divest
[4, 5, 7, 8, 9]

Unapproved

3.6

Unapproved

Approved w/Constraints
[2, 3, 4]

Approved w/Constraints
[2, 4, 5]

Approved w/Constraints
[4, 5, 6, 7]

Divest
[4, 5, 6, 7]

Divest
[4, 5, 7, 8, 9]

Unapproved

3.7.x

Unapproved

Approved w/Constraints
[4, 5, 6, 7]

Approved w/Constraints
[4, 5, 7, 8, 9]

Approved w/Constraints
[4, 5, 8, 9, 10]

4.1.x

Unapproved

Decision Constraints


[1]	Although print job content is not captured, some of the information captured about the print job may be considered sensitive. Users interested in this solution must contact their local ISO (Information Security Officer) to ensure VA sensitive data in transit and at rest is properly protected in compliance with VA Handbook 6500. Product`s central repository deployment includes a vendor hosted option, which may not be used without Enterprise Security Change Control Board (ESCCB) review and approval to ensure that confidential organization and/or sensitive data are not compromised. The solution features include Bi-Directional Enterprise Resource Planning (ERP) Synchronization, which provides two-way communication with billing and service dispatch systems. This functionality may not be used with external, third-party systems without first being fully vetted through the Assessment and Authorization (A&A) process and a Memorandum of Understanding/Interconnection Security Agreement (MOU/ISA) in place.

[2]	Although print job content is not captured, some of the information captured about the print job may be considered sensitive. Users interested in this solution must contact their local ISO (Information Security Officer) to ensure VA sensitive data in transit and at rest is properly protected in compliance with VA Handbook 6500. Product`s central repository deployment includes a vendor hosted option which may not be used without Enterprise Security Change Control Board (ESCCB) review and approval to ensure that confidential organization and/or sensitive data are not compromised. The solution features include Bi-Directional Enterprise Resource Planning (ERP) Synchronization which provides two-way communication with billing and service dispatch systems. This functionality may not be used with external, third-party systems without first being fully vetted through the Assessment and Authorization (A&A) process and a Memorandum of Understanding/Interconnection Security Agreement (MOU/ISA) in place.

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

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

[6]	Users must contact their local Information Security Officer (ISO) to ensure VA sensitive data in transit and at rest is properly protected in compliance with VA Handbook 6500. Users must ensure that the underlying infrastructure (operating system, Web Server, etc.) can protect the security of the application by providing Federal Information Processing Standard (FIPS) 140-2 encryption. Users must ensure Enterprise Security Change Control Board (ESCCB) review and approval to ensure that confidential organization and/or sensitive data are not compromised due to the product`s central repository deployment including a vendor hosted option. Users must not use the Bi-Directional Enterprise Resource Planning (ERP) Synchronization functionality which provides two-way communication with billing and service dispatch systems with external, third-party systems without first being fully vetted through the Assessment and Authorization (A&A) process and users must also ensure a Memorandum of Understanding/Interconnection Security Agreement (MOU/ISA) in place.

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

[8]	Per the Initial Product Review, user must abide by the following constraints: Users must ensure that the underlying infrastructure (operating system, Web Server, etc.) can protect the security of the application by providing Federal Information Processing Standard (FIPS) 140-2 encryption. Users must ensure Enterprise Security Change Control Board (ESCCB) review and approval to ensure that confidential organization and/or sensitive data are not compromised due to the product`s central repository deployment including a vendor hosted option. Consideration must be taken when reconfiguring antivirus programs and software firewalls on client systems, allowing applications interconnected communication access to other applications, systems, or devices.

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

[10]	This technology should only be used when required by a Veterans Affairs (VA) business partner for an approved VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. As of January 27th, 2017, Risk-based Decisions (RBD) will be handled per VAIQ # 7769667. 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 and ensure privacy of information compliance protections are in place.

Note:

At the time of writing, version 4.1.3 is the most current version released.

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
No components have been identified for this entry.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Network and Telecommunications Transport	Local/Campus Area Network (LAN/CAN)

Operating Systems Supported by the Technology

Windows Client - Approved w/Constraints
Windows Server - Approved w/Constraints

Technologies/Standards Relationships

Runtime Dependencies:

Microsoft .NET Framework

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Use of this technology may help reduce site printing costs through the analysis of printer and consumable use to identify more efficient enterprise print strategies.
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 is interoperable with other TRM-approved software to provide enhanced functionality.

Adoption Risks

System scans indicate this technology is no longer used within VA.
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.
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.
This technology has the ability to transfer data to either an off-premise or an on-premise server for processing.
ECi FMAudit is not Federal Information Processing standards (FIPS) 140-2 certified.

Architectural Risks

The FMAudit Agent connects back to the vendor cloud and provides data on services the computer is using (such as print services).
This technology connects back to the vendor cloud and provides data on services the computer is using (such as print services).
This technology includes cloud-based functionality which has potential information security risks.
This technology is not portable as it runs on only 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 (03/16/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 Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (03/16/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 Risks

EMAIL UPDATES