B2B SaaS
Compliance dashboard UX: designing a SOC 2 tool security leads will connect
The hardest part of a compliance product is not the dashboard. It is getting a security lead to trust it with access. Five decisions from designing Clearpass.
· 5 min read
Compliance tools promise to make audits painless, and most of them look the same: a score, a long sidebar and a wall of controls. The real design problem sits before the dashboard. A security lead has to connect the tool to GitHub, AWS and Google Workspace, and every connection is a risk they are personally accountable for.
I designed Clearpass, a concept SOC 2 readiness platform for startups with 10 to 50 people. The business problem I designed against: accounts that stall below 50% readiness never book their audit, and churn before renewal. Here are the five decisions that shaped it.
1. Read by default, write only by consent
This was the riskiest decision. Integrations connect read-only. When a control fails, Clearpass prepares the fix but does not run it. It lists exactly what will change, an Admin approves one write scoped to that change, then the control is re-tested and the approval is logged as evidence.
I rejected auto-remediation with standing write access. It is faster, but a wrong automatic fix in GitHub or AWS costs far more than a slow one, and no security lead I would want as a customer would connect it. The trade-off is real: fixes take a few extra minutes. The gain is a product people actually connect.
2. Top navigation, not a 14-item sidebar
Security leads spend their day in two places: the readiness score and the list of controls. A top bar gives the controls table the full width, and the detail panel opens beside it, so nobody loses their place. The long sidebar most compliance tools use puts every module on equal footing, when the daily job is mostly two screens.
3. One score, and every point explained
A readiness ring is the headline, but every point links to a control you can open. Switching between frameworks re-scores everything instantly. I rejected a separate headline score per framework: controls are shared, so three numbers moving at once read as noise instead of progress.
4. Approvals that expire, and admin access that needs two people
Access requests default to the shortest sensible window. Admin access needs a second approver and ends after four hours. Every decision is logged. A warning on risky requests is not enough. Compliance leads expect separation of duties, and the product should enforce it rather than suggest it.
5. Some alerts cannot be snoozed
Snooze is useful for noise and dangerous for real risk. Critical alerts, like former employees who still have access to production, stay visible until someone resolves them. Everything else can wait.
For an auditor, the log is the product
Auditors do not care how nice the dashboard looks. They want evidence: who approved what, when, and what changed. So the activity log is designed as a first-class surface, readable without the rest of the product, with a read-only Auditor role that sees evidence without being able to change anything.
Design for when it goes wrong
- An integration disconnects: say what stopped being monitored and since when.
- A fix fails halfway: show what was applied, what was not, and roll back or retry safely.
- Write permission is declined: the manual steps appear instead of a dead end.
- Evidence goes stale: flag it before the auditor does.
- No second approver in time: the request expires cleanly and the requester knows why.
Every status is written in words, not only shown in colour, and the product targets WCAG 2.2 AA with keyboard-first navigation.
How I would measure it
Clearpass is a concept, so these are targets, not results. The north star is 80% of new accounts past 50% readiness within 30 days, with a median of nine weeks to audit-ready. If people will not grant access, none of that happens, which is why the access model came before any screen.
Related work