Dynamic Web TWAIN (DWT)

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:	Dynamic Web TWAIN (DWT) is a document scanning software development kit (SDK) designed for web applications. This technology allows users to develop applications that scan documents from TWAIN and SANE compatible scanners, edit the scanned images and save those images to a local/server file system or document repository. DWT supports setting image scanning parameters including resolution, pixel type, page size, Automatic Document Feeder (ADF) scanning, and duplex scanning.
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.11
Decision Date:	11/01/2023 at 16:44:58 UTC
Aliases:	(DWT) Dynamsoft Web TWAIN
Introduced By:	TRM Request
Vendor Name:	Dynamsoft

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
11.x	07/23/2015
12.x	09/22/2016
13.x	06/20/2017
14.x	07/16/2018
15.x	06/27/2019
16.x	06/16/2020
17.x	04/20/2021
18.x	10/24/2023

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

CY2019

CY2020

CY2021

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

11.x

Unapproved

12.x

Unapproved

13.x

Approved w/Constraints
[2, 3, 4]

Divest
[2, 3, 5, 6]

Divest
[2, 3, 6, 7]

Unapproved

14.x

Unapproved

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

Divest
[2, 3, 6, 7]

Unapproved

15.x

Unapproved

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

Divest
[2, 3, 6, 7]

Divest
[2, 6, 7, 8]

Unapproved

16.x

Unapproved

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

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

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

17.x

Unapproved

18.x

Unapproved

Decision Constraints


[1]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. File Transfer Protocol is a prohibited standard within VA and must not be used. Ensure use of a FIPS 140-2 validated cryptographic module to secure VA sensitive data in applications and devices. Database Management Systems (DBMS) used in VA will be encrypted using FIPS 140-2 (or its successor) validated encryption as stated in section SC-28: Protection of information at Rest of the VA Handbook 6500.If FIPS 140-2 at the application level is not possible technically, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides as stated in the May 5, 2015 memo from the VA Deputy Assistant Secretary for Information Security titled `FIPS 140-2 Validated Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS)`. System administrators may wish to reassess whether they want to deploy SSL inspection capabilities with the VA environment. CERT Tapioca can be used to verify that the SSL inspection solution being used is doing its due diligence to minimize the increased risk to the users. At the very least, system administrators could contact the vendors of SSL inspection software to have them confirm the proper configuration options and behaviors. Addressing the generic concern of scanning, uploading and downloading of files into a browser all security concerns with regards to uploading VA files to the Internet must be evaluated to ensure proper use and behavior are expected. Risks with uploading VA files to the Internet need to be examined. Literature of VeriSign digital signing of scanned documents for Dynamsoft Web Twain security issues must be monitored before use. This includes monitoring for Common Vulnerabilities and Exposures (CVE), and also blog citations posted by the software developer. The product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. 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.

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

[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]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. File Transfer Protocol is a prohibited standard within VA and must not be used. Ensure use of a FIPS 140-2 validated cryptographic module to secure VA sensitive data in applications and devices. Database Management Systems (DBMS) used in VA will be encrypted using FIPS 140-2 (or its successor) validated encryption as stated in section SC-28: Protection of information at Rest of the VA Handbook 6500.If FIPS 140-2 at the application level is not possible technically, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides as stated in the May 5, 2015 memo from the VA Deputy Assistant Secretary for Information Security titled `FIPS 140-2 Validated Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS)`. System administrators may wish to reassess whether they want to deploy SSL inspection capabilities with the VA environment. CERT Tapioca can be used to verify that the SSL inspection solution being used is doing its due diligence to minimize the increased risk to the users. At the very least, system administrators could contact the vendors of SSL inspection software to have them confirm the proper configuration options and behaviors. Addressing the generic concern of scanning, uploading and downloading of files into a browser all security concerns with regards to uploading VA files to the Internet must be evaluated to ensure proper use and behavior are expected. Risks with uploading VA files to the Internet need to be examined. Literature of VeriSign digital signing of scanned documents for Dynamsoft Web Twain security issues must be monitored before use. This includes monitoring for Common Vulnerabilities and Exposures (CVE), and also blog citations posted by the software developer. The product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. 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.

[5]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. File Transfer Protocol is a prohibited standard within VA and must not be used. Per the Initial Product Review, users must abide by the following constraints: Ensure use of a FIPS 140-2 validated cryptographic module to secure VA sensitive data in applications and devices. If it is not technically possible to employ FIPS 140-2 encryption, then other third-party encryption solutions must be used. A data loss prevention (DLP) strategy should be employed to insure no Protected Health Information (PHI) / Personally Identifiable Information (PII) is disclosed. VA must enforce a usage policy to supplement DWT`s security controls until an acceptable DLP solution is deployed. Usage of DWT should be limited by role-based access controls ensuring the security of the VA network infrastructure and administrators must agree on scanning rules, such as: assets users are allowed to scan, the schedule, and frequency of scans.

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

[7]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users must ensure that Microsoft Internet Explorer (IE), Firefox, Google Chrome, and Safari are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) File Transfer Protocol is a prohibited standard within VA and must not be used. Per the Initial Product Review, users must abide by the following constraints: Ensure use of a FIPS 140-2 validated cryptographic module to secure VA sensitive data in applications and devices. If it is not technically possible to employ FIPS 140-2 encryption, then other third-party encryption solutions must be used. A data loss prevention (DLP) strategy should be employed to insure no Protected Health Information (PHI) / Personally Identifiable Information (PII) is disclosed. VA must enforce a usage policy to supplement DWT`s security controls until an acceptable DLP solution is deployed. Usage of DWT should be limited by role-based access controls ensuring the security of the VA network infrastructure and administrators must agree on scanning rules, such as: assets users are allowed to scan, the schedule, and frequency of scans.

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

[9]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users must ensure that Firefox and Google Chrome are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) Users must Divest the use of Internet Explorer with this technology. Other approved internet browsers are available. See Category Tab for details. File Transfer Protocol is a prohibited standard within VA and must not be used. Per the Initial Product Review, users must abide by the following constraints: Ensure use of a FIPS 140-2 validated cryptographic module to secure VA sensitive data in applications and devices. If it is not technically possible to employ FIPS 140-2 encryption, then other third-party encryption solutions must be used. A data loss prevention (DLP) strategy should be employed to insure no Protected Health Information (PHI) / Personally Identifiable Information (PII) is disclosed. VA must enforce a usage policy to supplement DWT`s security controls until an acceptable DLP solution is deployed. Usage of DWT should be limited by role-based access controls ensuring the security of the VA network infrastructure and administrators must agree on scanning rules, such as: assets users are allowed to scan, the schedule, and frequency of scans.

Note:

At the time of writing, version 18.4.1 is the most current version, released on 10/24/2023.

A standard configuration of this technology was developed by the DDE team. At the time of writing, the standard version is 1.4.1230 , and version 1.7.0330 is under testing and development for six weeks from 10/25/2023. DDEs versioning of this is separate from how the vendor supplies and versions as DDE follows what registers in programs and features. This release is under the 17.x umbrella.

References

The following reference(s) are associated with this entry:
Type	Name	Source	Description
Other	Data Sheet: Dynamic Web TWAIN		This page links to the overview and system requirements of Dynamic Web TWAIN.
Other	Release Notes		This site links to release notes for Dynamic Web TWAIN.

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
Dynamsoft Service x86	This component allows access to a connected scanner in JavaScript and Hypertext Markup Language (HTML). With a few lines, the user can scan a batch of documents from TWAIN and SANE.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Application Technology Development Tools	Development Frameworks

Operating Systems Supported by the Technology

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

Technologies/Standards Relationships

Runtime Dependencies:

Microsoft Edge.
Microsoft Internet Explorer (IE) - (required for some configurations)
Safari

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

This is a well-documented technology.
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 supports a number of industry standard file formats.

Adoption Risks

There are other VA-approved comparable solutions, and the adoption of this technology could result in duplicate functionality and compatibility issues.
This software 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.
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.
DWT uses the Symantec SSL cert for HTTP uploading and downloading to ensure data security during transfer while locally cached images use Blowfish AES-256-GCM encryption. However, there is no indication the product itself is Federal Information Processing Standards (FIPS) 140-2 or 140-3 certified.
DWT allows users to scan, upload, and download files in a browser, which may allow files to be transferred across the internet.
By matching the current website domain to the registered domain in the product key, DWT limits access to a scanner device to only the registered web scanning application.
Microsoft Internet Explorer, a dependency of this technology, is in End of Life status and must no longer be used.
This technology can potentially use File Transfer Protocol (FTP), an unapproved protocol.
This technology can potentially use Bitmap, which is divested in the TRM.

Architectural Benefits

The technology is portable as it runs on multiple VA-approved operating systems.

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/31/2023)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (10/31/2023)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

EMAIL UPDATES