No, SmartEncrypt is only limited by available hard disk space. Large files will take longer to encrypt and decrypt.
The amount of time to encrypt or decrypt a file depend on the file size and speed of the computer. An average document takes milliseconds, but a very large video may take a few minutes.
To share an encrypted file with someone outside of the organization the user creates a password protected HTML file to send. The password-protected files are decrypted using a password of the user’s choice. The HTML file can be then emailed or shared via any cloud file sharing service or portable device. Once the recipient receives the ...
All user data stored on our servers is highly secure and meets compliance requirements. SmartEncrypt does not collect or store any sensitive personal information (PII), and the data that is collected is the minimum required to offer the SmartEncrypt software-as-a-service. We store a small amount of information for each user, group and company which...
DCS utilises Azure for hosting the back-end, the Administration Console and the encryption key vaults. Azure meets a range of compliance requirements for ensuring both the physical and cyber security of our environment, including: (confirm all of the following apply for Azure -was for AWS) •ISO 9001, 27001, 27017, 27018 IRAP • PCI D...
Keys are transferred from the key vault to the client software via an encrypted OpenSSL TLS 1.2 tunnel. If the client detects an issue with the tunnel, it will not proceed with the transmission of the encryption key.
Passwords are encrypted using bcrypt , an algorithm based on the Blowfish cipher. Bcrypt is a password hashing function which incorporates a salt value to protect against rainbow table attacks. It has a significant advantage over a simply salted SHA-256 hash as it performs key strengthening on passwords. Key strengthening increases the resource co...
OpenSSL Secure TLS 1.2 tunnel and encrypted JSON Web Tokens (JWT) – an industry standard RFC 7519 method, represents claims securely between the client and Administrator Console. JWT verification includes header check and validation before acceptance, with time-based expiry of encrypted tokens. Our JWT token life cycle is short-lived, severel...
The Administrator Console is protected against SQL Injection, Cross-Site Request Forgery (CSRF) and Cross-Site Scripting (XSS) attacks. Browser connections to the console are secured using HTTP and SSL/TLS (HTTPS), ensuring that any information exchange between the browser and Administrator Console is encrypted. Encrypted cookies are used to save b...
SmartEncrypt uses the AES encryption algorithm in with a 32 byte key. This is commonly referred to as AES-256. In order to become the Advanced Encryption Standard (AES), the algorithm currently used underwent intense scrutiny from cryptographers around the globe. Now, it is the most widely used symmetric encryption algorithm. The use of validated c...