Pre-audit pass rate
Many teams assume Salesforce is compliant out of the box. Salesforce secures the platform, but your Profiles, Permission Sets and sharing rules are on you. The audit shows pass or fail for each control.
A Salesforce compliance audit checks your live setup against the controls your auditor tests, such as SOC 2 and ISO 27001. You get an evidence export to hand over.
A Salesforce compliance audit uses controls from SOC 2 (System and Organization Controls 2, a security audit report), ISO 27001 (the international security standard), GDPR (General Data Protection Regulation, the EU privacy law), HIPAA (Health Insurance Portability and Accountability Act, the US health data law) and NIST CSF (the US Cybersecurity Framework).
Clientell AI, the AI agent for Salesforce admins, scans your org, drafts each fix and asks before it changes anything in production.
Four patterns this audit is built to find. Figures are examples.
Many teams assume Salesforce is compliant out of the box. Salesforce secures the platform, but your Profiles, Permission Sets and sharing rules are on you. The audit shows pass or fail for each control.
SOC 2 and ISO 27001 access controls often fail for the same reason. The usual causes are profiles with Modify All Data, integration users with admin rights and stale permission sets.
A SOC 2 Type II report comes from an outside audit firm. Fixing gaps first, such as a user with View All Data who left last year, means fewer findings during the real audit.
For each failing control, the audit builds evidence from the live org, such as the PermissionSet record or the LoginHistory rows behind it. No more waiting two days while the admin checks. Open the control and export it.
Click any framework to see its top failing controls. The numbers below are sample data, not a real org.
Each control mapped to live Salesforce config. Auditor-ready evidence export.
See my compliance postureFive frameworks plus continuous monitoring.
SOC 2 groups its controls into Common Criteria. The audit maps each one to your Salesforce setup. Logical access (CC6.1) maps to your Profile and PermissionSetAssignment records. System monitoring (CC7.2) maps to the SetupAuditTrail object (Setup > Security > View Setup Audit Trail). Evidence is collected per control.
Annex A is the list of controls in the standard. The audit maps the ones that touch Salesforce. Most are about access control (who holds which Permission Set), asset management (Connected Apps and packages), suppliers and incident handling.
The audit covers erasure, data protection by design, records of processing and security of processing. Each maps to a Salesforce setting, such as field-level security on Contact.Email (Setup > Object Manager > Contact > Fields) or Shield Platform Encryption on a field.
The rule sets three kinds of safeguards: administrative, physical and technical. The audit focuses on the technical ones: access control (unique user IDs, session timeout), audit controls (SetupAuditTrail, FieldHistoryArchive), integrity and transmission security (TLS). Physical safeguards matter less for a cloud service.
The framework has six functions: Govern, Identify, Protect, Detect, Respond and Recover. Each function maps to Salesforce settings, such as Login Hours, IP ranges and Transaction Security policies. It suits orgs that use the framework for cyber governance.
Most compliance audits are annual snapshots. Clientell AI checks your controls again and again. When a setting drifts and breaks a control, you see it then, not at the next audit.
| Framework | Built from | Best for | Auditor |
|---|---|---|---|
| SOC 2 Type II | Trust Services Criteria | Customer security questionnaires, B2B SaaS sales, enterprise procurement. | An independent CPA firm. |
| ISO 27001:2022 | Annex A | International compliance, European customers, ISMS certification. | Accredited ISO certification body. |
| GDPR | Articles | EU data subject regulation, right-to-erasure, lawful basis tracking. | Your data protection officer (DPO) or an EU regulator. |
| HIPAA Security Rule | Security Rule | Healthcare orgs, BAA signers and PHI handling. | The HHS Office for Civil Rights or a HIPAA auditor. |
| NIST CSF 2.0 | Six functions | Federal contracts, cyber governance framework, mature security program. | Your CISO (chief information security officer) or an outside assessor. |
If any of these apply, run the audit first.
Building access reviews after the fact is slow. The audit lists who holds which Profile and PermissionSet (Setup > Users > Permission Sets), and who has the ModifyAllData or AuthorApex permission. You can export a review in the format SOC 2 auditors ask for.
Financial services (SOX, the Sarbanes-Oxley US law on financial controls, and PCI, the card payment standard), healthcare, education (FERPA, the US student privacy law) and federal work (FedRAMP, the US cloud security program) all expect mapped controls. The audit produces that mapping.
Questionnaires ask for your SOC 2 status, your ISO 27001 alignment and proof for specific controls. Without an audit, answers stay vague. With one, you can export the proof, such as your password policy (Setup > Security > Password Policies), MFA (multi-factor authentication) setting and session timeout.
The GDPR gives people the right to have their personal data erased. First you must find where it lives in your org. The audit maps the objects and fields that hold personal data, such as Contact.Email, Lead.Phone and custom fields of the Email or Phone type.
Agentforce is Salesforce's AI agent product. AI agents raise new questions: who can reach which data, how access is logged and what limits agent actions. The audit baselines the agent user's Permission Sets, sharing and logging before the agent goes live.
Five deliverables, made for a CISO, a compliance officer and an auditor.
SOC 2, ISO 27001, GDPR, HIPAA and NIST CSF dashboards show pass, partial or fail for each control. They are filterable by object or Permission Set, exportable and show the owner.
For each control, you get the live Salesforce setting that meets it. That includes Profile and PermissionSet exports and SetupAuditTrail excerpts. The format suits SOC 2 evidence collection.
When a setting drift breaks a control, you get a Slack or email alert. Examples: someone adds a Profile with ModifyAllData, or someone grants ViewAllData to an integration user.
A one-page summary of your position across all frameworks, with pass rates and the top failing controls. A CFO, a CISO or the board can read it.
Every failing control comes with a proposed fix, an owner role, an effort estimate and its dependencies. Sort by severity and export to Jira.
What CISOs and compliance teams ask before they start.
It maps your Salesforce configuration to the controls in SOC 2, ISO 27001, GDPR, HIPAA and NIST CSF. Each control shows as pass, fail or partial. Each finding comes with auditor-ready evidence.
No. Salesforce secures the platform and publishes its own audit reports on its Trust site. Your setup decides whether your org meets the controls. That means who holds Modify All Data and whether SetupAuditTrail and LoginHistory are reviewed.
Shield adds Event Monitoring, Platform Encryption and Field Audit Trail. Those are tools. The audit checks whether your setup, with or without Shield, meets each control.
No. A SOC 2 Type II report must come from an independent audit firm. This is the pre-audit. It finds gaps before the auditor does.
Yes. For every control, you get the live Salesforce setting that meets it or fails it. That includes PermissionSetAssignment exports, LoginHistory excerpts and user permission matrices. You hand the export to the auditor without rewriting it.
You can run it during the 14-day free trial, with no card needed.
Salesforce signs a BAA (Business Associate Agreement) for covered services. The BAA covers the platform. The audit checks your own setup against the technical safeguards in the Security Rule.
As often as you can. SOC 2 is an annual report, but configuration drift happens daily as admins add profiles and contractors get permissions. Continuous checks catch drift early. A yearly audit finds it months later.
The five frameworks cover most needs. For financial services, we map to the access and change controls inside them (the SOX equivalents). FedRAMP authorization, FISMA and custom regulator frameworks are not covered yet.
Drata and Vanta are compliance platforms that cover your whole company. This audit covers the Salesforce slice, with deeper control mapping. Use it beside them, or on its own if you have no platform yet.
Audits and services for compliance, security, and audit-prep teams.
Most compliance findings trace back to access control. Permissions Audit is the deep-dive.
Read moreAuditSOC 2 and ISO 27001 expect you to show who changed what. Change Intelligence provides it.
Read moreServiceA broader org audit, with compliance on its own tab.
Read moreAuditAI agents raise new compliance questions. Score your readiness before launch.
Read moreAuditGDPR accuracy and HIPAA integrity controls trace back to data quality.
Read moreGuideA phased implementation framework with compliance milestones.
Read moreProductCompliance-safe deployments with audit trail and rollback.
Read moreServiceContinuous compliance monitoring instead of annual-only audits.
Read moreTrust + security posture
CC6.1-CC6.8 (access controls) start with permissions. Audit before the SOC 2 review.
CC7.2 (monitoring) requires a complete SetupAuditTrail. Decode it here.
GDPR Article 5(1)(d) requires data accuracy. Score completeness across objects.
Departed-employee license retention is a recurring SOC 2 finding.
Last reviewed October 2026
SOC 2. ISO 27001. GDPR. HIPAA. NIST CSF. Evidence your auditor can use. Continuous monitoring. Free for 14 days.
14-day free trial · No credit card required