The quietest exposure.
WHAT LOGS ACCUMULATE
Network addresses Identifiers Request contents, sometimes Error details containing user input Email addresses
WHY IT MATTERS
Logs are widely readable, long retained, and rarely governed.
WHAT TO NEVER LOG
Passwords Tokens and keys Payment details Full request bodies containing personal data
WHY FULL BODIES SPECIFICALLY
It is the commonest accidental capture.
WHAT TO DO ABOUT ERRORS
Log the error and an identifier, not the data that caused it.
WHAT TO LOG INSTEAD OF DETAILS
A reference that lets you look it up where appropriate.
WHAT TO SET
Retention per log type, deliberately.
WHY
Logs default to indefinite, and grow enormously.
WHAT TO RESTRICT
Who can read logs.
WHY
They frequently contain more personal data than the application's own screens.
WHAT TO CHECK
What your logs actually contain.
HOW
Read a sample, looking for personal data.
WHAT THAT USUALLY REVEALS
More than expected.
WHAT TO DO ABOUT DELETION REQUESTS
Consider whether logs hold the person's data, and how you will address it.
WHAT MOST ORGANISATIONS CONCLUDE
That short retention resolves it.
WHAT TO DOCUMENT
Log retention and access, in the inventory.
