Uptime

Security & trust

Clear controls.
Stronger trust.

Your operational data deserves clear boundaries. See how Undown protects credentials, checks workspace access, and keeps internal details private.

Explore the controlsTalk security with us
Encrypted credentialsWorkspace boundariesPrivate by context
01 / Protect the credentialInteractive walkthrough
Integration vaultApplication encryption

Credential lifecycleStage 02 / 03

Authenticated application encryption.

AES-256-GCM uses a derived application key, a fresh initialization vector and an authentication tag to protect the stored credential.

algorithm
AES-256-GCM
key derivation
HKDF / SHA-256
initialization vector
12 random bytes

A new IV is generated for each encryption operation.

Illustrative demo · No live credentials

01 / Current application controls

Protection, built into
the everyday details.

From a saved integration key to a public status update, each control has a specific job.

01

Credential encryption

Integration credentials are encrypted with AES-256-GCM using a derived application key, unique initialization vectors, and authentication tags.

Write-only secrets · Versioned ciphertext
02

Tenant boundaries

Organization-scoped requests require an authenticated session, active membership, and permission for the requested action.

Membership + permission + scoped query
03

Role-based access

Owner, administrator, member, and viewer roles separate management privileges from read-only access across workspace resources.

Four workspace roles
04

Administrative audit trail

Platform changes can retain actor, action, target, request, network, and before/after context while redacting sensitive field names.

Sensitive values redacted
05

Session protection

Production authentication uses secure cookies, trusted origins, account-disable checks, and session revocation after password resets.

Secure production cookies
06

Public data minimization

Public status responses use customer-facing component data and derived identifiers without exposing monitor targets or organization records.

Targets remain private

02 / Access decisions

The right access.
For the right action.

A session is the starting point. Workspace membership and role permissions determine what happens next. Try a request as a viewer.

Authorization walkthroughIllustrative example

Choose a request

V
Workspace viewerExample actor · Read-only role

Every request passes through

  1. Authenticated sessionSatisfied
  2. Workspace membershipSatisfied
  3. Action permissionSatisfied

Request allowed

A viewer can read a monitor in a workspace they belong to.

Demo only. No real workspace is accessed or changed.

03 / Public boundaries

Keep customers informed.
Keep the context private.

Share component health and published updates. Monitor targets, workspace membership, and internal investigation notes stay inside.

Inside the workspacePrivate

Incident / Checkout API

The full investigation.

Monitor target
checkout.example.com/health
Regional evidence
Virginia + Frankfurt / HTTP 503
Investigation notes
Internal responder context

Internal details stay in the workspace.

Public status pagePublished

Customer-facing update

Checkout service disruption

Investigating

We are investigating checkout errors. Our team is working to restore service and will share an update here.

Explore the public example

Fictional incident and status page, shown to illustrate the public data boundary.

04 / Data handling

Every kind of data.
A defined purpose.

Understand what the application handles and how access is scoped.

01

Account and membership

Authentication, organization access, invitations, and support

Accessed through authenticated, role-aware operations
02

Monitoring telemetry

Availability history, incident evidence, charts, and reports

Organization-scoped; historical observations survive region retirement
03

Integration credentials

Deliver notifications to configured destinations

Application-encrypted and never returned in full after storage
04

Public status content

Communicate component health, maintenance, and incidents

Explicitly selected content with internal targets removed

05 / Security roadmap

Where we are.
What comes next.

A transparent view of current controls, work in progress, and planned capabilities.

Current

3 items

Organization-scoped authorization

Membership and role permissions are evaluated before workspace data access.

Encrypted integration vault

AES-256-GCM protects stored provider credentials at the application layer.

Platform audit records

Administrative changes retain traceable context with sensitive-key redaction.

In progress

3 items

Published retention schedule

Documented deletion windows and customer-facing retention commitments.

Formal incident-response policy

Published severity, escalation, notification, and post-incident commitments.

Self-service session management

User-visible active sessions with individual and global revocation controls.

Planned

3 items

Multi-factor authentication

Additional account verification beyond the primary password flow.

Enterprise identity

SAML-based SSO and automated identity lifecycle management.

Independent compliance program

Evidence collection and third-party assessment before any certification claim.

Planned items are not available features or delivery commitments. This page is not a claim of independent certification.

An open conversation

Let's talk about security.

Reviewing a requirement or reporting a concern? Tell us what you need to know.

Report a security concernDiscuss your requirements

For reports, include a description and safe reproduction steps. Omit passwords, live tokens, and customer data.