Security Command Center performs [agentless](https://docs.cloud.google.com/security-command-center/docs/compute-engine-threats.md.txt#runtime) and [log-based](https://docs.cloud.google.com/security-command-center/docs/compute-engine-threats.md.txt#log-based)
monitoring of Compute Engine resources. For recommended responses to these
threats, see [Respond to Compute Engine
threat findings](https://docs.cloud.google.com/security-command-center/docs/respond-compute-engine-threats).

## Agentless monitoring finding types

The following agentless monitoring detections are available with
[Virtual Machine Threat Detection](https://docs.cloud.google.com/security-command-center/docs/concepts-vm-threat-detection-overview.md.txt):

<br />

- [`Defense Evasion: Rootkit`](https://docs.cloud.google.com/security-command-center/docs/findings/threats/defense-evasion-rootkit.md.txt)
- [`Defense Evasion: Unexpected ftrace handler`](https://docs.cloud.google.com/security-command-center/docs/findings/threats/defense-evasion-unexpected-ftrace-handler.md.txt)
- [`Defense Evasion: Unexpected interrupt handler`](https://docs.cloud.google.com/security-command-center/docs/findings/threats/defense-evasion-unexpected-interrupt-handler.md.txt)
- [`Defense Evasion: Unexpected kernel modules`](https://docs.cloud.google.com/security-command-center/docs/findings/threats/defense-evasion-unexpected-kernel-modules.md.txt)
- [`Defense Evasion: Unexpected kernel read-only data modification`](https://docs.cloud.google.com/security-command-center/docs/findings/threats/defense-evasion-unexpected-kernel-read-only-data-modification.md.txt)
- [`Defense Evasion: Unexpected kprobe handler`](https://docs.cloud.google.com/security-command-center/docs/findings/threats/defense-evasion-unexpected-kprobe-handler.md.txt)
- [`Defense Evasion: Unexpected processes in runqueue`](https://docs.cloud.google.com/security-command-center/docs/findings/threats/defense-evasion-unexpected-processes-in-runqueue.md.txt)
- [`Defense Evasion: Unexpected system call handler`](https://docs.cloud.google.com/security-command-center/docs/findings/threats/defense-evasion-unexpected-system-call-handler.md.txt)
- [`Execution: cryptocurrency mining combined detection`](https://docs.cloud.google.com/security-command-center/docs/findings/threats/execution-cryptocurrency-mining-combined-detection.md.txt)
- [`Execution: Cryptocurrency Mining Hash Match`](https://docs.cloud.google.com/security-command-center/docs/findings/threats/execution-cryptocurrency-mining-hash-match.md.txt)
- [`Execution: Cryptocurrency Mining YARA Rule`](https://docs.cloud.google.com/security-command-center/docs/findings/threats/execution-cryptocurrency-mining-yara-rule.md.txt)
- [`Malware: Malicious file on disk`](https://docs.cloud.google.com/security-command-center/docs/findings/threats/malware-malicious-file-on-disk.md.txt)
- [`Malware: Malicious file on disk (YARA)`](https://docs.cloud.google.com/security-command-center/docs/findings/threats/malware-malicious-file-on-disk-yara.md.txt)

<br />

## Log-based finding types

The following log-based detections are available with
[Event Threat Detection](https://docs.cloud.google.com/security-command-center/docs/concepts-event-threat-detection-overview.md.txt):

<br />

- [`Brute force SSH`](https://docs.cloud.google.com/security-command-center/docs/findings/threats/ssh-brute-force.md.txt)
- [`Impact: Managed Instance Group Autoscaling Set To Maximum`](https://docs.cloud.google.com/security-command-center/docs/findings/threats/yl2-mig-autoscaling-set-to-max.md.txt)
- [`Lateral Movement: Modified Boot Disk Attached to Instance`](https://docs.cloud.google.com/security-command-center/docs/findings/threats/modify-boot-disk-attach-to-instance.md.txt)
- [`Lateral Movement: OS Patch Execution From Service Account`](https://docs.cloud.google.com/security-command-center/docs/findings/threats/yl2-os-patch-execution-from-service-account.md.txt)
- [`Persistence: GCE Admin Added SSH Key`](https://docs.cloud.google.com/security-command-center/docs/findings/threats/gce-admin-add-ssh-key.md.txt)
- [`Persistence: GCE Admin Added Startup Script`](https://docs.cloud.google.com/security-command-center/docs/findings/threats/gce-admin-add-startup-script.md.txt)
- [`Persistence: Global Startup Script Added`](https://docs.cloud.google.com/security-command-center/docs/findings/threats/yl2-global-startup-script-added.md.txt)
- [`Privilege Escalation: Global Shutdown Script Added`](https://docs.cloud.google.com/security-command-center/docs/findings/threats/yl2-global-shutdown-script-added.md.txt)

<br />

The following log-based detections are available with
[Sensitive Actions Service](https://docs.cloud.google.com/security-command-center/docs/concepts-sensitive-actions-overview.md.txt):

<br />

- [`Impact: GPU Instance Created`](https://docs.cloud.google.com/security-command-center/docs/findings/threats/sensitive-action-gpu-instance-created.md.txt)
- [`Impact: Many Instances Created`](https://docs.cloud.google.com/security-command-center/docs/findings/threats/sensitive-action-many-instances-created.md.txt)
- [`Impact: Many Instances Deleted`](https://docs.cloud.google.com/security-command-center/docs/findings/threats/sensitive-action-many-instances-deleted.md.txt)

<br />

## What's next

- Learn about [Virtual Machine Threat Detection](https://docs.cloud.google.com/security-command-center/docs/concepts-vm-threat-detection-overview.md.txt).
- Learn about [Event Threat Detection](https://docs.cloud.google.com/security-command-center/docs/concepts-event-threat-detection-overview.md.txt).
- Learn about [Sensitive Actions Service](https://docs.cloud.google.com/security-command-center/docs/concepts-sensitive-actions-overview.md.txt).
- Learn how to [respond to Compute Engine
  threats](https://docs.cloud.google.com/security-command-center/docs/respond-compute-engine-threats).
- Refer to the [Threat findings index](https://docs.cloud.google.com/security-command-center/docs/threat-findings-index.md.txt).