Use case · SaaS, HR & payroll
Protecting your customers’ employee data on shared platforms
HR and payroll platforms hold salaries, bank details and ID numbers for thousands of employers. CCL keeps that data sealed across shared infrastructure and support tools.
- Salaries and payslips
- Bank details
- National insurance and tax IDs
- Home addresses and personal details
The challenge
Where the data goes today.
SaaS platforms, especially in HR and payroll, hold sensitive personal data on behalf of their customers, who in turn hold it on behalf of their employees. That is two layers of trust, and both are placed in your platform.
Shared infrastructure, support tooling, integrations and analytics mean the data is readable in far more places than the payroll engine that actually needs it.
Where it’s readable
- Employee self-service forms
- Shared services and queues serving many customers at once
- Support and impersonation tools used by your own staff
- Integrations with banks, pension and benefits providers
- Logs, analytics and data warehouse exports
How CCL applies
The same journey, sealed where it doesn’t need to be read.
- Self-serviceBrowser SDK
Bank details and ID numbers are sealed in the employee’s browser before they are sent.
- Platform edgeGateway
Requests move through shared infrastructure without it reading the data.
- Payroll engineBroker
Only the payroll service you authorise opens the fields it needs to run payroll.
- Employee recordsProtected Storage
Records are sealed again at rest, including in backups and exports.
What changes
The outcome.
Support without exposure
Staff tools can work with records without seeing salaries or bank details they don’t need.
A stronger security answer
A clear architecture to show enterprise customers in security questionnaires and due diligence.
Contained incidents
A compromised service, log store or integration does not automatically expose employee data.
CCL is in development. This use case describes how the v1.0 design is intended to apply.
Related insights
Where your customers' data is exposed today
Encrypted in transit, encrypted at rest. Follow one piece of customer data through your stack and count how often it is neither.
- Data exposure
- Architecture
The breach that starts somewhere boring
Serious incidents rarely begin with a movie-style hack. They begin with a debug log, a forgotten test database or an over-privileged service account.
- Breaches
- Containment
Trust less, prove more
Every system you run asks to be trusted. The strongest security removes that need wherever it can, and makes the rest visible.
- Principles
- Trust
Contact
Get in touch.
Whether you’re exploring how to protect your clients’ data, interested in CCL, or want to work with us, we’d like to hear from you.