FAQ

Where is the sensitive information stored?

In the database.

Is an attempt of data modification directly in the database detected?

Yes, all information which is considered sensitive is protected by a data seal. This applies to both data flows and static data. This can be customized to include other data fields as well.

Where and how is the private key stored?

By default the key is stored inside the application ear file, optionally it can be stored on a secondary protected directory on the file system. The key is contained in a serialized (encrypted) javax.crypto.SecretKey file. A default key is delivered together with the product. This key can be replaced by a key generated specifically for each install. (The generate tool is included in the framework). In this way you can ensure complete confidentiality (including from SunGard staff).

How is expiration handled?

There is no automatic key expiration. If desired a new private key can be generated and installed at any time. When a new key is installed the old key is effectively revoked as it cannot be used anymore for existing or new data.

What happens in case the key gets lost?

No secondary recovery key exists, if the primary key is destroyed it should be recovered from backup or a new one generated. A backup of the private key should also be done in a separate location then the database. When restoring both elements (database & key) should be restored together.

What happens if somebody tries to create a new message directly in the database?

This message will not be accepted and will trigger a data seal alert. An application log event is triggered TRAX-SEC-00410. All alerting options (for example email) are available.

What can be done in case the on-site security is breached and the database is tampered with?

Both privileged delete and database repair can be used to bring the database back in service.