Skip to content
Diffbridge

Security

Diffbridge connects to your Salesforce orgs and repositories, so protecting that access comes first. This page describes how the service at https://diffbridge.mokahub.duckdns.org is protected. It's run by an individual developer. Security questions: use the contact form.

Your org credentials

  • Salesforce tokens, git credentials, webhook URLs and integration secrets are encrypted with AES-256-GCM under a key that belongs to your workspace alone. That key is encrypted with a master key kept outside the database, so a database copy on its own reveals nothing.
  • Owners can rotate the workspace key at any time. Deleting a workspace destroys its key, which makes any remaining copies of its secrets unreadable.
  • Connections use OAuth with PKCE where Salesforce supports it; Diffbridge never sees Salesforce passwords.

Controlling access

  • Roles: owner, admin, deployer and viewer, plus per-org access and a minimum role to deploy into each org. Production deployments can require approval.
  • Single sign-on with any SAML identity provider, with enforcement; SCIM provisioning from Okta, Microsoft Entra ID and others.
  • IP allowlists, maximum session length and idle timeouts per workspace.
  • API tokens with an expiry you choose, never able to do more than their owner's role, and recorded in the audit log.
  • Audit log of every change, deployment and support session.

Our access to your data

We don't browse workspaces. Support can only see a workspace when one of its users grants support access, for a limited time; everything support does is recorded in that workspace's audit log as support.

Infrastructure and operations

  • All traffic is encrypted with TLS. The database and file storage aren't reachable from the internet.
  • Backups: the database and stored files are backed up daily to Oracle Cloud Object Storage, separate from the server, with checksums, and kept for 30 days. Every week the newest backup is restored automatically to check that it works, and a failed backup or restore test alerts us by email.
  • Availability: the service's processes are health-checked and restart automatically if they stop. There's no uptime guarantee.
  • Changes are deployed only after an automated test suite passes (type checks, unit, end-to-end and accessibility tests, and an audit for known vulnerabilities in dependencies). Dependency updates are proposed weekly.

Your data, your choices

  • Record backups, archives and their retention are set by your workspace, which also decides who may view or restore record data.
  • Right-to-erasure requests remove a person from every backup and archive, with a hash-only log.
  • Data masking for sandbox seeding keeps personal data out of test orgs.
  • AI assistance is off unless your workspace turns it on.

Certifications

Diffbridge has no security certifications or third-party audits. The providers it uses are on the Sub-processors page.

Reporting a vulnerability

Please report security issues through the contact form ("Contact support"). Include steps to reproduce, and give us reasonable time to fix the issue before disclosing it. Don't access or change other people's data, and don't degrade the service while testing.