{"id":154,"date":"2024-11-15T12:25:21","date_gmt":"2024-11-15T11:25:21","guid":{"rendered":"https:\/\/aralez.co\/index.php\/docs\/documentation\/4-configuration-and-customization\/configuring-encryption-and-security-options\/"},"modified":"2024-11-17T21:30:17","modified_gmt":"2024-11-17T20:30:17","password":"","slug":"configuring-encryption-and-security-options","status":"publish","type":"docs","link":"https:\/\/aralez.co\/index.php\/docs\/configuring-encryption-and-security-options\/","title":{"rendered":"Configuring Encryption and Security Options"},"content":{"rendered":"\n

Aralez provides built-in encryption and security mechanisms to protect the sensitive data it collects during triage. By leveraging AES-GCM encryption and flexible configuration options, users can ensure that collected files are securely and safely stored and transferred. This page explains how to configure encryption and manage security settings in the YAML configuration file.<\/p>\n\n\n\n

\n

Important<\/strong>: In digital forensics and incident response workflows, it is critical to handle potentially malicious files securely to prevent unintentional execution or propagation. Aralez<\/strong> includes a feature to encrypt collected malware samples with the password \"infected\"<\/code>. This ensures that the encrypted files cannot be accidentally executed or analyzed directly on a workstation without first being intentionally decrypted. <\/em><\/p>\n<\/blockquote>\n\n\n\n

<\/div>\n\n\n\n

Overview of Encryption<\/strong><\/h4>\n\n\n\n

Aralez supports AES-GCM encryption<\/strong>, a secure and efficient encryption standard, to safeguard collected files. When encryption is enabled, files are encrypted and saved with an .enc<\/code> extension. The encryption key (password) is defined in the configuration file using the encrypt<\/code> field.<\/p>\n\n\n\n

<\/div>\n\n\n\n
Configuring Encryption<\/strong><\/h5>\n\n\n\n
encrypt<\/code> Field<\/strong><\/h6>\n\n\n\n