-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Snowflake Data Exfiltration CR #1257
Conversation
😱 [INFO][root]: ignoring file dependabot.yml |
@arielkr256 - does this require a customer to perform a SF share of 'SNOWFLAKE.ACCOUNT_USAGE.QUERY_HISTORY' before running these? |
@casey-r-hill for SF connected yes, similar to this guidance. For SaaS it should already have those permissions. |
* Update Action versions; use SHAs * Add dependabot.yml to keep Actions updated * Update PAT to 0.49.0
snowflake data exfiltration
8f907e6
to
eecb93c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
snowflake data exfiltration
Background
In April 2024, Mandiant received threat intelligence on database records that were subsequently determined to have originated from a victim’s Snowflake instance. Mandiant notified the victim, who then engaged Mandiant to investigate suspected data theft involving their Snowflake instance. During this investigation, Mandiant determined that the organization’s Snowflake instance had been compromised by a threat actor using credentials previously stolen via infostealer malware. The threat actor used these stolen credentials to access the customer’s Snowflake instance and ultimately exfiltrate valuable data. At the time of the compromise, the account did not have multi-factor authentication (MFA) enabled. https://cloud.google.com/blog/topics/threat-intelligence/unc5537-snowflake-data-theft-extortion/
Changes
Testing