This document describes the security measures implemented in the RushFiles software solution as a reference for Resellers
when addressing customers’ questions about data security.
1. Secure communication
All communication in RushFiles is done based on Secure SSL/TLS communication on port 443.
The RushFiles applications will only work with certificates that has been digitally signed by a trusted CA. This will make sure that all
communication between server and client is encrypted, and it will also prevent so called “man in the middle” attacks.
A "man in the middle attack" is a situation where an imposter is trying to extract sensitive information from a client by impersonating you.
The RushFiles’ Reseller have the responsibility to install the certificate on the server running the RushFiles solution and we recommend
as minimum the use of a 2048-bit wildcard certificate signed by a trusted CA.
2. Data Encryption in client applications
There are several types of client applications in the RushFiles ecosystem.
All connections are encrypted with AES encryption and Mobile devices are secured with isolated storage.
3. Encryption and obfuscation of data on the Resellers' server
All file and folders are obfuscated by not using the original name and extension type, so files are can’t be discovered.
Also the file and folder structure is secured in a database and the files are not stored in the same structure on disk to
obfuscate even more.
It is possible to give each individual Account/Company an encryption key, which will then be used to encrypt all data uploaded to the server on that company. The encryption algorithm we use, is called AES (Advanced Encryption Standard) which is the industry’s standard and one of the most vigorously tested and secure encryption standards in existence. In AES it is possible to use 128, 192 or 256 bit keys, and we use 256 bit keys to encrypt file data. This helps ensure that your data is kept secure.
Since performance is a prime requisite for our solution, it is important for the server to be able to access file data through what is called random access, which simply put, means being able to access any part of the file without having to decrypt the entire file first. In order to achieve this we utilize a mode of operation called Counter Mode as described per NIST Special Publication 800-38A[1].
This mode of operation uses a counter to transform each block of data, and for each transformation the counter is incremented. In this way each block is transformed with a unique counter, which ensures complete confidentiality of encrypted data.
Enabling encryption will prohibit the providers in accessing the files. But also make it difficult, if not impossible to recover the files if the Company loses the password.
4. Logon credentials
Passwords are stored as a hash along with a salt and a high iteration count. The salt is 256 bits long and is generated with
a high entropy cryptographic function. Before hashing occurs the password is appended with the salt and a secret key which
is not stored in the database.
All communication from clients to servers via API are using tokens generated from the domain master. No username or
passwords are used continually on API calls.
Password security if use of AD integration
For users set up to use Active Directory (AD) their password is only stored in the AD and the password rules that apply in the
AD is enforced since RushFiles always authenticate the user credentials through Single Sign On (SSO) directly in the AD.
Password security without AD integration
If the organization don’t have AD integration the standard RushFiles password security rules apply and the password must be
strong, meaning:
- Minimum 8 characters
- Upper and lower letters are required
- At least one numbers or one special character is required
Only the individual user can change the password by requesting a onetime link send to the email address the user is registered with.
5. Logon Mechanism – Global discovery service
The RushFiles service is designed to connect to multiple Domains (installations) where RushFiles acts as a discovery service, which
enables access to multiple servers from the same client.
Resellers have the option to run the RushFiles service as an Isolated Data Island, the logon mechanism is slightly
different then for Resellers using the global discovery service (see section 7).
6. Logon Mechanism – isolated data island
For Resellers who chose the Isolated Data Islands option, the logon mechanism is slightly different then for Resellers
using the Global Discovery Service.
When providing Isolated Data Islands the client applications can only login to the servers that is hardcoded in the applications.
The Reseller can therefore not change IP without building and publishing new client applications.
7. Use of Isolated Data Island vs. Global discovery service
Isolated Data Islands is a high security version of the RushFiles solution. The Isolated Data Island means that the Resellers' customers
don’t use the normal Global Discovery Service to discover domains to connect to.
This is often used if the end-customers are organizations that requires very high security measures.
This requires rebranding of the clients as the URL for the domain will be hardcoded into the clients for tight security.
This also means that, to access the data, users will need to use the rebranded client applications.