PrinterLogic Web Stack Server is a web application that is used to manage on-premise application designed to simplify the management, migration, and provisioning of printers. PrinterLogic Web Stack Server facilitates features including centrally-managed direct IP printing, self-service installation of printer drivers, automated deployment of drivers, centralized reporting of printer usage, and pull/mobile printing.
\r\nPrinterLogic Web Stack Server is part of a client-server distribution. The TOE is the server portion of this distribution. It interacts with remote PL Client applications in its operational environment.
","evaluation_configuration":"","security_evaluation_summary":"\r\nThe evaluation was carried out in accordance with the Common Criteria Evaluation and Validation Scheme (CCEVS) process and scheme. The criteria against which the PrinterLogic TOE was judged are described in Protection Profile for Application Software, Version 1.3, 1 March 2019 and the Common Criteria for Information Technology Security Evaluation, Version 3.1 rev 5. The evaluation methodology used by the evaluation team to conduct the evaluation is the Common Methodology for Information Technology Security Evaluation, Version 3.1 revision 5 as refined by the assurance activities in the protection profile. The product satisfies all of the security functional requirements stated in the PrinterLogic Web Stack Server v18.3 Security Target, version 1.0, November 27, 2019, when delivered and configured as identified in the following documents:
\r\n· PrinterLogic Web Stack version 18.3 Common Criteria Supplemental Guidance Version 1.0, 23 October 2019
\r\nThe project underwent CCEVS Validator review. The evaluation was completed in December 2019. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report prepared by CCEVS.
","environmental_strengths":"\r\n\r\nThe TOE uses NIST-validated cryptographic algorithms to secure data in transit. The TOE relies on the FIPS-validated cryptographic library cng.sys provided by Windows to perform cryptographic functionality. The TSF encrypts credential data stored by the TOE in the environmental SQL database.
\r\nThe TOE relies on its underlying OS platform to implement TLS/HTTPS server functionality. The TOE also relies on its underlying OS platform to provide entropy used for key generation.
\r\n\r\nThe TSF leverages functionality provided by their underlying OS platform to secure sensitive data at rest. The TOE uses network resources provided by the underlying platform. All platform services are invoked with user awareness and authorization.
\r\nThe TOE uses network connectivity to handle interactive user and administrator sessions and to communicate with environmental PL Clients for the purpose of applying configuration changes and updating the status of held print jobs.
\r\nSecurity Management
\r\nThe Web Server provides an Admin Console GUI for configuration of environmental PL Client activity. Specifically, an administrator can designate a PL Client as a Service Host and configure it to work with email printing and mobile printing, thus defining the trusted channels used by a PL Client.
\r\nThe Web Server also provides Self-Service Portal and Release Portal GUIs that allow users to control printing activity. The Release Portal is used to release print jobs, which prompts secure communications back to environmental PL Clients (Service Hosts) to initiate the print operation.
\r\nAuthentication to the Web Server is performed using locally-defined credentials. On initial installation, the administrator is prompted to specify credentials to be used for the Admin Console.
\r\nTOE configuration data is stored locally in the Windows Registry.
\r\nPrivacy
\r\nThe TOE does not handle personally identifiable information (PII).
\r\nProtection of the TSF
\r\nThe TOE includes measures to integrate securely with its underlying OS platform. The TOE does not perform explicit memory mapping and it does not allocate any memory region with both write and execute permissions. Similarly, the TSF does not write user-modifiable data to directories that contain executable files. The TOE is compatible with its host OS platform when that platform is configured in a secure manner. The TOE is not written in a language that is susceptible to stack-based buffer overflow attacks.
\r\nThe TOE uses a well-defined set of platform APIs and third party libraries.
\r\nThe TOE provides the ability for a user/administrator to check its version and to apply updates. Updates are delivered in formats appropriate for the platform on which the TOE is installed. Application of an update removes all executable code associated with the application; there is no way for the application to modify its own code. Updates the TOE are digitally signed, and the signature is validated prior to installation.
\r\nTrusted Path/Channels
\r\nTOE components use trusted paths and channels to secure data in transit. The following interfaces are provided by each TOE component:
\r\n· Web Server:
\r\no TLS/HTTPS server for remote user/administrator access
\r\no TLS/HTTPS server for changes to PI Client configuration data and pull printing status
","features":[]}