Reference Guide
Kron PAM Reporting and Logging...
Tamper-Evident Logging
any logs stored in the database can potentially be altered by a malicious user who gains access to mitigate this risk, kron pam implements a tamper evident mechanism that makes it possible to detect and identify any changes made to log records this mechanism ensures that any unauthorized alteration can be reliably detected all log types are stored in the database and are secured using hashing and encryption each log record is processed with the sha 256 hashing algorithm to generate a unique hash value the hash value, together with its timestamp, is encrypted with a customer specific encryption key and stored in the database alongside the original log record records are audited periodically kron pam recalculates the stored data's hash value and compares it to the previously stored encrypted hash if the values match, the record is verified as unchanged if they differ, it indicates tampering through this design, the system provides a verifiable audit trail where log integrity can be continuously validated beyond this tamper evident mechanism, kron pam also enforces strict communication and access control policies to protect the database itself internal applications communicate with the database exclusively over tls encrypted connections, ensuring that all data transmitted between components is protected against interception or modification in transit additionally, database access is blocked by default for any resources other than authorized internal applications this layered approach ensures that while the hashing mechanism verifies the integrity of logs, the secure communication and access controls minimize opportunities for unauthorized access to the database