Treasury Software practices the concept of 'Defense in Depth' (also known as Castle Approach), in which the system has multiple layers of controls.
--Database encryption using AES-256
--Encrypt within QuickBooks qbw
--SQL Server security
--Full Audit Trail
--Segregation of Duties
--SSH-FTP encrypted transmission
Many of the options are available in the Settings tab.
There are two components to Treasury Software access control:
Server based security - 'Gold Standard'
Server-based security is Microsoft SQL Server based and is first addressed during account creation and setup. It centers around the user's Windows or SQL Server login ID and the membership of the groups/roles that the individual belongs to.
Based on the membership, the user will have access to or be denied to the various SQL Server databases. There is a one to one relationship between databases and accounts.
SQL Server is maintained according to your corporate security policies outside of Treasury Software by your database administrator (DBA) with Microsoft's SQL Server Management Studio.
Treasury Software products on SQL Server, with SQL Server security maintained - is the strongest form of security we can deliver. SQL Server is required by many Government agencies and according to corporate bank policy. SQL Server security is often viewed as the 'Gold Standard' of security.
Treasury Software also provides two levels of client based security:
--user authentication - simple access to software
--feature-level access - segregation of duties - requires SQL Server with and Treasury Software Enterprise license
While we are proud of our client-based security features - if only client-based security is implemented - it will merely be an inconvenience to those seeking to commit fraud.
Security is only as effective as the weakest link in the chain.
Locking down the 'front door' (client), only to leave the 'back door' (server-data) open is not an ideal security model.
Adding to security concerns - The input to Treasury Software is an unprotected file - typically a spreadsheet, and the output for ACH Universal and Positive Pay is an ASCII file.
Client workstation access control
For those environments requiring high security, we highly recommend the use of Windows Operating System and Network Operating System based features, to limit physical and remote access to the Treasury Software client.