Integrations / HR & people ops
Screenata + GustoHow do you automate SOC 2, ISO 27001, and HIPAA personnel evidence from Gusto?
Quick answer
Gusto is where personnel controls are proved: joiner-mover-leaver, screening, and training records. The payroll-derived roster is the population auditors sample when they test whether hiring and termination procedures actually ran. An onboarding or offboarding policy existing on paper is not the control. The control is the recorded event plus the record that it operated for every employee across the audit period. Screenata runs 10 native checks against those records on a schedule and turns each result into signed evidence mapped to the control it satisfies.
Screenata connects to Gusto read-only and runs 10 native checks against your employee records: lifecycle state and payroll-derived rosters. The active roster becomes the ground truth that access reviews and offboarding checks reconcile against. Each finding is a signed, timestamped evidence artifact mapped to SOC 2, HIPAA, and ISO 27001 controls.
10 native checks · read-only · signed evidence
What it proves
Gusto evidence, mapped to controls.
Hires and terminations detected from the roster, triggering training assignment on start and access verification on departure.
Per-event records connecting employment changes to the security actions that must follow them.
The payroll-derived active-employee list reconciled against accounts in identity and SaaS systems.
The authoritative roster access reviews start from: accounts without a matching current employee get flagged.
Employment records available as evidence when auditors sample personnel controls.
Start dates and roles supporting the personnel evidence requests that come with every audit.
Control references are the requirements each evidence area supports, via the shared control catalog. Your auditor decides sufficiency; the artifacts are theirs to verify.
Compliance checks
What Screenata checks on Gusto, and why each matters.
Terminated Employees Deprovisioned
Verifies terminated employees have a termination record with an effective date. Without it the offboarding trail is incomplete and access removal cannot be timed, and an auditor samples leavers to confirm departure was recorded.
Timely Offboarding
Flags non-terminated employees carrying a past termination date. The mismatch means a departure was not finalized and access may still be live, and an auditor checks that offboarding closed out on time.
All Active Employees Have Managers
Confirms active employees have a manager assigned. Reporting chains underpin access approvals and reviews, and an auditor verifies the org structure needed to attribute responsibility is populated.
All Active Employees Have Departments
Verifies active employees are assigned to a department. Access reviews scope by org unit, so missing departments leave populations unclassified, which an auditor relies on when sampling.
All Active Employees Have Current Jobs
Confirms each active employee has a current job with a title. Job titles map workers to expected access, and without them role-based reviews lose the reference point an auditor checks against.
Work Email Recorded for Active Employees
Verifies each active employee has an email on file. Email is the primary identifier that joins the roster to identity provisioning, and an auditor verifies accounts can be reconciled against current employees.
Onboarding Complete for Active Employees
Confirms started employees completed onboarding with a hire date. Incomplete onboarding leaves the provisioning trail open, and an auditor samples hires to confirm records are complete before access.
Worker Classification Recorded
Verifies active workers have an employment type recorded. Access reviews segment employees from contractors, and without a recorded type the population cannot be partitioned cleanly, which an auditor depends on when sampling.
Gusto Admin Count Reasonable
Checks that the number of Gusto admins stays consistent with least privilege. Excess admins over-expose payroll and personnel data, and an auditor verifies privileged access is limited to a narrow, documented group.
Drawn from Screenata’s Gusto check library. Control refs are the requirements each check produces evidence for; your auditor decides sufficiency.
How it connects
Read-only, revocable, yours.
Read-only by construction
OAuth scopes and IAM roles are scoped to read. Vera never gets write access to your systems.
Signed findings
SHA-256 per artifact, RSA/ECDSA signatures, RFC 3161 timestamps. Verifiable without a Screenata account.
Mapped to controls
Each finding lands on the shared control catalog, so one scan satisfies SOC 2, HIPAA, and ISO 27001 at once.
What access does Screenata need to Gusto?
A read-only connection that you authorize and control. Screenata reads roster and lifecycle data for scheduled checks and never receives write access. You can revoke the connection at any time.
How does Gusto help with offboarding evidence?
The integration detects the termination in the roster, checks that access removal followed in your connected identity systems, and records the timeline as signed evidence. A human performs the actual revocation; Vera verifies and chases it.
Does Screenata read compensation data?
The checks use lifecycle and roster data: who is active, who started, who left. Compensation details are not part of any check.
What are the steps to implement SOC 2 with Gusto?
Connect Gusto read-only and authorize the connection. Let the first scan establish a baseline so you can see which records are complete and which are not. Fix what fails: record a termination with an effective date for every leaver and clear anyone still carrying a past termination date, complete onboarding with a hire date for each started employee, fill in the manager, department, current job title, work email, and worker classification fields the roster depends on, and keep the Gusto admin count consistent with least privilege. Collect the passing results as signed evidence on a schedule, so you hold coverage across the whole audit period rather than one snapshot. Then hand the evidence package to an independent auditor. The audit is a separate engagement with a CPA firm; Screenata prepares the evidence and does not issue the report.
What evidence do auditors ask for about onboarding and offboarding?
They sample hires and leavers. For each hire they expect a start date with the training and policy acknowledgments that followed it, and screening completed before access was granted. For each leaver they expect a termination date with the access removal that followed it. Timing is what gets tested, not just existence. A training record dated after the employee already had production access, or an account disabled two weeks after the departure, is a finding even though the record exists.
Do auditors accept evidence Screenata collects from Gusto?
Yes. Every finding is exported as a signed, timestamped artifact, a SHA-256 hash with an RSA or ECDSA signature and an RFC 3161 timestamp, that an auditor verifies outside Screenata with a free CLI. A person reviews and approves the evidence before it reaches the auditor. Screenata collects and signs it; it does not decide the audit result.