Updated on 2025-11-06 GMT+08:00

IAM Side

To ensure that your personal data, such as the username, password, and mobile phone number, will not be obtained by unauthorized or unauthenticated principals or individuals, IAM encrypts your data during storage and transmission to prevent data leakage.

Personal Data

Table 1 lists the personal data generated or collected by IAM.

Table 1 Personal data

Type

Source

Description

Modifiable

Mandatory

Username

  • Entered when you create an IAM user or modify a username.
  • Entered when you call an API.
  • User identity identification
  • Identity authentication during console access or API calling

Yes (Administrators can change the username via the console or API.)

Yes

Usernames are used to identify users.

Password

Entered when you create a user or reset the password on the console.

Identity authentication during console access

Yes

No

You can also choose AK/SK authentication.

AK/SK

Displayed in the Security Settings > Access Keys area of a specific user on the IAM console or on the My Credentials > Access Keys page.

Identity authentication during API calling

No

AK/SK cannot be modified, but they can be deleted and created again.

No

AK/SK are used to sign the requests sent to call APIs.

Data Storage Security

IAM uses encryption algorithms to encrypt user data before storing it.

  • Usernames and AKs: non-sensitive data, stored in plaintext.
  • Passwords: encrypted by the salted SHA512 or SM3 and then stored.
  • SKs: encrypted by AES or SM4 and then stored.

Data Transmission Security

Sensitive data (including passwords) of users is encrypted using TLS 1.2 during transmission. All IAM APIs support HTTPS to encrypt data during transmission.