- Reassure users.
- Allow users to enter sensitive data, safe in the knowledge that They will be protected.
- Minimize the risk of fraudulent use of user data.
Use a computer security certificate in a version supported by recent versions of browsers
Use a decentralized third-party authentication service such as OpenID.
A secure page can be recognized by its URL which begins with https:// or by the presence of a visual element in the browser (a padlock, change of colour of the URL input bar).
For any website offering to exchange sensitive data:
- Enter the URL address of the website in http (not in https), without being identified, and check that you are directly redirected to the HTTPS version of the site and that all exchanges are secure;
- At the very least, check that the exchange of sensitive data (pages for entering identifiers, personal or banking data, etc.) are in HTTPS;
- In the event that the data is entered in an unsecured page, check in the source code of the form that an HTTPS address is present within the action attribute, which proves that the data is sent to a secure page.
Please note, the third option does not offer a level of security equivalent to the first two and can be tolerated in the case of personal data, or even identifiers but never for very sensitive data (biometric or banking data for example).
Opquast training and certification
The objective of these rules and the Opquast community mission is ‘making the web better’ for your customers and for everyone! Opquast rules cover the key major areas of risk that can negatively affect website users such as privacy, ecodesign, accessibility and security.