The desktop client is compatible with the following operating systems:

* Only 64-bit OSX machines are supported.

Minimum system requirements are as follows:

Mobile Application Support

• Apple iOS 2.4+
• Android 2+
• Windows Phone

Because of the use of an rsync-derived algorithm and a file-queuing mechanism on the desktop client, there is no logical limit to the number or size of files that can be backed-up by the AXIS CloudSync desktop client. File size and count limitations are determined by the file-systems in use, not the AXIS CloudSync desktop client.

Revision capture

AXIS CloudSync employs an rsync-derived algorithm that only sends and stores a file’s deltas (changes), compressed and encrypted, from revision to revision. This algorithm detects byte-level changes and, unlike block-level algorithms, will not re-upload an entire file even if all data within a file shifts as the result of a block being inserted at its beginning.

Security

Security is a core component of the AXIS CloudSync platform. If a device is compromised, administrators have the ability to remotely wipe AXIS CloudSync data from affected machines. No passwords or confidential information are stored in plain-text in the database. Additionally, our hosted solution operates in an SSAE16 and SAS-70 Type II compliant datacenter.

Data is protected using 256-bit AES (Advance Encryption Standard), both in transit and at rest.

When syncing data to the server, the desktop client encrypts data using 256-bit AES. This data is then sent over TLS to the server, which receives the encrypted binary data and stores it in its encrypted format at rest.

When the desktop client requests data from the server, the data is received over TLS; the desktop client then decrypts the data upon receipt before turning it into the original file. When a file is requested through the web, mobile apps, or through the API, the server will decrypt the data and then present the full file to these clients.

The Apache configuration includes TLS ciphers that successfully mitigate the risks of the POODLE  vulnerability, as well as potential BEAST server-side attacks. Additionally, to protect against brute force and dictionary attacks, browsers are prevented from logging in for 30 minutes after 5 failed login attempts.

The following password-complexity requirements are enforced across the Anchor system:

• The password is at least eight characters long.
• The password does not contain three or more characters from the user's account name.
• The password contains characters from at least three of the following five categories:
  1. English uppercase characters (A - Z)
  2. English lowercase characters (a - z)
  3. Base 10 digits (0 - 9)
  4. Non-alphanumeric (For example: !, $, #, or %)
  5. Unicode characters