In an effort to ensure your data is secure in interactions with AMS Services, we have employed internal processes to “sanitize” sensitive data in Phoenix, PhoenixDirect and PremiumBill databases.  For example, we change any Social Security, Tax Payer ID and account/routing number data to all ones, and modify sensitive dates, such as birthdates, so they cannot be extrapolated from the new dates.

However, we would like to establish protocol, and recommended practices for securing files exchanged with AMS Services.  There are many potential methods available, such as PGP or other key based encryption, multi-phase encryption methods, etc.

There are also non-encryption methods available to secure data, such as creating SQL Server backups with a password.  While this does not encrypt data, it prevents parties not privy to the password from accessing the backup file.  This option is not available through the SS GUI’s available at various levels, but only via script backup.  Below is an example of how the syntax would appear for SS:

backup database database_name to disk='c:\database_backup_name.bak' with mediapassword = 'special_password'

What methods does your company employ when exchanging data with other vendors?

What methods would you like to use in conjunction with AMS Services? 

We are aware that over recent years, with the influence of Sarbanes-Oxley, your organization is under heavier scrutiny with regard to data security.  We have internal requirements to do everything we can to help you maintain those responsibilities, so any feedback would be appreciated. 

It would be helpful to know the following details:

• your company
• methods you use/prefer to ensure protection of your data and
• how we could coordinate an effective and secure transfer of information in the future

Please login or register and provide any thoughts or details.  Thanks!  We will be compiling  recommended solutions and posting them on the AMS Carrier Community site!