Skip to main content
Camo Onboarding home

Security

Staffing software security, in plain English

Onboarding means holding Social Security numbers, birth dates and identity documents for people who trusted you with them. Here is how Camo Onboarding protects that information, without the jargon.

Secure staffing onboarding

Encrypted applicant data, scoped access, every view logged

The protections that matter most when you hold Social Security numbers and identity documents.

  • SSNs even database administrators can’t read

    Social Security numbers, dates of birth, names, addresses and I-9 document numbers — more than 100 columns — are encrypted with SQL Server Always Encrypted before they reach the database. Anyone with database access sees only ciphertext.

  • Each agency kept apart, twice

    Every query is limited to one agency by the application and, independently, by row-level security in the database, so a defect in the application alone cannot expose another agency’s records.

  • Access scoped by branch

    Staff see only the branches and functions their role allows. Personal data is masked for everyone but the compliance officer and the tenant administrator.

  • Every view of personal data logged

    A log records which staff member viewed which applicant’s personal information. It is an append-only ledger: nobody, including database administrators, can alter or delete an entry.

  • Identity documents scanned for malware

    Every upload, including photos taken with the camera, lands in quarantine and is scanned for malware. Only files with a clean result are released.

  • No database passwords to steal

    The applications reach the database with managed identities, so there are no database passwords. The encryption key can be used by the application but never exported.

The controls

Every control that protects applicant data

  • Who can sign in

    • Your staff sign in with Microsoft Entra ID accounts. Multi-factor authentication with an authenticator app is required, and legacy sign-in methods are blocked.
    • Applicants sign in with a personal PIN, stored only as an Argon2 one-way hash, or a one-time code sent by email or text.
    • Sending one-time codes is rate-limited to stop abuse.
  • Your data stays yours

    • Every agency’s data is kept separate from every other agency’s.
    • That separation is enforced twice: by the application, and independently by SQL Server row-level security in the database.
  • Encrypted applicant data

    • HTTPS only, with TLS 1.2 or later on the database, storage and web applications. All databases and storage are encrypted at rest.
    • More than 100 columns of personal data are additionally encrypted with SQL Server Always Encrypted, before they reach the database.
    • With Always Encrypted, even database administrators see only ciphertext.
  • Keys

    • Encryption keys are held in Azure Key Vault with soft delete and purge protection turned on.
    • The application can use a key but can never export it.
    • No database passwords are used, so there are none to leak.
  • Off the public internet

    • The database, document storage and key vault have public network access turned off and are reachable only over private connections.
    • The web applications accept traffic only through a protected edge connection, not directly from the internet.
  • Logs you can rely on

    • An access log of who viewed which applicant’s personal information, a full change history of applicant records, and signature audit records.
    • The access and change logs are append-only ledger tables: entries cannot be altered or deleted, and tampering is detectable.
  • Monitoring

    • Microsoft Defender for Cloud monitors the database, storage, Key Vault, containers and Azure management activity.
    • Critical application failures alert by email, then text, then phone call.
  • A plan for incidents

    • A written incident response plan covers detecting, containing and notifying on a data breach.

I-9 data protection

Protecting I-9 data and identity documents

Form I-9 brings in passports, alien registration numbers and photos of identity documents. Here is how each is protected.

  • I-9 identity-document numbers — passport, alien registration and I-94 — are encrypted with Always Encrypted, like Social Security numbers.
  • Uploaded identity documents are quarantined and scanned for malware before anyone can open them.
  • Every staff view of an applicant’s personal information is logged.
  • Every e-signature records the signer, the time, the IP address and the device.
  • Records are kept for the period employment law requires, and applicants cannot erase records the agency must keep.
  • The applicant chooses which acceptable documents to present. Camo Onboarding never requires a particular one.

Hosting and backups

Hosted on Microsoft Azure, in the United States

Backups are kept on the schedule below, with copies in a second Azure region.

Point-in-time restore
7 days
Weekly backups kept
5 weeks
Monthly backups kept
12 months
Deleted documents recoverable for
30 days

How changes ship

Tested before it reaches you

  • Every change passes more than 2,000 automated tests, including tests that hold the security rules and the I-9 rules in place.

  • The build fails on any dependency with a known vulnerability.

  • Every change runs in a separate staging environment first, before it reaches the system your branches use.

  • Releasing to the live system is a manual step run by a person, and the source-code host holds no credentials for it.

Questions

Staffing software security questions

Can database administrators read applicants’ Social Security numbers?
No. Social Security numbers and more than 100 other columns of personal data are encrypted with SQL Server Always Encrypted before they reach the database, so database administrators and anyone with database access see only ciphertext.
Can another agency see our applicants?
No. Every query is limited to one agency by the application and, independently, by row-level security in the database, so a defect in the application alone cannot expose another agency’s records.
Who at our agency can see an applicant’s personal data?
Staff see only the branches and functions their role allows. Personal data is masked for everyone but the compliance officer and the tenant administrator, and every view of an applicant’s personal information is logged.
How are uploaded identity documents protected?
Every upload, including camera photos, is quarantined and scanned for malware, and only files with a clean result are released. Documents are encrypted at rest and stored off the public internet.
How do applicants sign in without a password?
With a personal PIN, stored only as an Argon2 one-way hash, or a one-time code sent by email or text. Sending codes is rate-limited.
Where is the data hosted, and how is it backed up?
On Microsoft Azure in the United States. The database can be restored to any point in the last 7 days; weekly backups are kept 5 weeks and monthly backups 12 months, with copies in a second Azure region. Deleted documents can be recovered for 30 days.

Questions from your IT or compliance team?

Bring them to the demo. We will walk through how each of these controls works.