On this page

Security and Identity#

Signing in#

User accounts. Accounts are managed by Amazon Cognito.

  • Passwords must be at least eight characters and include upper case, lower case and a number.
  • Multi-factor authentication is available with an authenticator app or by text message.
  • Account recovery is by verified email.

Google and Microsoft sign-in. People can sign in with a Google or Microsoft account. Each person has one DevStride account, however they sign in, and a social identity is linked to an existing account only under strict matching rules.

Enterprise single sign-on. Each organization can connect its own identity provider over SAML or OpenID Connect, for example Microsoft Entra ID or Okta. An organization verifies its email domains before its provider is trusted. Any provider client secret is stored encrypted.

Sign-in rules for each organization. An organization decides which sign-in methods its members may use (password, Google or Microsoft, or its own single sign-on). It can require single sign-on and it can require multi-factor authentication. These rules are checked on every request, not only at sign-in.

Customer portal. Service Desk customers sign in to the portal with an emailed link and a one-time code. Alternatively they use their own company's single sign-on, which can be set for each customer company as optional or required. Portal sessions are signed with keys held in AWS Key Management Service (KMS) and checked on every request.

Programs and integrations.

  • API keys. A key and secret for each user, bound to one organization. Secrets are stored only as salted hashes and compared in constant time.
  • OAuth 2.1. DevStride runs its own authorization server, with discovery, dynamic client registration and PKCE using S256 only. Tokens are signed with keys held in KMS and bound to one organization, and people can see and revoke the apps they have connected. AI assistants connect to the MCP server this way.

Permissions#

Access inside an organization is decided by roles and by sharing.

Roles and permissions.

  • Every capability in the product has its own permission, for example creating items, managing boards, viewing reports, running automations or managing billing.
  • A role is a set of those permissions, and each member has one role.
  • Common bundles of permissions are offered in the role editor as templates for convenience. Only the permissions themselves are checked.

Owner. Every organization has exactly one Owner role, which holds every permission and cannot be edited or deleted. An organization always keeps at least one active Owner, and only an Owner can make someone else an Owner.

Your own versus anyone's. Many actions come in two strengths, such as "manage your own comments" and "manage all comments". The narrower one applies to things you created or own. The broader one applies to everything.

Sharing. Work items, workstreams and boards can be shared with people, teams or the whole organization as Viewer, Commenter, Editor or Owner, or access can be denied.

  • A person's own access overrides their team's, which overrides the organization's. A denial always wins.
  • New items inherit sharing from where they are created.
  • Which items a person can see is decided by sharing.

Enforced in one place. Every API endpoint must declare the access it needs, and the build fails if one does not. The web app's copy of permissions is used only to decide what to show; the server makes every access decision.

Protecting data#

  • In transit. All traffic uses HTTPS, the web app sends a strict transport security header, file storage refuses any connection without TLS, and database connections require TLS.
  • At rest. The database, file storage and email are encrypted at rest by Neon and AWS.
  • Sensitive values in the database. Integration tokens, identity provider secrets and webhook signing secrets are additionally encrypted by the application with AES-256-GCM, with key rotation.
  • Signing keys. The keys that sign OAuth tokens and portal sessions are held in KMS and never leave it.
  • Configuration secrets. Credentials are kept in AWS's managed secret stores, not in code or in the repository, and are checked when the application starts. Deploys sign in to AWS with short-lived GitHub identities, so no long-lived AWS keys are stored in GitHub.

Protecting the platform#

  • Rate limits. Every organization has a request rate limit. The sign-in and OAuth routes have their own tighter limits.
  • Browser protections. The web app and documentation sites send a content security policy and anti-framing headers.
  • Threat detection. Amazon GuardDuty watches each AWS account. Findings of medium severity or higher raise an alert.
  • Change alerts. AWS CloudTrail raises an alert for any use of the root account and for security or permission changes made outside the deploy pipeline.
  • File scanning. Files uploaded through the customer portal are held apart and scanned for malware before anyone can open them.
  • Inbound email checks. Every inbound email is checked for viruses and spam, and for sender authentication (SPF, DKIM and DMARC).
    • Infected or duplicate messages are dropped.
    • Messages that fail other checks are held for staff review instead of opening tickets.
    • A sender is trusted only when DMARC passes.
  • Outbound email from customer domains. Email is sent from a customer's own domain only after that domain's DKIM records are verified.
  • Code checks. Every change is scanned for leaked secrets and analysed for common security mistakes before it ships. See Delivery and Environments.

Audit#

  • Authentication log. Records sign-ins and refused single sign-on attempts for each organization. Administrators can read it.
  • Item history. Every work item keeps a full history of who changed what and when.
  • OAuth and portal sign-ins. Both keep their own audit records.
  • Inbound email. Each inbound email keeps a record of the checks it passed or failed.
Powered by DevStride