When scans run
Workload scanning has no schedule of its own. After each project’s posture scan completes, whether scheduled or started withScan now, Plerion starts a workload scan run for that project covering every enabled workload type. On the default daily schedule that means one workload scan per project per day.
Before enumerating anything, each run checks four organization policy constraints against the scanning project. A blocking result fails the run for that project rather than producing a silent empty result. The run shows as failed on the project’s Workload scans tab, and the constraint that blocked it is recorded in Plerion’s logs. See Prerequisites for the constraints and what to change.
Each run’s status (in progress, completed, failed, or timed out) appears on the project’s Workload scans tab. If any scanner VM in a run fails, the whole run is recorded as failed, even if other targets in it were scanned.
Compute Engine instances
Snapshot the boot disk
Create a scan disk in the scanning project
Boot a scanner VM
pln-public-artifacts, image family plerion-appliance), which already has the scanning toolchain installed. Otherwise, it boots Google’s public Ubuntu 22.04 image and installs a checksum-pinned scanning toolchain at startup. Scanning works the same way regardless of which image it boots from; the pre-built image only makes scans start faster. One scanner VM handles up to 10 scan targets in a run.Scan
Upload results
Clean up
RUNNING or TERMINATED (stopped) state are scanned, and only their boot disk is scanned.
Compute Engine custom images
A custom image has no running disk to snapshot, so Plerion creates the scan disk directly from the image in the scanning project and skips the snapshot step. Everything else matches the instance flow above: same scanner VM, same read-only attach, same upload, and cleanup deletes the disk and VM. Nothing is created in the project that owns the image. Plerion scans every custom image a project owns that is in theREADY state, whether or not anything has booted from it, so a golden image is checked before your fleet is built from it. Findings attach to the image itself and are kept separate from any instance booted from it, because an instance can diverge from its image the moment it is patched.
A custom image is a global resource, so it has no region to match. Plerion runs the scan in the first region listed in your Workload regions setting. If that setting is empty, it uses a region the same project’s instance scans already use. Otherwise, it uses us-central1.
Compute Engine managed instance groups
A managed instance group can run hundreds of identical members, so Plerion samples instead of scanning each one.List the group's members
Skip GKE node pools
goog-gke-node label belongs to a GKE node pool. Plerion skips it at the group level. Its nodes stay covered as ordinary Compute Engine instances.Group members by boot image
Pick one sample per image
Scan each sample and merge
Cloud Run services and Cloud Functions (2nd gen)
A Cloud Run service runs a container image, and a 2nd gen function is a Cloud Run service underneath, so both are scanned the same way. The image for a 2nd gen function is the one Google built when it deployed the function, stored in thegcf-artifacts repository in your project.
Resolve the serving image digest
:latest is never trusted. Every container in the revision, including sidecars, is scanned.Run a Cloud Run job in the scanning project
plerion-scan-artifact-<region>), passing the digest as a per-execution override. The job runs as the artifact-scanner service account, with 1 vCPU and 2 GiB of memory, and fetches its own registry token from the metadata server at runtime. No credential is written into the job definition.Pull and scan
Upload results and delete the execution
Cloud Functions (1st gen)
A 1st gen function is deployed from a source archive, not a container image, so Plerion downloads that source and scans it.Ask Google Cloud for a download link
Download and unpack in a Cloud Run job
plerion-scan-source-<region>) downloads the archive and unpacks it inside the job’s container, which has no persistent disk. The job runs as the source-scanner service account, with 1 vCPU and 4 GiB of memory. Archives over 100 MB compressed or 500 MB unpacked are skipped.Scan
Upload results and delete the execution
Vertex AI Agent Engine agents
An agent deployed from a container image is scanned like a Cloud Run service: Plerion resolves the image’s digest, and the standing image scan job pulls it from Artifact Registry as the artifact-scanner service account. An agent deployed from a staging bucket is scanned from its code.Read the agent's deployment
requirements.txt and dependency archive in your staging bucket. The pickle file the spec also names is never read.Run a Cloud Run job in the scanning project
Download, unpack and scan
Upload results and delete the execution
The identities involved
Encrypted disks and images
- Customer-managed encryption keys (CMEK): the snapshot keeps the source disk’s key, but the scan disk Plerion creates in the scanning project uses Google-managed encryption. Plerion creates it without your key. For the minutes the scan disk exists, Google’s key protects it rather than yours. It is deleted at the end of the scan. The same applies to a scan disk created from a CMEK-protected custom image.
- Customer-supplied encryption keys (CSEK): Plerion has no way to supply your key, so CSEK-encrypted disks are skipped.
Cleanup and the sweeper
Every resource Plerion creates for a scan is labeledowner=plerion, plus the tenant, integration, and execution that own it. Snapshots, scan disks, and scanner VMs are also named with a plerion-scan- prefix. Cleanup runs at the end of every scan, whether it succeeded or not. A separate sweeper runs every hour in the scanning project and removes any Plerion-labeled resource older than 24 hours, so an interrupted scan can’t leave resources behind for long. Because the scanning project is yours, you can also delete any leftover resource yourself.