Laserfiche WebLink
SOLICITATION # CH16012 <br />email system to send email to ServiceNow over TLS and ServiceNow will receive that email over <br />TLS. <br />Encryption at Rest <br />ServiceNow can provide three types of encryption for data at rest that are implemented by the <br />customer or by customer request in the case of edge encryption and dedicated hardware. <br />-Column encryption of customer added fields and attachments: Provides data encryption using <br />AES128/256 or 3DES symmetric key encryption. The customer provides the keys for this encryption. <br />Data stored in these fields cannot be searched or reported on and this does not support out of the <br />box fields. <br />-Edge Encryption Proxy: With optional additional cost Edge Encryption, the customers create and <br />control their encryption keys within their own network. Edge Encryption includes a proxy application <br />that resides in a customer's network. This encrypts data before it is sent (also encrypted in transit) <br />from the customer's environment to the ServiceNow instance. The data always remains encrypted <br />whilst stored in the instance and the data along with the keys and the encryption configuration is <br />never accessible by ServiceNow. Requests for encrypted data must also be made through the proxy <br />application and is therefore decrypted only within the customer's network before being sent to their <br />end users client browser. Please note that data encrypted with Edge encryption cannot be used by <br />back -end scripts or processes and searching and reporting behavior is also modified through its use. <br />-Full disk encryption: Provides via self -encrypting hard drives with AES256 bit encryption. This <br />encryption capability is only available through the purchase of dedicated ServiceNow hardware at an <br />additional cost. This delivers "at -rest" protection only and is focused solely on preventing data <br />exposure through the loss or theft of hard disks holding customer data. <br />Wherever possible, ServiceNow leverages existing FIPS 140-2 certified technologies. <br />Docusign <br />Secure, private SSL 256 bit viewing session <br />Anti -tampering controls <br />Signature verification of signing events <br />Unalterable, systematic capture of signing data <br />Digital certificate technology <br />Customer confi urable data retention program <br />SAP <br />Ariba <br />We enforce minimum AES 128-bit encryption using Transport Layer Security <br />(TLS) for all sessions. We encrypt only PCI-DSS data in the database where <br />appropriate and in support of PCI-DSS compliance. All backup media is <br />encrypted using AES 256-bit cipher prior to transporting to off -site storage <br />Fieldglass <br />Our application provides a high level of application -level security through a <br />combination of encryption, page -level access checking, document envelopes, <br />and activity logging. Application security is handled through a combination of <br />programming checks, application server configuration, and database server <br />configuration. Fieldglass uses 2048-bit SSL (HTTPS) encryption for all data <br />transmissions over the public Internet, including data shared between the <br />product and end users and data shared between the product and back -end <br />systems. Data is decrypted on the internal VLAN to allow IDS monitoring. <br />Passwords are hashed using a one-way hash based on the SHA-256 <br />encryption algorithm. The hash value is saved within the database; not the <br />password. <br />The base Fieldglass application does not require data that would require <br />breach notifications if compromised. While customers should not store <br />sensitive personal data, custom fields may be defined by the customer that <br />can be encrypted with AES-256 to capture any pertinent and permissible data <br />points. These fields can also be optionally masked from view while entering <br />and viewing the fields in the application. <br />carahsoft 123 carahsoft <br />