Lacework-cli

Lacework CLI is a command-line interface for managing the Lacework cloud security platform from your terminal or scripts.

  • Security
  • Tools & Utilities
Lacework CLI is a command-line interface for managing the Lacework cloud security platform from your terminal or scripts. It wraps the platform's public APIs to let you authenticate, query security data, and run routine configuration or automation tasks. It suits security engineers and home-lab admins who prefer scripting or batch workflows over the web console.

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.

14/100 Low

Maintained
0last commit 861 days ago
Popular
2618 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
No data
Security check
152 serious findings, 20 minor, CI, tests, OpenSSF Scorecard 3.8/10

Based on 4 of 5 factors.

GitHub stars
18
Open issues
5
Last commit
2024-07-12
Latest release
v4.1.0
License
MIT
Activity
stale

Checked yesterday - source: GitHub (lacework/python-sdk)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

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

First-install notes

  • Install the Python SDK Run pip3 install laceworksdk so your Python environment has the Lacework library. Without it, code that starts with from laceworksdk import ... will not work. source
  • Use your default CLI profile If the Lacework CLI is installed and configured, start the Python client with LaceworkClient() so it reads the default profile from your ~/.lacework.toml settings file. This keeps account secrets out of your code and points the SDK at the right Lacework account. source
  • Optional notebook container For a ready-made Jupyter notebook setup, run docker-compose pull to download the packaged container and docker-compose up -d to start it in the background. This saves you from installing the notebook's Python packages yourself. source
  • Docker image Deploy from the official Docker image; arm and arm64 variants are both published. source

Fetched 2 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How can I quickly identify running hosts that do not have the Lacework agent installed?

Use the Lacework CLI to pull an inventory of running hosts that do not have the Lacework agent installed.

What should I verify when troubleshooting Lacework IaC in GitLab?

Ensure that the GitLab prerequisites are in place for either the SaaS or self-hosted GitLab variation.

How can the Lacework Python client use the existing Lacework CLI configuration?

If the Lacework CLI is installed and configured, starting the Python client with LaceworkClient() reads the default profile from the user's ~/.lacework.toml settings file.

What can the Lacework CLI Docker image be used for?

It can be used to manage compliance reports, external integrations, vulnerability scans, and other operations.

Answers sourced from community.fortinet.com, community.fortinet.com, github.com, hub.docker.com

Community

Collected 49 days ago - public community threads