Container Auto Scan

Container Auto Scan is a Lacework integration that automatically triggers vulnerability assessments for active containers, helping users detect security…

  • Security
  • Tools & Utilities
Container Auto Scan is a Lacework integration that automatically triggers vulnerability assessments for active containers, helping users detect security weaknesses without manual scans.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

28/100 Low

Maintained
0last commit 1334 days ago
Popular
2823 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
208 GB minimum RAM, runs on ARM
Security check
95no serious findings, CI, tests
GitHub stars
23
Open issues
1
Last commit
2023-03-28
Latest release
v1.1.2
License
MIT
Activity
stale

Checked 3 days ago - source: GitHub (lacework-dev/container-auto-scan)

Resources & Compatibility

Minimum requirements: 8 GB RAM, 4 CPU core(s). ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Install the app’s PHP helper first Run composer require league/container in the app’s main folder before first launch. This tells Composer, the PHP downloader, to fetch the toolkit the code relies on; without it, the app may fail because it can’t load its core parts. source
  • Prerequisites Requires a Lacework account and integrated container registries. source

Fetched 41 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I authenticate container-auto-scan when running it in Docker?

You can mount the local Lacework CLI configuration file into the container at /home/user/.lacework.toml. Alternatively, pass account, subaccount, API key, and API secret arguments, or use the standard Lacework CLI environment variables.

Can I force a new scan of containers that were already scanned recently?

By default, containers scanned within the previous day are skipped using a local scan cache. You can override that behavior with the --rescan flag.

What happens if my container registry is not integrated with Lacework?

The Inline Scanner can fall back and scan active containers that do not have an integrated container registry. It can also pull publicly accessible images through the local Docker daemon.

How do I tell it to scan only one registry instead of all integrated registries?

By default it enumerates all integrated container registries that can be scanned by Lacework. Use the --registry argument to override that and scan a specific registry.

How do I change the time window used to find active containers?

The default look-back period for active container repository and tag combinations is one day. You can change it with the --days or --hours arguments.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads