Reporting a vulnerability or an incident
Reporting a vulnerability
security@lockally.com, for anything you believe is a security weakness in the API, the console, webmail or the mail infrastructure.
Useful to include, in rough order of how much time it saves:
- what an attacker gets, stated plainly
- the exact request or steps, including the
request_idif the API answered - affected host and endpoint
- whether you could reproduce it against your own workspace only, or another’s
A proof of concept against your own workspace is welcome. Please do not test against another customer’s data, and please do not run volumetric or denial-of-service tests against production: they are indistinguishable from the thing they imitate, and they affect people who did not consent.
What happens next
Acknowledgement by a person, not a form. Then triage, a severity, and a fix timeline we will tell you about rather than leave you to guess.
If the finding affects customer data we also run our own breach assessment, which carries a 72 hour customer notification commitment from a confirmed breach, as stated in the DPA.
Reporting an incident you are experiencing
Different thing, different route.
| What you see | Where to go |
|---|---|
| Mail not arriving, API erroring, console down | status.lockally.com first |
| Still broken, and status is clear | support@lockally.com |
| You believe data was exposed | security@lockally.com |
For a support report, the four things that make it findable are the
request_id, the endpoint, the timestamp with a timezone, and whether the
key was live or test. With those, a single request can be located. Without
them it is a search. See Support.
If one of your own keys leaks
Treat it as yours to contain, and do it in this order:
- Revoke the key. Revoking a key takes effect immediately. Do this before working out the blast radius, not after.
- Issue a replacement with the narrowest scopes that work, and deploy it.
- Read the sending record.
GET /v1/messagesshows what was sent, and the audit log shows what else the key did. - Tell us if you believe mail was sent in your name, so the reputation effect can be looked at rather than quietly counted against you.
Removing the key from a repository is not step 1 and is not remediation. Git keeps history, forks keep copies, and public pushes are scraped within seconds of appearing.
What we publish
- Live and historical status on status.lockally.com
- Uptime measured from recorded incidents rather than asserted
- Sub-processors, and the compliance posture including what we do not hold, on the trust page
SOC 2 and ISO 27001 are not held today. Where a questionnaire asks, the honest answer is readiness rather than certification, and we would rather you read that here than discover it in procurement.