T
Telblu

Security & Compliance

Data Protection

Available today

Learn how Telblu protects organisational data through layered authentication, authorisation, encryption and database security.

Telblu protects organisational information using multiple independent security controls that validate every request before data is accessed. Data protection is enforced through authentication, role-based access control, organisation isolation, Row-Level Security and managed encryption.

Identity & Access

Users authenticate before accessing protected resources. Role-Based Access Control determines what each user may do.

Data Security

Organisational data is protected by Row-Level Security policies that filter every database query.

Organisation Isolation

Users only access information belonging to organisations where they have authorised membership.

Encryption

Data in transit is protected with HTTPS/TLS. Data stored by the managed backend is encrypted at rest.

Overview

Data protection in Telblu is the result of multiple independent security controls working together. Every request is authenticated, authorised and evaluated against organisation membership and database policies before organisational data is returned.

Data Protection Lifecycle

Every request is authenticated, authorised and evaluated before organisational data is returned.

User

Authentication

Session Validation

Role Evaluation

Organisation Validation

Row-Level Security

Managed Database

Encrypted Storage

Data Protection Principles

Telblu's approach to data protection is built on six principles that guide how organisational information is accessed and stored.

Identity Verification

Users must successfully authenticate before accessing protected platform resources. Supported authentication methods include Email & Password and Google OAuth.

Authorisation

Role-Based Access Control determines which organisational resources a user may access. Permissions are evaluated for every protected request.

Organisation Isolation

Users only access information belonging to organisations where they have authorised membership. Organisation boundaries are enforced throughout the platform.

Database Protection

PostgreSQL Row-Level Security ensures database queries only return authorised records. Security is enforced at the database layer.

Encryption

Communication between users and the platform is protected using HTTPS/TLS. Data stored by the managed backend is encrypted at rest.

Audit Visibility

Authentication, administration and governance events are recorded within the application audit log for authorised organisation administrators.

Data Access Flow

The flow below shows how a user request moves through each protection layer before data is returned.

1

User Request

The user initiates a request to access organisational data.

2

Authentication

The platform verifies the user's identity using the current session credentials.

3

Session Validation

The session is validated and confirmed active before any protected resource is accessed.

4

Role Validation

Assigned organisational roles are loaded to determine what the user is permitted to do.

5

Organisation Membership

The platform resolves which organisations the user is authorised to access.

6

Row-Level Security

PostgreSQL RLS policies filter the database query using organisation and role context.

7

Database Query

The database executes the query and returns only rows that satisfy the security policies.

8

Authorised Response

Only data the user is authorised to access is returned to the client.

Data Protection Controls

The table below lists the controls that protect organisational data throughout its lifecycle.

ControlStatus
HTTPS/TLSAvailable
Encryption at RestAvailable
Email VerificationAvailable
Role-Based Access ControlAvailable
Organisation IsolationAvailable
PostgreSQL Row-Level SecurityAvailable
Audit LoggingAvailable
Session ValidationAvailable
SAML Single Sign-OnAvailable

Protecting Organisational Data

Telblu protects organisational data by applying the following controls consistently across the platform.

  • Organisational data is logically isolated.
  • Access decisions require successful authentication.
  • User permissions are evaluated before protected resources are accessed.
  • Database policies prevent unauthorised records from being returned.
  • Security controls operate together rather than independently.

Data Protection Responsibilities

Data protection is a shared responsibility. Telblu operates the platform controls while organisation administrators manage user access and governance.

Platform ResponsibilityCustomer Responsibility
Authentication platformUser account management
Session validationUser lifecycle management
Role enforcementRole assignment
Database securityUser provisioning
Audit loggingInternal governance processes

Current Implementation

The lists below describe what is available today and what is planned for future releases.

Available Today

  • Email & Password Authentication
  • Google OAuth
  • Email Verification
  • TOTP Multi-Factor Authentication
  • Role-Based Access Control
  • Organisation Isolation
  • PostgreSQL Row-Level Security
  • HTTPS/TLS
  • Encryption at Rest
  • Audit Logging
  • SAML Single Sign-On

Planned

  • Password Reset
  • Microsoft OAuth

Best Practices

Enable Multi-Factor Authentication

Best Practice
Require TOTP Multi-Factor Authentication for privileged accounts to reduce the impact of credential compromise.

Review user roles regularly

Recommendation
Recertify role assignments on a defined cadence to ensure permissions remain appropriate as responsibilities change.

Defence in depth

Important
Data protection within Telblu relies on multiple independent security controls working together. Authentication alone does not grant access to organisational data.