- Sinch Authentication 365’s token generation is implemented using both industry standard RFC 6238 (TOTP) and RFC 4226 (HOTP).
- Implementation of TOTP algorithms exceed the default by using a SHA-256 cryptographic hash method instead of SHA-1 (default)
- Invalid responses are limited and locked out after repeated failures from an end-user.
- Sinch Authentication 365 is implemented across geographically redundant servers, requiring a secure connection between Sinch and the customer.
Learn more about the security standards adopted by Sinch Authentication 365.
Steven Garcia, Chief Architect, Head of Product and Infrastructure Engineering