ICOs are quite different as they allow you to convert your tokens with any available pair and withdraw whenever you want. It does not only give the investors a sense of security but boosts up the chances of cash influx for the project owners.
Security Protocols HTTPS: We will use it everywhere in the system. Bcrypt
Hashing Technique: We have used advanced Bcrypt hash to store sensitive information. It is an adaptive function — over time, the iteration count can be increased to make it slower, so it remains resistant to brute-force search attacks even with increasing computational power.
Session Identifier: We have incorporated it after each logout.
Timeout Sessions Management: We have timed the entire session management. Similar to banking websites, we monitor in-activity and timeout sessions. If multiple sessions are detected, we destroy all active sessions. Furthermore, if the user resets the password, we destroy all active sessions
No Open Redirects: The exchange takes care that “no open redirects” performed in the system post a successful login by the user.
Cookies Management: We have given extra attention to cookies management and processing in the HighBank Exchange. We have set only ‘secured’ and ‘Http only’ cookies.
JSON Web Tokens: We employ JSON Web Tokens wherever possible to represent claims between two parties.
One Time Password: OTP is secure but has become an old technique that hackers can sometimes get around.
Reset Password Token: Prediction in the pattern of reset password tokens is a common loophole used by hackers. We have ensured randomness in the reset password token that is generated and sent to users’ emails.
RFC compliant UDIDs: We have adopted the best practice of using RFC compliant UDIDs for user ID, etc.
SMS Authentication: As with banking systems, any update in the personal contact details of the users is done via an SMS verification to the owner.
KYC Document Uploads: To neutralize the shell technique used by hackers to gain access to the exchange server, we are very careful while allowing KYC document uploads, carefully controlling how users upload files and what type of files are allowed. Cross Site Scripting: We employ Content Security Policy headers to fight cross-site scripting and data injection attacks HTTP Strict
Transport Security: We implemented HTTP Strict Transport Security across the exchange to avoid the Secure Sockets Layer stripping attacks.
Clickjacking: We have taken steps to protect the Exchange from Clickjacking and cross-site attacks by making effective use of X-Frame and X-XSS securing.
Countering Phishing Techniques: We keep updating Domain Name System records to add Sender Policy Framework. It effectively counters hackers’ phishing techniques to trick our users from the original site.
Time-locked Transactions: All transactions on HighBank Exchange are executed in a specific timelock and across several steps based on the configuration of the time-lock.
2-Factor Authentication: Using Google Authenticator as a 2-Factor Authentication process helps us to prevent hackers from gaining unauthorized access into users’ accounts.
Cloud Flare: HighBank will use Cloud Flare to secure the exchange and APIs from online cyber attacks.
#HighBank makes #ICO #cryptoexchange #trade and all related process incredibly easier and reliable! We invite you to join our Dedicated #HighBank Community: HERE, as well as:
✅ Website: https://highbank.io/
✅ WhitePaper: https://highbank.io/HighBank_Whitepaper.pdf
✅ Telegram Community: https://t.me/HIGH888
✅ Blog: https://blog.highbank.io
✅ Twitter: https://twitter.com/HighBank19
✅ Facebook: https://www.facebook.com/HighBank.io
✅ Linkedin: https://www.linkedin.com/company/highbank
✅ Github: https://github.com/HighBankio