Exto
API Status
  • Introduction
  • Architecture
    • Microservice Architecture
    • Security
  • Release Cycle
  • Integration
    • Best Practices
    • Endpoints
    • Response Format
    • Error
    • Data Formats
    • Data API
      • Generate API Key
      • API
      • ID/Access Token
      • Azure API Gateway
      • Filter Master Record/Custom Module Records
  • Installation
    • Installing Exto on Kubernetes
      • Prerequisite
      • Installing Exto
        • Setup
        • Configuration
        • Installation
        • Purging
      • Tips and Tricks
        • AKS to use existing storage account
        • AKS with Application Gateway Ingress Controller
        • AKS Private Cluster
Powered by GitBook
On this page

Was this helpful?

  1. Architecture

Security

VAPT, SOC II Certified

PreviousMicroservice ArchitectureNextRelease Cycle

Last updated 8 months ago

Was this helpful?

  • Exto is built considering the IT security standards and best practices, which includes secure default configuration, sensitive data protection, authentication ,and access control.

  • Exto services only accessible over TLS 1.2 and secured over REST.

  • Users can access the application using native authentication or SSO with Google and Microsoft.

  • Internal services and Integration API's need to acquire JWT (JSON Web Tokens) for authentication and authorisation.

  • Security measures implemented to grant project access to users and tenants. No tenant will be able to access other tenant projects.

  • The folders and files in Exto cannot be accessed until they are granted access permissions. This makes the document modeling secure.

  • Exto is also VAPT compliant thereby keeping the data secured and protecting the software from evolving threats.

  • Exto is SOCII certified