Solum/Logging
< Solum
Revision as of 21:27, 9 December 2013 by Paul Montgomery (talk | contribs)
In order to prevent accidental leakage of confidential information to unauthorized Solum users, there are some guidelines to assist in isolating this confidential data for easy/accurate filtering on the back end log management tools:
- Unless the developer is sure that an exception will never contain confidential information, exceptions should be identified as confidential. This has historically been especially problematic with database exceptions which may contain real field data.
- Recommend parsing the specific exception or error and providing an abstracted/safe version back to the user
- Never log plain text passwords
- Minimize Personally Identifiable Information (PII) logging where possible
- Avoid logging local server state which may provide hints to attackers (examples: file paths, code file names, user account names)
- If a user identifier (tenant/project ID) is not present in the log record or does not match the current authenticated user, do not show this log data to the user
- If a Solum configuration option causes the system to enter a potentially less secure state, log a message to this effect for operators to see
