📄️ Usage Impact of Agent Deployment
This topic discusses the resource impact on a host when a Lacework agent is deployed for workload security.
📄️ Configure Linux Agent Behavior in config.json File
If you run the install.sh script to install the Lacework Linux agent on a machine, the script creates a config.json file in the /var/lib/lacework/config directory. You can add properties to the config.json file to alter the agent behavior as described below.
📄️ Agent Access Tokens
To connect to the Lacework application, Lacework agents require an agent access token. Lacework also provides scripts and configuration files to facilitate deployment, which includes the token.
📄️ Agent Administration
Start, Stop, or Restart Lacework Agent
📄️ eBPF Support
Overview
📄️ Mismatch Between Docker and Machine Hostnames
There is a limitation in Docker runtime which prevents running containers from being notified when Docker updates the hostname.
📄️ Add Agent Tags
In addition to importing AWS, Azure, and GCP tags, local tags can be added to agents. Agent tags can be very helpful for security teams as they provide better search and filtering capabilities. For example, tags can be used to identify critical assets and filters can be used to review the assets or applications running on these assets. Native AWS tags can also be used to organize data, but a fixed AWS tag schema may already be in place, preventing the security team from making changes.
📄️ How Lacework Derives the Kubernetes Cluster Name
When you deploy the Lacework agent in your Kubernetes environment, the list of Kubernetes clusters in which the agent is deployed is displayed in the Kubernetes dossier in the Lacework Console.
📄️ View K8s Clusters or Node Types in Lacework Console
The filters in the Lacework Console show the list of Kubernetes clusters and namespaces active during the time window selected. If a Kubernetes cluster is selected, the list of namespaces is updated for that cluster and vice versa.
📄️ Change Agent Resource Installation Limits on K8s Environments
This article discusses how to change the CPU/memory installation limits for Kubernetes-based environments where the Lacework agent is deployed as a daemonset (pod/container).
📄️ Agent Server URL
The default endpoint that the agent communicates with is and the default region is US.
📄️ Run Agent as Non-Root User
This topic describes functionality that is currently in beta.