TrustLedger

Security

Vulnerability disclosure and incident response

Customers trust TrustLedger with their private source code. If you believe you have found a security vulnerability in TrustLedger, or you are a customer who suspects a security incident affecting your account, please tell us.

Reporting a vulnerability

Email trustledgerapp.dev@gmail.com. Please include:

  • what you found and where (URL, API endpoint, or component);
  • steps to reproduce, and a proof of concept if you have one;
  • the impact you believe it has;
  • how we can reach you for follow-up questions.

Please do not report security issues through public GitHub issues, social media, or support chat.

What to expect from us

  • An acknowledgement within 3 business days.
  • An initial assessment and severity rating within 10 business days.
  • Updates as we work on a fix, and a note when it is deployed.
  • Credit in our release notes if you would like it, once the issue is fixed.

We do not currently run a paid bug bounty programme.

Safe harbour

We will not pursue legal action against, or ask law enforcement to investigate, anyone who researches and reports a vulnerability in good faith and within these guidelines:

  • only test against accounts and organisations you own or have permission to test;
  • access no more data than needed to demonstrate the issue, and never another customer's source code or findings — stop and report as soon as you can see data that isn't yours;
  • do not degrade the service for others (no denial-of-service or high-volume automated testing);
  • give us a reasonable time to fix the issue — normally up to 90 days — before disclosing it publicly.

Scope

In scope: this web application and its API, the TrustLedger GitHub App, and the scanning pipeline.

Out of scope: social engineering or phishing of our staff or customers; physical attacks; denial-of-service; vulnerabilities in third-party services we use (report those to the vendor); and reports that only point out a missing best practice without a demonstrated security impact.

Security incidents and customer notification

If we confirm a security incident that affects a customer's data, we notify that customer's account administrators by email without undue delay — and within 72 hours of confirming it — with what happened, what data was involved, what we have done, and what they should do. We follow up as our investigation progresses.

Customers who suspect an incident affecting their TrustLedger account should report it to trustledgerapp.dev@gmail.com.

How we protect your data

  • Encryption: HTTPS everywhere (HSTS); data at rest is encrypted by our database provider; two-factor secrets are additionally encrypted (AES-256-GCM) and backup codes are stored only as salted hashes.
  • Tenant isolation: every organisation's data is separated by database row-level security, and an automated check fails our build if a server query is not limited to one organisation.
  • Access control: role-based permissions checked on every API write, SAML single sign-on, two-factor authentication, and SCIM deprovisioning.
  • Audit log: sign-ins, repository changes, data exports, attestations and administrative actions are recorded in a tamper-evident, hash-chained log.
  • Scanning: your code is analysed as text — it is never executed — and the scanner has hard limits so a malicious file cannot crash or stall it.

Machine-readable contact details: /.well-known/security.txt