This documentation details the encryption practices implemented in Omnidocs Create to secure data at rest and in transit, utilizing advanced encryption standards to protect sensitive information. It explains how data is stored using MongoDB and Azure Blob Storage, ensuring compliance with industry-best security practices.
Overview of Encryption Strategy
Omnidocs Create is committed to ensuring the security and privacy of its users' data. To achieve this, the platform employs robust encryption mechanisms for data at rest and data in transit. This dual-layered approach guarantees that all data, regardless of its state, is shielded from unauthorized access.
MongoDB Storage:
Data stored in MongoDB is encrypted at rest using strong encryption protocols. This ensures that sensitive data, such as user information and operational data, remains secure against unauthorized access attempts. MongoDB's encryption at rest encompasses all data stored within the database, including backups and logs, safeguarding them from potential breaches.
Azure Blob Storage:
Specific parts of data needed for Omnidocs Create is stored in a Blob Storage, this consists of temporary files and cached files. Like MongoDB, Azure Blob Storage also supports encryption at rest. The data stored in these blob containers is encrypted using Azure's advanced encryption standards, providing an additional layer of security and data integrity.
HTTPS Protocols:
All data transmitted to and from Omnidocs Create is protected using HTTPS, employing SSL/TLS encryption. This ensures that any data sent over the internet is securely encrypted, preventing interception or tampering by malicious actors. HTTPS is a fundamental security measure for protecting data integrity and confidentiality as it moves between the user's device and Omnidocs Create servers.
Comments
0 comments
Article is closed for comments.