Encryption - Architecture Advanced Design and Setup Guide - Foundation 24.1 - Foundation 24.1 - Ready - Perceptive Content - external

Architecture Advanced Design and Setup Guide

Platform
Perceptive Content
Product
Architecture Advanced Design and Setup Guide
Release
Foundation 24.1
License

Perceptive Content delivers AES (Advanced Encryption Standard) encryption using the AES-256 block cipher. This encryption method uses a 256-bit encryption key to encrypt plain text into cipher text. AES is the first publicly accessible and open cipher to gain the approval of the National Security Administration (NSA) for the encryption of top secret information. Perceptive Content’s AES encryption uses FIPS 140-2 Certified Cryptographic Provider modules from Microsoft and Certicom. You can use AES for user authentication requests for Perceptive Content.

Whether capturing a document or streaming content to the client for retrieval, Perceptive Content can provide encrypted, port-level access to authenticated users through 256-bit AES encryption, which encrypts the TCP/IP message stream between the Perceptive Content Server and external agents, Perceptive Content Clients, Interact for Office Clients, and Interact for eCopy Clients. AES Encryption is optional and is not enabled by default. To enable encryption, you configure the inow.ini file on your Perceptive Content Server.

HTTP(S) (SSL) is a fully supported transport encryption method between Integration Server and REST clients. Perceptive Content offers 128-bit SSL encryption between Integration Server and any application using the Integration Server API. In addition, 128-bit SSL encryption is available for Interact clients, such as Interact for Epic and Interact for Lexmark.