Multi-factor authentication
Sign-in supports multi-factor authentication, and an organisation can require it of everyone. Sensitive actions, such as creating API keys or configuring webhooks, ask for it again at the moment they happen.
Security
Kumry keeps your organisation's data behind strong sign-in and role checks, and records who changed what so you can see it for yourself. Here are the controls in place today.
Sign-in supports multi-factor authentication, and an organisation can require it of everyone. Sensitive actions, such as creating API keys or configuring webhooks, ask for it again at the moment they happen.
Each request is tied to one organisation and checked against that person’s role in it. Owners, admins, editors and viewers see and do different things.
Kumry is served over HTTPS. Connections between your browser and Kumry, and from Kumry to your webhook endpoints, use TLS.
Each posted entry carries a fingerprint of the one before it, so a change to an earlier entry would break the link and show up.
Each posting records who approved it and when, and the audit history shows who did what in the organisation.
Migration certificates are digitally signed (Ed25519) when Kumry issues them.
API keys are stored only as hashes and shown once. Webhook signing secrets are kept encrypted, and every webhook delivery is signed so your endpoint can check it came from Kumry.
Documents uploaded to Kumry are virus-scanned, and files that fail the scan are held back rather than stored with your records.
They show that records and certificates have not been altered since they were written or signed. They do not show that the underlying accounting choices were right, which is why the approval trail and your accountant's review still matter.
Read how verification works →Found a vulnerability? Please report it privately to support@kumry.com. Include enough to reproduce the issue, and leave out customer data, secrets or exploit material beyond that.