Every Cloud 66 account has a Security Score. This measures how secure your account is against unauthorised or unwanted access. Security Score is based on industry best practices for access and authentication controls.
Finding your Account Security Score
To see the Account Security Score for your Cloud 66 account:
- Open your Dashboard
- Click on your account avatar (top-right) and select Account Settings
- Click on Login & Security in the Account panel on the left This will show you your current score (out of 100%) and suggest ways to improve it (if necessary).
The components of your Security Score
Your account's score is based on six (interrelated) factors:
- Do you use two factor authentication (2FA) or do you rely entirely on passwords?
- If you are already using 2FA, do you have more than one key to access your account?
- Do you have an appropriate number of user accounts, or are team members sharing logins?
- Are you enforcing 2FA for your entire team, or is it optional?
- Are other team members using 2FA?
- Are you using any personal access tokens in your account?
To achieve a perfect Security Score, you would need to ensure all of the factors above follow best practices - i.e. no shared logins, 2FA enforced (and enabled) for all accounts, backup 2FA keys (to allow for lost or stolen devices) and no personal access tokens.
What are personal access tokens?
Personal access tokens are the method we use to give external services access to your Cloud 66 account (with your approval, of course!) You can check if you have any tokens on your account via this link or by visiting the Account Settings page and clicking on Authorized Apps in the Settings panel.
Having personal access tokens associated with your account makes it inherently less secure because it gives an external service access to one of your applications. The external service may well be trustworthy, but our system cannot independently verify that trustworthiness and so it will always warn you about these tokens.
Why do I need 2FA?
Over the last five years hackers have stolen several billion password and username combinations from a variety of companies and services, including LinkedIn, Yahoo and Dropbox.
This has provided criminals and other bad actors with an incredible toolkit for breaking into online services because it has dramatically narrowed the search space for passwords actually used by humans (compared to the total available combination of characters available for use in passwords).
If you're unconvinced of the dangers, we suggest you visit Have I Been Pwned? to check your own exposure.
2FA is an order of magnitude more secure than simple passwords because it requires access to a second, independent device or mechanism (such as a mobile phone). This does not make an account un-hackable, but it makes hacking difficult enough that criminals may simply target other (less secure) accounts.
Cloud 66's 2FA uses the FIDO2 (Fast IDentity Online v2) standard. This means:
- Greater security (thanks to public key cryptography)
- Less friction (multi-factor authentication and BYOD)
- Best practice implementation based on global standards
How FIDO2 works
When a user enables 2FA on their account, the user's chosen authenticator (which can be a smartphone app, a physical key or other device) creates a public/private key pair and shares the public key with Cloud 66.
Then, whenever anyone requests to log in, Cloud 66 will ask the designated authenticator to prove that it has the correct private key by signing the login request with that key. This is then compared to the public key and, if they correspond, the user is logged in.
You can read more about the process here.
Cloud 66 fully supports the FIDO2 standard, including WebAuthn and Client to Authenticator Protocol (CTAP). This new standard is backward compatible with all existing FIDO U2F and UAF keys.
Physical security keys
Although app-based authentication is already very secure, you may prefer to use physical security keys for an additional layer of security. Physical keys are virtually impossible to spoof because the physical presence of a specific device is required. So, not only is the authentication key unique, it is also paired to a specific device which must be physically present during authentication.
Follow our how-to guide to learn how to add a physical security key to your Cloud 66 account.
Why can't we share logins?
Sharing login details, while convenient, opens your account up to significant additional risks. Apart from the fact that shared passwords are more easily leaked, they can be abused by former team members or careless (or malicious) employees.
Cloud 66 uses enhanced security techniques to detect sharing of logins, and we will warn you via email in those cases. However if you ignore this warning, it will be more difficult to audit who is responsible for changes on an account. It also does not allow for different team members to have different levels of access and permissions.