Security Protocols and Infrastructure

Version 1.3

bilabl commits to delivering the highest level of security, reliability, privacy, and compliance in our products and services. Here are measures bilabl takes to keep your data secure.

‍

1. Application architecture

BILABL is a native SaaS solution, built on state-of-the art infrastructure. We embed security best practices into everystep of our development lifecycle.

Here’s an outline of our architecture:

●    Cloud provider: Amazon Web Services (AWS)

●    Infrastructure as code tool: Terraform

●    Source code management: Git, Gitlab

●    CI/CD: Gitlab CI/CD

●    Container orchestration: Kubernetes (EKS)

●    DBMS: Postgres (AWS RDS)

●    Search Engine: Elasticsearch

●    Logging & Monitoring: ELK Stack (Elasticsearch, Logstash, Kibana), Prometheus

●    Programming Language: Golang, Python, React

●    Architecture: Microservices

‍

Request Flow

All client requests are routed through a centralised API Gateway, which acts as the single-entry point and security enforcement layer:

  • The Load Balancer receives the request and forwards it to the API Gateway.
  • The API Gateway delegates authentication and authorisation to the AuthX service, which verifies the user's identity, resolves tenant context, and retrieves tenant-level settings.
  • Upon successful verification, the API Gateway injects the authenticated context (user, tenant, permissions) into request headers and forwards the request to the appropriate upstream service.
  • Upstream services operate exclusively with the context provided by the API Gateway; they never independently handle authentication.

This design enforces a single point of access control, ensuring consistent security enforcement across all services.

Asynchronous Processing

For event-driven workflows, bilabl uses a dedicated Consumer service backed by RabbitMQ. Services publish events via HTTP to the Consumer, which standardises event delivery with built-in retry logic, logging, and tracing. Events are then dispatched to registered handlers via HTTP webhooks based on topic configuration.

This architecture ensures reliable, auditable event processing without direct coupling between services.

‍

2. Cloud Infrastructure & Network Security

AWS Foundation

bilabl is hosted entirely on AWS, leveraging its enterprise-grade security capabilities. AWS maintains compliance with a comprehensive set of international standards:

  • SOC 1/ISAE 3402, SOC 2, SOC 3
  • FISMA, DIACAP, and FedRAMP
  • ISO 9001, ISO 27001, ISO 27017, ISO 27018

Network Architecture

Our infrastructure follows a defence-in-depth model:

  • All services, databases, and internal components are deployed within private subnets. They are not directly accessible from the public internet.
  • Only the Load Balancer is exposed to external traffic, serving as the sole ingress point.
  • Internal service-to-service communication occurs entirely within the private network.
  • AWS Shield Standard provides automatic protection against common DDoS attack vectors at the network and transport layers.

Production Access Control

Access to production infrastructure is restricted and controlled:

  • Engineers access production environments exclusively through Teleport, a zero-trust access platform that provides identity-based, auditable access to infrastructure.
  • All sessions (SSH, Kubernetes, database) are recorded and logged for full audit trail.
  • Role-based access policies ensure engineers only access resources relevant to their responsibilities.

 

3. Data Security

Encryption

bilabl encrypts data at every layer:

  • In transit: All communication is encrypted via TLS 1.2+ using 256-bit AES encryption. Public endpoints enforce HTTPS exclusively.
  • At rest: All databases (Amazon RDS) and storage services utilise AWS-managed encryption with 256-bit AES. Backup data is encrypted using the same standards.
  • Key management: Encryption keys are managed by AWS through its managed key infrastructure, providing automated key rotation and access controls.

Multi-Tenant Data Isolation

As a multi-tenant platform, bilabl enforces strict logical data isolation:

  • Each tenant’s data is separated at the application level with enforced tenant context on every request.
  • The API Gateway + AuthX service injects and validates tenant context before any data access occurs.
  • Cross-tenant data access is architecturally prevented — services only operate within the scope of the authenticated tenant.

Data Residency

bilabl currently hosts all data in the AWS Asia Pacific (Singapore) region. Additional regional deployments are available upon request to meet specific data residency or regulatory requirements.

 

4. Identity & Access Management

Authentication

bilabl follows industry best practices for SaaS authentication:

  • User passwords are securely hashed and never stored in plaintext.
  • Credentials are filtered from all application log files.
  • Multi-Factor Authentication (MFA) is available for all accounts via Microsoft Authenticator or Google Authenticator.
  • OAuth 2.0 is used for API authentication and third-party integrations, with access scoped and governed by bilabl’s terms of service.

Access Monitoring

  • Every authentication attempt is logged with full context: user ID, IP address, timestamp, and result.
  • Authentication logs are continuously monitored.
  • Repeated failed authentication attempts trigger automatic account lockout to prevent brute-force attacks.

Session Management

  • Sessions are managed with secure, time-limited tokens.
  • Token refresh and revocation mechanisms are in place to ensure sessions cannot be hijacked or reused after expiry.

For higher protection, all accounts are able to enforce the use of strong passwords and Multi-Factor Authentication (MFA) through Microsoft Authenticator or your Google account.

 

5. Secure Development Lifecycle

bilabl integrates security into every stage of the software development process:

Code Quality & Review

  • All code changes require mandatory peer review before merging into the main branch.
  • Reviews are conducted through GitLab merge requests with enforced approval policies.
  • Code quality standards and conventions are maintained across the engineering team.

Environment Separation

  • Staging and Production environments are fully separated — distinct infrastructure, configurations, and access controls.
  • New features and changes are validated in staging before any production deployment.
  • Production deployments follow a controlled CI/CD pipeline with automated build, test, and deployment stages.

Continuous Integration & Delivery

  • All code is built, tested, and deployed through GitLab CI/CD pipelines.
  • Automated tests run on every merge request to catch regressions early.
  • Deployments to production are gated and require passing all pipeline stages.

‍

6. Operational Security

Monitoring & Alerting

bilabl employs continuous monitoring to ensure platform health and rapid incident detection:

  • ELK Stack (Elasticsearch, Logstash, Kibana) is used for centralised log aggregation, search, and visualisation.
  • Prometheus provides real-time metrics collection and monitoring of application and infrastructure health.
  • Key metrics monitored include requests per second (RPS), error rates, latency, and resource utilisation.
  • Automated alerts are configured to notify the engineering team via Slack and Telegram when anomalies or threshold breaches are detected.

Incident Management

bilabl maintains a structured incident response process:

  • Incidents are classified by severity and triaged accordingly.
  • The engineering team is notified immediately through automated alerting channels.
  • Post-incident reviews are conducted to identify root causes and implement preventive measures.
  • Clients are communicated with promptly and transparently during service-impacting incidents.

Backup & Recovery

  • Automated backups are performed on a daily, weekly, and monthly basis.
  • Backups are stored securely in Amazon S3 with encryption at rest.
  • You always retain full ownership of your data - a complete export of your database and files is available upon request at any time.

‍

7. API Security

bilabl’s API follows industry-standard security practices:

  • OAuth 2.0 authentication with scoped access tokens.
  • All API traffic is encrypted via TLS.
  • API access is restricted by OAuth 2.0 scopes, ensuring clients can only access resources they are explicitly authorised for.
  • All integrations must be directly authorised and signed at the user level, offering full visibility and control over third-party access.

‍

Additional Questions?

Please reach out to the Technical team at tech@bilabl.io or contact us at https://www.bilabl.io/contact-us

‍

Want to learn more?
Book a demo with our experts today. Discover how bilabl can help your team in 40 minutes.
See the product. Ask any question.
Learn how our solution will save you time and money