Security
A Structured Approach to Data Security and Confidentiality
Retirement plan data is sensitive. This page describes the safeguards we propose for client engagements.
Planned versus implemented
The controls below describe our proposed delivery approach. Specific safeguards are agreed, approved and implemented with each client before any client data is handled. We do not claim third-party certifications or attestations on this site.
Proposed safeguards
How We Propose to Protect Your Data
Individual user accounts
Every team member would work under a named account, so activity can be attributed to a person.
Multi-factor authentication
Multi-factor authentication would be required for access to delivery environments.
Role-based access
Access limited to the people and roles assigned to a given client engagement.
Client-separated workspaces
Each client's data would be kept in a separate workspace to prevent cross-client exposure.
Encryption
Encryption of data in transit and at rest within the delivery environment.
Secure remote access
Remote work performed through controlled, secured access paths.
Audit logging
Logging of access and file activity to support review and accountability.
Controlled file transfers
Defined, secure channels for exchanging files, rather than ad hoc email attachments.
Backup and recovery
Backup and recovery arrangements for delivery environments and working files.
Delivery infrastructure
Cloud Environment
Where a client requires a hosted delivery environment, we propose using Microsoft Azure or Amazon Web Services.
Microsoft Azure
Amazon Web Services
Use of either platform is a proposed option, subject to client approval and implementation. Provider names are not a statement that any specific configuration or certification is in place.
Have Security Questions or Requirements?
Share your security expectations and we will discuss what can be agreed for your engagement.