Good morning folks

I am currently working on a migration project from Sterling's database document storage to a File System. The client requires encryption for stored documents; however, the default encryption provided by Sterling is considered too heavy, and they are looking for a lighter alternative.

They mentioned the possibility of implementing something similar to the encryption used in the TRANS_DATA table (internal to Sterling). However, after researching, I haven't been able to find any public documentation or official implementation guidance regarding this.

I'm currently using the following custom properties:  

jdbcService.document_dir = /home/filesystem  
jdbcService.RESTORE_DOCUMENT_DIR = /home/filesystem/restored  
jdbcService.getAbsolutePath = true  
jdbcService.defaultDocumentStorageType = FS  
jdbcService.LWJDBC.writeDocForNonSelect = false  
security.CERT_NAME = doccrypto  
security.ENC_DECR_DOCS = ENC_FS  
security.ENC_ALG = AES-128  
resourceMonitor.ScheduleMonitor.propertyValue.1 = SELECT STATUS, SERVICENAME FROM SCHEDULE WHERE SERVICENAME IN ('BackupService','IndexBusinessProcessService','AssociateBPsToDocs','BPRecovery','BPLinkagePurgeService')

My main concern is whether security.ENC_ALG = AES-128 is actually functional and enforced when encrypting documents to File System.

Additionally, I understand that for data cleanup and document lifecycle management, it is recommended to use External Purge together with Data Sweeper. Could you confirm if this is the proper approach in hybrid environments?

Any guidance or official references would be greatly appreciated.

Best regards,

------------------------------
Rodrigo Ricardo Pérez memije
------------------------------

Hi Rodrigo,

I believe the value for ENC_ALG can only be "AES".  The default key size is 128.

Also, yes; External Purge is the recommended option.  It allows for all purging activity to be done in a separate JVM outside of the Sterling JVM and has been shown to have a massive performance improvement compared to internal purge.  DataSweeper should also be run regularly to enable cleanup of orphaned records and other things based on the sweeper module.

Regards,

Vivek Mittal

jdbcService.document_dir = /home/filesystem  jdbcService.RESTORE_DOCUMENT_DIR = /home/filesystem/restored  jdbcService.getAbsolutePath = true  jdbcService.defaultDocumentStorageType = FS  jdbcService.LWJDBC.writeDocForNonSelect = false  security.CERT_NAME = doccrypto  security.ENC_DECR_DOCS = ENC_FS  security.ENC_ALG = AES-128  resourceMonitor.ScheduleMonitor.propertyValue.1 = SELECT STATUS, SERVICENAME FROM SCHEDULE WHERE SERVICENAME IN ('BackupService','IndexBusinessProcessService','AssociateBPsToDocs','BPRecovery','BPLinkagePurgeService')