Checkr
Background-screening STATUS and dates for your people — who was screened, when it was requested, and whether it came back — as SOC 2 CC1.4 evidence. Report contents and the clear/consider outcome are never read.
What CMDash reads
- Background screening status
Syncs only read from Checkr. Some integrations also support write-back actions on Command and Enterprise plans, such as opening a ticket or deactivating a user.
How you connect
An API key or token you create in the vendor console and enter in CMDash.
Once connected, CMDash syncs it every 4 hours by default. What it finds maps to your controls through rules you install or write.
Where this fits in your frameworks
- CMMC Level 2 — Background screening status feeds Personnel Security
- SOC 2 Type II — Background screening status feeds Control Environment
This is where Checkr’s data is documented as relevant on our framework pages — not a pre-built, automatic control mapping. You configure which controls it maps to inside CMDash.
Also in HR & Workforce
Ready to see your posture?
Start a 30-day free trial of any paid plan — a card is required, and it converts unless you cancel — or sign up for Free with no card at all.