Deepomatic Platform
  • Overview
  • Release notes
    • January 2025
    • November 21, 2024
    • October 17, 2024
    • September 19, 2024
    • July 18, 2024
    • June 27, 2024
    • May 23, 2024
    • April 18, 2024
    • March 21, 2024
    • February 22, 2024
    • January 18, 2024
    • December 13, 2023
    • October 26, 2023
    • July 20, 2023
    • June 29, 2023
    • May 29, 2023
    • April 27, 2023
    • March 30, 2023
    • February 17, 2023
    • January 19, 2023
    • December 22, 2022
    • November 18, 2022
    • October 19, 2022
    • September 19, 2022
    • July 27, 2022
    • June 26, 2022
    • May 17, 2022
    • April 13, 2022
    • March 17, 2022
    • February 10, 2022
    • December 21, 2021
    • October 26, 2021
  • Getting started
  • ADMIN & USER MANAGEMENT
    • Invite and manage users
      • Invite group of users at once
      • SSO
        • Azure Active Directory
  • Deepomatic Engage
    • Integrate applications
      • Deepomatic vocabulary
      • Deepomatic connectors
        • Set-up
        • Camera Connector
        • Work Order Connector
      • API integration
        • Authentication
        • Errors
        • API reference
          • Work order management
          • Analysis
            • Guide field workers
            • Perform an analysis
            • Correct an analysis
          • Data retrieval
          • Endpoints' list
      • Batch processing
        • Format
        • Naming conventions
        • Processing
        • Batch status & errors
      • Data export
    • Use the mobile application
      • Configure a mobile application
      • Create & visualize work orders
      • Complete work orders
      • Offline experience
    • Manage your business operations with customisable solutions
      • Roles
      • Alerting
      • Field services
        • Reviewing work orders
        • Exploring work orders
        • Grouping work orders
        • Monitoring assets performance
      • Insights
  • Security
    • Security
    • Data Protection
Powered by GitBook
On this page
  • Authentication and Access Management
  • Protection of Customer Data

Was this helpful?

  1. Security

Data Protection

Authentication and Access Management

End users may log in to Deepomatic using an Identity Provider, leveraging Deepomatic’s support for the Security Assertion Markup Language (SAML). This service will authenticate an individual’s identity and may provide the option to share certain personally identifying information with Deepomatic, such as your name and email address. Deepomatic’s SAML support allows organizations to control authentication to Deepomatic and enforce specific password policies, account recovery strategies, and multi-factor authentication technologies.

All requests to the Deepomatic API must be authenticated, either via a user/password authentification or via an API key tied to a user. The various dashboards of the platform and the underlying API sections are tied to specific roles. A user can access a specific dashboard only if he/she has been attributed the corresponding role.

Protection of Customer Data

Data submitted to the Deepomatic service by authorized users is considered confidential. This data is protected in transit across public networks and encrypted at rest. Customer Data is not authorized to exit the Deepomatic production service environment, except in limited circumstances such as in support of a customer request.

All data transmitted between Deepomatic and Deepomatic users is protected using Transport Layer Security (TLS). If encrypted communication is interrupted the Deepomatic application is inaccessible.

Deepomatic maintains one data center in the EU and one data center in the US. Unless specifically required, your account will be assigned to the closest data center. Deepomatic utilizes encryption at various points to protect Customer Data and Deepomatic secrets, including encryption at rest (e.g. AES-256).

Access to Customer Data is limited to functions with a business requirement to do so. Deepomatic has implemented multiple layers of access controls for administrative roles and privileges. Access to environments that contain Customer Data requires a series of authentication and authorization controls, including Multi-Factor Authentication (MFA). Deepomatic enforces the principles of least privilege and need-to-know for access to Customer Data, and access to those environments is monitored and logged for security purposes.

Last updated 15 days ago

Was this helpful?