While debugging a Meraki integration, a developer enables a ‘log everything’ mode that prints Authorization headers and API keys. What makes that logging strategy unsafe?
Select an answer to reveal the explanation.
Short Explanation
Logging a Meraki key is like taping the vault combination to the incident whiteboard. Redact tokens and secret payloads—debug volume is never an excuse to spill credentials.
Full Explanation
An effective logging strategy never writes authorization headers, refresh tokens, or secret-store payloads into log streams. ‘Debug everything’ that prints API keys creates a durable leak surface across collectors and backups. Redaction is a logging concern distinct from which vault product stores the secret.