GRC Oversight

Salesforce (Security & Access)

Collect user roster, profile/permission-set assignments, and login-history evidence as read-only access-review compliance signal through the Salesforce REST API. Scoped to security/identity evidence only -- not sales, marketing, or customer-record data.

Connect Salesforce (Security & Access)All integrations
Identity · Access
Tier 2 generic template — runs on the HTTP / REST endpoint connector
Evidence coverage

What this connector audits

Checks this connector runs once it's connected. This is the full list; we don't claim coverage beyond what's implemented.

  • Read-only API inventory endpoint checks
  • Evidence assets generated through the generic HTTP connector
Read-only calls

Endpoints this template queries

The exact Salesforce (Security & Access) API endpoints called once connected. All read-only GET requests unless noted.

  • GET/query?q=SELECT+Id,Name,Username,IsActive,ProfileId+FROM+User
  • GET/query?q=SELECT+Id,Name+FROM+Profile
  • GET/query?q=SELECT+Id,Name+FROM+PermissionSet
  • GET/query?q=SELECT+Id,UserId,LoginTime,Status+FROM+LoginHistory+ORDER+BY+LoginTime+DESC+LIMIT+50
Least privilege

What we need

Field labels only. We never show secret values here. Credentials are encrypted at rest and used only to run the checks above.

Required

  • Base URL(prefilled: https://<your-instance>.my.salesforce.com/services/data/v59.0)
  • Endpoints (JSON)(prefilled: [ { "id": "users", "name": "Active users", "path": "/query?q=SELECT+Id,Name,Username,IsActive,ProfileId+FROM+User" }, { "id": "profiles", "name": "Profiles", "path": "/query?q=SELECT+Id,Name+FROM+Profile" }, { "id": "permission-sets", "name": "Permission sets", "path": "/query?q=SELECT+Id,Name+FROM+PermissionSet" }, { "id": "login-history", "name": "Recent login history", "path": "/query?q=SELECT+Id,UserId,LoginTime,Status+FROM+LoginHistory+ORDER+BY+LoginTime+DESC+LIMIT+50" } ])

Optional

  • Auth header name(prefilled: Authorization)
  • Auth header value(secret credential)
Where this evidence goes

Which frameworks this evidence supports

Salesforce (Security & Access) evidence feeds into controls for any framework you run that requires this check type; the same synced evidence can satisfy more than one framework's requirements instead of being collected per audit.

Don't see your system?

Tell us what you use and what it needs to prove. We'll follow up about adding a connector.

Wire in Salesforce (Security & Access) evidence

Get a guided demo, or start by scanning any domain for free.

Connect Salesforce (Security & Access)Browse all integrations