New ID_Check v2.5.0 — Session Journey: a per-submission timeline of FE/BE events with list & detail views, a new DROPPED session status, and a configurable data retention period. See what's new →
New ID_Check v2.5.0 — Session Journey: a per-submission timeline of FE/BE events with list & detail views, a new DROPPED session status, and a configurable data retention period. See what's new →
Learn how to strengthen data security through liveform encryption settings and secure transmission settings.
Data protection functions provide encryption and secure transmission options to strengthen project security levels. Safe data transmission and storage are supported through liveform encryption settings and secure transmission settings.
When encryption is needed in liveform URL’s Query String, data must be encrypted using the selected encryption algorithm and encryption key.
Algorithm
Description
ECB (Electronic Codebook)
Fast and simple block encryption method
GCM (Galois/Counter Mode)
Enhanced encryption method including authentication and integrity functions
How to Use After Algorithm SelectionAfter selecting encryption algorithm, parameters requiring encryption in liveform URL’s Query String must be encrypted using the selected algorithm and encryption key, then used in the form encrypted={encrypted_data}.
Activate encryption-only mode when you want to encrypt and use all Query String parameters.
When encryption-only mode is activated, only pid, encrypted, lang parameters are allowed in liveform URL, and all other parameters must be encrypted and included in the encrypted parameter.Allowed URL Format:
Encryption-only Mode PrecautionsWhen encryption-only mode is activated, all unencrypted Query String parameters are ignored. All data must be encrypted and included in the encrypted parameter.
Manages keys to be used for encryption. You can use API KEY or issue and use a dedicated key (secretKey).
Key Type
Description
API KEY
Use the default API key assigned to the project as encryption key
Dedicated Key (secretKey)
Dedicated encryption key newly issued and used in liveform
Dedicated Key (secretKey) Important NoticeNewly issued dedicated key (secretKey) is only displayed at issuance, so be sure to store it safely. If lost, you must reissue and use, and existing keys can no longer be used.
Key Selection Guide
Using API KEY: Can start quickly with simple settings.
Using Dedicated Key (secretKey): Can strengthen security by using different keys in liveform and API.
Non-encryptable Parameterspid, lang query strings and sid, action query strings used in ‘Additional Process (Injection)’ page do not support encryption. However, when using Injection, sid and action must be encrypted by including them inside the encrypted parameter.
When secure data transmission option is activated, all data transmission between ARGOS and customers is encrypted.
Setting
Description
Secure Data Transmission
Encrypts and transmits data in API methods (GET, POST, PATCH, etc.) and webhooks.
Important: Encryption/Decryption RequiredWhen secure data transmission option is activated, all API request (Request) and response (Response) data must be encrypted/decrypted. Errors occur if requests are made with unencrypted data.