We have a specific question regarding IFS Cloud Document Management security.
The document repository is located on a sovereign SMB server/share, and the end user is also located within that same sovereign environment. However, the IFS Cloud application tier and DB is hosted remotely in another country.
Our requirement is that cryptographic protection is applied before the document leaves the originating sovereign security boundary and remains intact until it reaches the intended recipient’s sovereign security boundary.
In practical terms, we need to understand whether the IFS Cloud middle tier ever decrypts or materialises the document content in plaintext while it is being transferred between the SMB repository and the client, including in volatile memory (RAM).
For example:
Download / View
Sovereign SMB Repository → Remote IFS Cloud Middle Tier → Sovereign Client
Check-in
Sovereign Client → Remote IFS Cloud Middle Tier → Sovereign SMB Repository
The requirement is that the remote application tier must not have access to the document content in plaintext. The middle tier may transport or proxy encrypted content, but it must not decrypt the file in order to process, index, scan, preview or render it.
Could someone confirm:
- Whether DocMan file transfer is end-to-end encrypted between repository and client, or whether TLS terminates at the IFS middle tier and a new encrypted session is then established?
- Whether document content is ever present in plaintext in middle-tier memory during View, Download, Check-out or Check-in.
- Whether features such as Document Preview, indexing or other document-processing functions cause the document to be decrypted or processed by the middle tier.
- Whether there is a supported configuration that allows the middle tier to act only as a transport/proxy without access to the plaintext document.
If this architecture can meet the requirement, are there specific DocMan features that should be disabled, such as Document Preview?
Thanks.
Stuart