Analytic for Signal Desktop sensitive data access #5220
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary of the Pull Request
Adds analytic for detecting access of Signal Desktops sensitive files containing message data, and key material used for encrypting- and decrypting said data. Multiple threat actors have targeted locally stored data in Signal, WhatsApp and Telegram in recent years.
See also: https://cloud.google.com/blog/topics/threat-intelligence/russia-targeting-signal-messenger/
Changelog
Example Log Event