ISC2 Certified Secure Software Lifecycle Professional (CSSLP) Practice Question

Hashing (ideally with a salt) replaces each session token with an irreversible value before it is written to disk, so the token itself can no longer be replayed if logs are exposed. Because the same token always hashes to the same value during its lifetime, analysts can still correlate related events. Simply Base64-encoding the token offers no real protection because it is easily reversible. Encrypting the log file or its storage medium does add a layer of defense, but insiders or processes with decryption access could still read the raw tokens, and the application would still write secrets to memory and disk. Extending the retention period does nothing to reduce disclosure risk and may increase it by keeping sensitive data longer.