Security

Prev Next
Servitly is a distributed system composed of many interconnected elements. The DPS system applications are configured and running on the architecture described below. Frontend The DPS main interface is provided through the Frontend, which is...
This article describes the security framework, including physical and logical countermeasures, DPS functionalities, and best practices put in place on various aspects like data transmission, API integration, and user interface and experience. The f...
Servitly can save a large amount of data, but this does not imply that all of your DPS data is persisted forever. Some data are critical according to the type of service you are offering, and it is right that these are kept forever; vice versa, less...
Other than API use by the cloud-to-cloud integrations (managed in the Console), in the DPS it is possible to let Organization users to create End-user API Keys for a specific business entity (e.g. customers, partners). For instance, for a speci...
To allow end-users to access APIs in a secure way without exposing their personal passwords (e.g. encoded in a configuration files), they can use the concept of Personal Access Token (PAT). A PAT is a long string consisting of numbers, letters, and...
This article explains how clients and products establish a trusted SSL connection to the DPS backend (including the built-in connectors ) and how to keep the CA certificates up to date throughout the life of your products. Certificate download URL...
A user accessing the DPS can enforce the security by enabling the two-factor authentication mechanism, which requires the user to provide, in addition to an email and password, an OTP (One Time Password) generated by a third-party system (e.g. Goo...
Here you will find all the functionalities available to users in the DPS, enabling them to access the DPS and manage personal data in compliance with the GDPR. Explicit Consent All users accessing the DPS are presented with the following documents...
Discover how NIS 2 compliance impacts manufacturing companies and what steps you need to take to meet the EU’s updated cybersecurity directive.
Checkout how Servitly can help you meet the new NIS 2 directive key requirements.
In this article, you can find how Servitly is compliant with the requirements of the certification schemes defined by the Cybersecurity Act (Regulation (EU) 2019/881) . EUCC : European Cybersecurity Certification Scheme on Common Criteria [alr...
The Cyber Resilience Act (Regulation (EU) 2024/2847) , also known as CRA, sets mandatory cybersecurity requirements for products with digital elements (hardware and software) made available on the EU market, covering their entire lifecycle, from ...
To ensure the security of our customers' information, we have implemented an Information Security Management System (ISMS) in accordance with  the requirements of ISO/IEC 27001:2022 standard. All the company policies, terms, and opera...