Solution Overviews

Key Usage Models On Secure App Service (SAS)

Issue link:

Contents of this Issue


Page 1 of 2

If you are looking for a "default" option, here is what we would recommend: • Java files: unique keys • Android files: on-demand keys • Microsoft files: rotating keys • Other files (default): unique keys All signing models are enabled by default on SAS. When you select a signing service (e.g., Authenticode signing) the platform will automatically select the relevant model for you (the pool of rotating keys in this instance). It is possible to change this automatic selection for the signing service of your choice to align with your needs and maximize security. Key Usage Models on Secure App Service (SAS) 2 © 2018 DigiCert, Inc. All rights reserved. DigiCert is a registered trademark of DigiCert, Inc. in the USA and elsewhere. All other trademarks and registered trademarks are the property of their respective owners. Lightning-Fast Application Signing on Windows, OpenSSL, & Java DigiCert Secure App Service enables you to sign large-sized applications without uploading them to the Secure App Service cloud. The solution works in partnership with our APIs and a local application installed to perform signing of large files by computing the hash of the application being requested for signing and passing that hash to SAS for signing in the cloud. Once the hash is signed, SAS sends it back to the local application, which adds it to the local file and thus the application is signed. You retain the benefit of key protection, user management, and reporting provided by SAS. The malware scanning service included with SAS is not available with lightning-fast signing, since only the hash of your file is uploaded to SAS, and not the entire file. Related Services DigiCert Secure App Service (SAS) 1 is part of our Complete Website Security (CWS) solution) 2 . 1 2

Articles in this issue

Links on this page

view archives of Solution Overviews - Key Usage Models On Secure App Service (SAS)