Technology & Security.

Explore Workzoom’s architecture, hosting and security practices.

The security posture, documented.

Hosting

Canadian or US data residency.

Hosted on Amazon Web Services data centers. Hosting region is agreed at onboarding. Confirm processing locations and transfer requirements with Workzoom during your security review.

  • CanadaAWS data centers
  • United StatesAWS data centers

Isolation

Isolated per client.

Every client has their own database schema and document repository instance.

Encryption

Encrypted in transit and at rest.

  • AES-256At rest
  • TLS 1.2In transit, over 2048-bit certificates

Replication

Multi-AZ

Real-time replication across physically separate AWS availability zones.

  1. Primary
  2. Replica
  3. Backup vault

Vulnerability response

4 hr

Response SLA for Critical vulnerabilities.

See the vulnerability SLA

  • Critical, CVSS 9.0+4 hours or less
  • High, 7.0 to 8.91 business day or less
  • Medium, 4.0 to 6.95 business days or less
  • Low, 0.1 to 3.9Next regular release cycle

Hosting assurance

13

AWS assurance references in our whitepaper.

Audit reports, certifications and frameworks. Scope depends on the AWS service and region. They do not certify Workzoom's application. See the list.

  • SOC 1
  • SOC 2
  • SOC 3
  • ISO 27001
  • ISO 27017
  • ISO 27018
  • ISO 9001
  • PCI DSS Level 1
  • FedRAMP
  • HITRUST CSF
  • NIST
  • FIPS
  • CSA

For your IT team

The Security Whitepaper.

Architecture, hosting, encryption, replication and vulnerability response in one PDF.

Hosting and certifications

AWS data centers. Canadian or US residency.

Powered by AWS Cloud Computing

  • SOC 1Financial reporting controls
  • SOC 2Trust services criteria
  • SOC 3Public attestation
  • ISO 27001Information security management
  • ISO 27017Cloud-specific security
  • ISO 27018Cloud personal-data protection
  • ISO 9001Quality management
  • PCI DSS Level 1Payment card data security
  • FedRAMPUS federal cloud authorization
  • HITRUST CSFHealthcare information security
  • NISTUS cybersecurity framework
  • FIPSUS federal cryptographic standards
  • CSACloud Security Alliance

These AWS assurance references are listed in Workzoom's whitepaper. They do not certify Workzoom's application.

Scope and documentation

Workzoom is hosted on Amazon Web Services data centers in Canada and the United States. Clients choose data residency at onboarding.

They include audit reports, certifications and frameworks, with scope that varies by service and region. Request current AWS documentation, applicable scope and sharing terms via security@workzoom.com.

Workzoom uses AWS Global Accelerators and Edge Computing to route traffic to endpoints nearest each client.

Amazon Web Services, AWS, and the Powered by AWS logo are trademarks of Amazon.com, Inc. or its affiliates.

Client ADB schema
Doc repository
Your orgDB schema
Doc repository
Client CDB schema
Doc repository
Shared application layer · Java on Tomcat

System architecture

Multi-tier Java, multi-threaded, isolated per client.

Workzoom is a proprietary platform written in Java on Tomcat web servers running on hardened Linux. Persistent data lives in MySQL. Documents and media live in MongoDB.

Every client has their own database schema and their own document repository instance, isolated from every other client.

More on the architecture

Per-client isolation

Application software, web resources, meta-data, and common content are held outside the per-client databases. Every byte of client-specific data sits inside an isolated instance. Backup, recovery, and access policies all attach at the per-client level.

Self-healing cluster

Intelligent clustering uses auto-scaling and self-healing across multiple AWS Availability Zones. No single data-center incident takes the application down. Refreshable memory and file caches maintain top performance under load.

Private Data Cloud

Clients requiring physical isolation subscribe to the Workzoom Private Data Cloud: a dedicated database instance with separate encryption keys and a VPN-gated private network. No other client data resides on the server.

Network edge

Traffic is routed to the AWS endpoint nearest the client via AWS Global Accelerator and Edge Computing. Minimal latency for clients in Canada, the United States, the Caribbean, and the United Kingdom, without compromising data residency.

PrimaryAWS AZ ReplicaReal-time Backup vaultDaily, encrypted Multi-AZ WORM

Replication, backup, recovery

Physically separate facilities. 24-hour maximum data exposure.

Real-time replication. Client data replicates in real time across AWS Availability Zones, which are physically separate facilities with independent power, cooling, and networking, to mitigate environmental and infrastructure failures.

Backups and recovery

Daily encrypted backups. Backups run daily into AWS Backup vaults, held redundantly across multiple availability zones in the same region as the primary. More frequent backups are available per client.

Configuration as code. Application and infrastructure configuration lives in version-controlled Kubernetes manifests, so an environment is rebuilt from source rather than restored from a server image.

Recovery posture. On failure, clients switch to the replication environment. Intelligent clustering across AZs means no downtime from a single-data-center incident.

Encryption, authentication, SSO

AES-256 at rest. TLS 1.2 in transit. Federated SSO via SAML 2.0.

All client data at rest is encrypted with AES-256. In the Private Data Cloud option, encryption keys are managed in a separate key management server with no shared key material across clients.

All data in transit is encrypted using 128-bit-plus TLS 1.2 over TCP/IP with a 2048-bit certificate and strong cipher suites. Servers refuse to acknowledge connections from browsers or operating systems that do not support TLS 1.2.

Passwords are encrypted with the PBKDF2WithHmacSHA1 algorithm, combining salted hashing with key stretching. Protection against dictionary, rainbow-table, and brute-force attacks. Policy configurable per client.

Federated authentication via SAML 2.0. Native integrations with Microsoft Entra ID (formerly Azure AD), OneLogin, and Okta. Other SAML 2.0 identity providers may be supported; confirm compatibility and configuration with Workzoom. See the SSO configuration guide.

  • WhoCan log in, with start and end dates
  • SubjectsWhat they can access
  • TasksWhat they can perform
  • DataView, add, update, or remove

Access management and logging

Role-based access. Every change dated and attributed.

Workzoom controls four dimensions of access independently.

How roles work

Role-based access control, down to the field

Workzoom is primarily role-based. Because the platform is built around HR, every user has a pre-defined role and responsibilities built into their job and position definition. The same role definition drives security: a user's role defines exactly what data they can view, add, update, or remove. When an exception is required, security can be applied at the individual user or group level, down to a single field if necessary.

Recorded for every login, action, or change

  • The user
  • The process
  • The timestamp
  • The IP address
  • The original value
  • The new value

Activity logging with full attribution.

All logins and session activities are logged. For every login, action, or change, the application records the user, the process, the timestamp, the IP address, the original value, and the new value.

Workzoom staff access to client data

Access to client data is restricted to individuals who support the client. Every Workzoom employee signs a non-disclosure agreement and a code of ethics and is subject to background and criminal record checks as part of the new-hire process.

All Workzoom servers are isolated on their own VPC. Access to Workzoom servers is available only to a very limited set of authorized personnel, only through a VPN tunnel with TLS 1.2 ciphers and SHA-256 key exchange, with AES-256 encryption of all data inside the tunnel. Administrator access to infrastructure uses rotating access tokens. All VPN connection data is logged, and alerts fire on failed authentication attempts. All client data is securely removed from the cloud and from internal computers at the end of every engagement.

Security framework

Minimal attack surface. Least privilege. SELinux-hardened.

Workzoom servers reside in Virtual Private Clouds with security groups that close every external TCP and UDP port beyond HTTPS. All communication between Workzoom services is limited to within the secure VPC.

Root access on Workzoom servers is disabled. Elevated user privileges are strictly limited. All sudo-level commands are logged and monitored using industry-standard tools.

Privilege separation is enforced via server hardening with SELinux. Process isolation ensures users and applications can only operate in areas absolutely necessary. Backup tools, for example, are only granted read-only privileges to the relevant databases.

Vulnerability scanning, penetration testing, hardware/software/application firewalls, comprehensive monitoring, logging, auditing, event management, and virus, trojan, and malware protection.

See Workzoom in 30 minutes.

Real product, real questions, no slides. Starts at $4 per employee per month, CAD or USD, with no initial setup fees.

Workzoom employee dashboard with tasks, profile and time off

Vulnerability response SLA

Documented response and resolution times by CVSS 3.1 severity.

How the SLA is measured

Workzoom uses the Common Vulnerability Scoring System (CVSS) version 3.1 to rate potential vulnerabilities. The SLA below applies from the moment Workzoom becomes aware of a vulnerability in the Workzoom platform, or from the moment a third-party vendor confirms a fix for an upstream component.

  • CVSS 9.0+

    Critical

    Response time

    4 hours or less

    Resolution time

    80% resolved within 1 business day

  • CVSS 7.0–8.9

    High

    Response time

    1 business day or less

    Resolution time

    80% resolved within 5 business days

  • CVSS 4.0–6.9

    Medium

    Response time

    5 business days or less

    Resolution time

    80% resolved within 25 business days

  • CVSS 0.1–3.9

    Low

    Response time

    Next regular release cycle

    Resolution time

    Bundled with the next scheduled release

Incident response

Seven-step procedure, 24/7 monitoring.

How incidents are detected

Advanced monitoring is in place at the hardware, database, and application level. Hardware is monitored for data integrity, resource consumption, and network failure. Real-time replication and application availability are monitored 24/7, with alerts routed immediately to technical personnel. The procedure below executes on every confirmed security or privacy incident.

Security and senior management are informed within minutes of detection.

A report is started and tracked through resolution.

The Information Security Team assesses how far and how serious the incident is.

Affected clients are emailed, scaled to the scope and severity.

Immediate action to contain, restore availability, and prevent recurrence.

Root-cause analysis and risk mitigation are documented and applied.

If data is lost, clients get individual recovery plans.

  • 14 daysAdvance notice of any testing
  • Signed NDAFrom all parties, before testing begins
  • 7 daysUn-redacted results after testing completion

Client penetration tests

Clients can run their own pen tests. Here is the policy.

Clients may conduct penetration tests and vulnerability assessments against Workzoom, either internally or through a third-party security firm, with Workzoom's prior approval.

The full policy
  • 14 days advance notice of any testing, with a detailed outline of testing procedures and schedule.
  • Signed NDA from all parties involved before testing begins.
  • Un-redacted results related to Workzoom technologies provided within 7 days of testing completion.
  • Workzoom reserves the right to restrict testing scope, timing, methodology, or supplier where necessary to protect other clients in the multi-tenant environment.

Submit a pen test request to security@workzoom.com with the testing window, scope, and the firm performing the assessment.

  • WeeklyA server restart of approximately five minutes
  • Two monthsA new release ships approximately this often
  • QuarterlyUpdates run off-hours over a weekend

Maintenance and release cycle

Most maintenance runs in the background. ~5 minutes weekly.

Weekly maintenance: a server restart of approximately five minutes. Most maintenance runs in the background with no client-visible impact.

Releases, sandbox and patching

Releases: a new Workzoom release ships approximately every two months. The release is staged in the background and activated after the regular server restart. Quarterly updates run off-hours over a weekend with minimal downtime.

Major releases: upgrades to a new major release are planned events. Workzoom provides clients a window of opportunity that suits their business cycle (avoiding active payroll runs, for example). All clients must be on the current release or the immediately previous release.

Sandbox: clients on a secondary Sandbox environment can preview an upcoming release for their own testing before production cutover.

Patching: OS-level and third-party application vulnerabilities deemed high-risk are tested and applied within timeframes appropriate to the assessed risk. All updates are tested on internal development and sandbox servers before production deployment.

For your security review team

Workzoom Architecture & Security Whitepaper

8-page PDF. Full architecture, hosting, certifications, encryption, replication, security framework, access management, vulnerability response, incident procedure, maintenance cycle, and pen-test policy. Cleared for distribution to your IT and security review teams without further NDA.

Download the PDF

Workzoom security: common questions.

Workzoom client data is hosted on Amazon Web Services data centers in Canada or the United States, chosen at onboarding. Canadian clients can elect the AWS Canada (Central) region; US clients can elect a US region. Confirm the agreed hosting region, backup locations, subprocessors and any cross-border processing requirements with Workzoom as part of your security review.
Every Workzoom client has its own database schema and its own document repository instance. Application software, web resources, meta-data, and common content sit outside the per-client databases and are shared. Client-specific data is isolated end to end. For clients that require physical isolation, Workzoom offers a Private Data Cloud subscription that provides a dedicated database instance with separate encryption keys held in a key management server.
Data at rest is encrypted with AES-256. Data in transit is encrypted with TLS 1.2 over 2048-bit certificates with strong cipher suites. Passwords are encrypted with the PBKDF2WithHmacSHA1 algorithm using salted hashing with key stretching. Workzoom servers refuse to acknowledge connection requests from browsers or operating systems that do not support TLS 1.2.
Yes. Workzoom supports federated authentication via SAML 2.0. Native integrations include Microsoft Entra ID (formerly Azure AD), OneLogin, and Okta. Other SAML 2.0 identity providers may be supported; confirm compatibility and configuration with Workzoom.
Yes, with prior approval. The policy requires 14 days advance notice, a detailed outline of testing procedures and schedule, a signed NDA from all parties, and un-redacted results related to Workzoom technologies within 7 days of completion. Submit requests to security@workzoom.com. Workzoom reserves the right to restrict scope, timing, or methodology to protect other clients in the multi-tenant environment.
Workzoom uses CVSS 3.1 to score vulnerabilities and commits to documented response and resolution times. Critical (9.0+): 4 hours or less to respond, 80% resolved within 1 business day. High (7.0–8.9): 1 business day to respond, 80% resolved within 5 business days. Medium (4.0–6.9): 5 business days to respond, 80% resolved within 25 business days. Low (0.1–3.9): bundled with the next scheduled release.
Weekly maintenance is approximately a 5-minute server restart. Most maintenance runs in the background. New releases ship roughly every two months and are activated after the regular weekly restart. Major releases are scheduled events that avoid critical client business cycles (active payroll runs, fiscal close). In the event of a major incident, recovery time is normally 5 minutes to 8 hours and maximum data exposure is 24 hours.
Workzoom is hosted on AWS infrastructure, which holds SOC 1, SOC 2, and SOC 3 audit attestations. These certifications belong to AWS and apply to the hosting environment, not to Workzoom directly. AWS publishes the underlying SOC reports under its Customer Compliance Program. Request current assurance documentation and its sharing terms from Workzoom. Application controls and AWS infrastructure attestations should be reviewed separately. Email security@workzoom.com with your due-diligence request.

Security review

Need more for your security review?

Request current security documentation and discuss the requirements in your procurement questionnaire. Questions in writing? Email security@workzoom.com.

Loading available times.

Better work, in your inbox.

Fresh ideas for HR and payroll. Every week.

Better work, in your inbox.

Practical ideas for HR, payroll and workforce teams.