4 ms·

In the past, I've seen logs monitored for high-entropy strings that could be API keys or passwords. However, in a NoSQL/UUID-using environment, this could be re

• techdragon 9y ago
  Log line -> high entropy check -> false positive uuid check -> alerts I’m not seeing how it would be a challenge in a uuid based environment, unless there’s a nuanced detail I’m missing.
• maddyboo 9y ago
  Perhaps implement some type of “password canary” - some type of test account(s) with known high-entropy passwords. Have an automated system send periodic login requests (or any other requests which contain sensitive information that shouldn’t be logged) for this account, and have another system which searches log files for the password. If it’s ever found, you know something is leaking.
  • cm2187 9y ago
    And regularly check for that password on haveibeenpwned and other breached password databases.
    • AstralStorm 9y ago
      Do you trust the database to not have been hijacked to capture checked passwords? A better advice is to delete accounts you don't use. If not possible (illegal in EU now) scramble private data and the password. Download the databases yourself and check them locally. Changing passwords regularly also limits the damage.