# Operating modes

## Operating modes

The SignBox system is available in two modes: as a network security appliance fully managed locally (on-premises) by the customer, or as a virtual machine, also installed locally, but leveraging a remote automatic signing service at a Trusted Service Provider.
To make integration with management and application systems immediate, it is configured simply as a service (webservice interface), or as a network printer (virtual printer). Alternatively, it can poll from shared network folders and process the contained documents according to options configurable from the administrative interface.

## SignBox on premises

The system serves can be dedicated as "application server" for signature and time-stamping systems. SignBox in the proposed version includes a Hardware Security Module (HSM) based on a pool of smartcards with associated automatic signature certificates. The internal HSM system can be upgraded to accommodate a number of up to 7 smartcards to ensure better performance and/or a larger number of signers.

We take as an example the case where the SignBOX is configured to work in polling. In the diagram shown we have two shared network folders. One serves as the input folder (where the files to be signed are deposited) while the other serves as the output folder (where the signed files are deposited instead).

In polling, the optimizer goes to collect the data in the input folder and goes to perform all the relevant computational operations such as hashing the document to be signed. This step is indispensable both in this flow and in the remote flow because by doing so it goes to pass to the HSM only the hash of the document to be signed and not the document itself going to safeguard privacy on those documents. It also goes to simplify the signing operation because this must be done on a much smaller file than the original one. After signing, the signed files are then deposited in the output folder.

## SignBox Remote

Through configuration which requires SignBox to be used as an automatic signature service offered by a Trusted Service Provider (OnCloud). The client and end users will need to install a lightweight client and agent on the workstation that will:

- retrieve the documents to be signed.
- process locally at the user's PC the hash of the file, thus safeguarding the confidentiality of the document.
- send the hash to be signed to the remote SignBox at the TSP
- receive the signed hash from the TSP and compose locally to the user's PC the digitally signed file.
- save the signed file to the network folder from which the web application will then publish online.