Tridge
Sign in

Security

What protects a Tridge workspace, stated as facts we can show, and how to tell us when something is wrong.

Last updated

Signing in

  • One sign-in. People sign in through Exprezoe Identity, Exprezoe’s single sign-on service, which checks the password and the second step.
  • A second step is required. Tridge accepts a sign-in through Exprezoe Identity only when Identity confirms that a second factor was used: an authenticator app or a security key.
  • No self-registration. Nobody can create an account for themselves, and signing in as a guest is switched off.
  • Access follows the directory. Who may sign in to Tridge is decided in Exprezoe Identity, by membership of a group.

In transit and in the browser

  • Every connection uses HTTPS, and browsers are told to refuse anything else (HSTS).
  • The application runs under a content security policy that blocks scripts from other sites, inline scripts, plug-ins and framing by other sites.
  • The application loads nothing from an advertising or analytics network.

Your data

  • Backed up every night. The whole database and every stored file, not a subset.
  • Encrypted backups. A backup is encrypted before it leaves the machine it was made on, and a set that is not encrypted fails its own check.
  • A second server. Each night’s backup is copied to a separate server and verified there.
  • Restores are proven, not assumed. A backup counted as working only after a complete restore from it passed.

How it is built and changed

  • Every release of the application is built from a recorded commit, type-checked first, and tested in a browser against the running service before it replaces the previous one.
  • A release can be put back with one command, and the previous version is kept for that purpose.
  • The open-source core is public: anyone can read the code Tridge is built on. See Open source.

This website

This site is a set of static files. It runs no scripts, sets no cookies, has no forms and loads nothing from another host. Its content security policy allows none of those things, so a mistake in a page cannot quietly add them.

Report a vulnerability

Write to security@exprezoe.com. Please include what you found, where, and the steps that show it. A person reads every report.

  • Give us a reasonable time to fix a problem before you make it public.
  • Test only against your own account and your own workspace. Do not read, change or delete other people’s data, and do not degrade the service.

The machine-readable form of this section is at /.well-known/security.txt.