Google SecOps
@GoogleSecOps4 followers1,217 downloads379 copies1 like18,177 views
758 detections
Filters
Last updated
All Time
Detection languages
756
2
Categories
189
188
109
81
77
Platforms
257
198
122
112
67
Products / Services
186
94
93
69
52
MITRE Techniques
237
181
109
95
79
CVEs
4
4
This rule identifies process and file creation events where the associated file's SHA256 hash is present in Google Safe Browsing data and has been observed for a duration greater than 7 days (604,800 seconds). This long observation period for a Safe Browsing-flagged hash could indicate persistent malware or a file that has been present on systems for an extended time before being flagged or detected.
This rule detects when a network connection is made to a domain that has expired. It leverages WHOIS data to identify domains whose expiration time is before the event timestamp. The rule specifically looks for HTTP network events and joins them with WHOIS information to identify access to recently expired domains. This could indicate access to potentially malicious infrastructure, as expired domains can be re-registered by threat actors for nefarious purposes.
This rule detects the creation or launch of processes or files that match known Indicators of Compromise (IOCs) from a MISP instance and exhibit low prevalence (3 or fewer occurrences) over a 10-day rolling period. This combination suggests potentially malicious activity that is not widespread, indicating a targeted attack or early-stage malware.
This rule detects when a file, identified by its SHA256 hash, initiates a network connection to an IP address that is identified as a Tor exit node. The rule leverages VirusTotal relationships to link the file hash to the contacted IP address and Google Cloud Threat Intelligence (GCTI) Feed to identify Tor exit nodes. The risk score is increased if the Tor IP's geolocation is in certain countries (Cuba, Iran, North Korea, Russia, Syria).
This rule detects the use of 'net use' commands to connect to Windows administrative shares (C$, ADMIN$, IPC$) from a principal IP address associated with a Windows asset entity. It correlates process launch events with asset entity data, specifically looking for Windows machines within the 'Domain Computers' group. This activity can indicate lateral movement or remote access by an adversary.
Detects DNS queries to domains classified as 'Gaming Sites' within a MISP threat intelligence feed. This rule is designed to identify potential policy violations related to accessing unauthorized gaming websites.
This rule detects the creation or execution of files that have been identified as malicious by Google Safe Browsing. It correlates process launch or file creation events with a list of known malicious file SHA256 hashes provided by the Google Safe Browsing service, specifically looking for files categorized as 'SOFTWARE_MALICIOUS' with 'CRITICAL' severity.
This rule detects the creation or launch of processes or files that have a SHA256 hash matching an Indicator of Compromise (IOC) from MISP, specifically when the file is identified by VirusTotal as an MS Office DOCX file type. It correlates process/file events with threat intelligence data to identify potentially malicious activity involving weaponized documents.
Whoami Command Execution
YARA-L
Detects the execution of the 'whoami' command, which is frequently used by attackers post-exploitation to identify the current user's credentials and privileges. This activity is a common step in reconnaissance and privilege escalation phases of an attack.
This rule detects a sequence of events indicating the creation of a user account, a successful login by that user, and the subsequent deletion of the same user account within a 4-hour timeframe. This pattern is often indicative of an adversary creating temporary accounts for malicious activities, using them, and then removing them to cover their tracks or evade detection. The rule specifically targets Windows login events (event code 4624).
Page 20 of 76