Sequences

Security

How to report a vulnerability, how sign-in and API tokens work, who can see your work, and what each release records.

Report a vulnerability

Write to security@conductscience.com. Say which release you run, as the docs home shows it, what you found and how to see it again. ConductScience reads that address at any hour. It fixes a critical vulnerability within 7 days and a high one within 30 days, and the release notes name each fix. Please give it that time before you tell others.

Every server answers /.well-known/security.txt with that address, in the standard form that security tools read.

Sign-in and API tokens

  • On this site you sign in with a ConductScience Account, through the authorization code flow with PKCE, a signed state that expires after 15 minutes, and a nonce. Sequences never sees your password.
  • A sign-in lasts 7 days. Five minutes before it ends, the page offers to sign in again in a new tab, so the work open on the page stays.
  • Your session is a signed cookie that the page's scripts cannot read. Signing out ends it in that browser and leaves your other browsers as they are.
  • Programs sign in with API tokens. A token lasts up to 90 days and is shown once. The service keeps only its SHA-256 hash, so nobody can read one back. A token cannot make another token, and Revoke, on the API tokens page, ends one.

Who can see your work

  • Your searches, portfolio exports, cases, listings, saved sequences, watches and applicant joins belong to your account. No other account can open them, except a case you hand to a colleague, with the searches and listing it holds.
  • An admin's usage page counts each account's searches and other work. It shows counts, not content.
  • ConductScience runs this site and holds its stored files.
  • You can delete a listing, a saved sequence or a watch. Searches, portfolio exports and cases have no delete of your own; an admin can delete a case with its searches.
  • Claim text and a case's facts leave the server only when you ask for model suggestions or a draft, and then they go to the model the server names.
  • The ST.26 check runs in your browser and sends nothing.
  • Every page behind sign-in loads its scripts, styles and font from the service alone, under a strict content security policy.
  • Google Analytics counts visits to the home page, the feature pages, the use-case pages, this page, the accessibility page, the docs pages, the API reference, the list of all pages and the plans page. It never runs on the ST.26 check, the sign-in pages, the sample results, the page-not-found pages or any page behind sign-in.

See Who can see your work in the user guide.

The audit log

With sign-in on, Sequences keeps its own audit log: each sign-in, refused sign-in and sign-out, each API token made or revoked, each start of the service with its settings, each change to the invite list, each case handed to another account and each case an admin deletes.

Every event carries the SHA-256 hash of the event before it and its own, so a changed, missing or reordered event breaks the chain from that event on. The log holds no IP addresses, queries, sequences or results. An admin can export it as JSON lines, a day or a time range at a time, and check the chain with the script in the installation guide.

What each release records

Each release gets a software bill of materials (SBOM) in SPDX 2.3, which lists the packages in its container image: the operating system's packages, Node.js, Biopython and NumPy. The list is scanned for known vulnerabilities, with the vulnerability data of that day, before the release is installed on this site.

A high or critical finding with no written reason stops the install. Only an urgent fix may go ahead past the scan, and the install log then names each such finding. A finding is fixed in a later release when a fix exists, or accepted with a written reason once a check in the image shows that the vulnerable code cannot be reached.

BLAST+, FASTA36 and the antibody numbering models are not in the SBOM, so the scan does not cover them. The build pins each of them by version and SHA-256.

The image a customer runs on its own server holds the same system packages and programs. On request, ConductScience sends a release's SBOM, its vulnerability scan and its test results: write to support@conductscience.com.

Run Sequences on your own server

The server edition runs the same releases as this site, in one container image on your own Linux server, with sign-in through your organization's OpenID Connect provider.

  • Queries, results and the sequence snapshot stay on your server.
  • The service connects to your sign-in provider and to nothing else, unless you turn on watch emails, claim suggestions from a model or several servers that share one queue. See Network traffic in the installation guide.
  • There is no license server, and the service sends no usage data anywhere.
  • Sign-in uses the authorization code flow with PKCE, a one-time state and a nonce, and checks the signature of each ID token.
  • The image runs the service as user ID 10001, not as root.

The installation guide gives the steps, and the plans page gives the server edition's price. To get the image, write to support@conductscience.com.