avatar

Google SecOps

@GoogleSecOps
4 followers1,217 downloads359 copies1 like18,019 views

727 detections

This rule detects suspicious command-line activity indicative of credential access or reconnaissance, as outlined in a CISA 'Living off the Land' report. Specifically, it looks for commands that attempt to list SSH known hosts, access Firefox profiles, execute Mimikatz, query OpenSSH or RealVNC registry keys, or save SAM/SYSTEM registry hives. While individual commands might be benign, their combined presence or repeated execution could signal malicious intent.
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
1 year ago
0039
This rule detects when a known malicious file, identified by its SHA256 hash through VirusTotal relationships, attempts to contact a domain that VirusTotal also associates with that file. It correlates DNS query events with VirusTotal intelligence to identify suspicious network communications originating from potentially compromised systems.
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
1 year ago
1039
This rule detects attempts to extract the ntds.dit file, which contains Active Directory credential information, using `wmic` in conjunction with `vssadmin.exe` or `ntdsutil.exe`. It also identifies the creation of `.dit` files in temporary directories and specific ESENT application event logs associated with NTDS database activity. This activity is indicative of credential dumping, a common post-exploitation technique.
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
1 year ago
0038
This rule detects the creation of scheduled tasks on Windows systems using the `schtasks.exe` command-line utility. It specifically looks for process launch events where the command line contains `schtasks` and `/create` (case-insensitive). This activity is often used by adversaries for persistence, privilege escalation, or lateral movement.
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
1 year ago
0036
This rule detects the use of PowerShell to enumerate successful logon events (Event ID 4624) from the security event log on a Windows host. It specifically looks for command-line executions containing 'Get-EventLog', 'security', and '-instanceid 4624'. This activity is often performed during the reconnaissance phase by adversaries to understand user activity on a system.
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
1 year ago
0036
This rule detects DNS queries to domains identified as Command and Control (C2) infrastructure within a Threat Intelligence (TI) feed, specifically MISP. It correlates DNS events with MISP data where the entity type is 'DOMAIN_NAME' and the threat summary indicates 'C2 domains'. The rule is designed to identify potential C2 communications from internal hosts.
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
1 year ago
0036
This rule detects when a user is added to an administrative role within Office 365. While adding users to administrative roles is not inherently malicious, it is a sensitive action that warrants validation due to the elevated privileges granted. The rule specifically looks for the 'Add member to role.' event type within Office 365 and requires the role to be present in a predefined watchlist of sensitive roles.
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
1 year ago
2035
This rule detects outbound network connections to IP addresses that are identified as Indicators of Compromise (IOCs) within a threat intelligence platform, specifically MISP. It filters out connections to RFC1918 private IP ranges to reduce false positives. The rule correlates network connection events with ingested MISP data to identify malicious communication.
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
1 year ago
0035
This rule detects web traffic to a recently expired domain followed by the creation of an executable (.exe) file on the same host. It correlates network access events with WHOIS data to identify expired domains and then looks for subsequent file creation events where the file path ends with '.exe'. The file creation must occur after the network access event on the same principal hostname.
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
1 year ago
0035
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.
avatar
Google SecOps@GoogleSecOps
avatar
Google SecOps Detection Rules
1 year ago
0034
Page 16 of 73