Are root privileges required for installing a Lacework agent?
Yes, you must install the Lacework agent using root privileges:
- Log in as root and run the installer
- Run the installer with sudo—Running a command with just the sudo prefix invokes the command with root privileges.
During the startup of the Lacework agent, the agent checks that the agent binary and configuration files are owned by root.
Does the Lacework agent have any package dependencies?
No. The Lacework agent has no package dependencies. When the Lacework agent package is installed, Lacework does not install any shared libraries. The Lacework agent is a statically-linked binary that uses the following libraries:
linux-vdso.so.1 /lib/x86_64-linux-gnu/libdl.so.2 /lib/x86_64-linux-gnu/libpthread.so.0 /lib/x86_64-linux-gnu/libc.so.6 /lib64/ld-linux-x86-64.so.2
Does the Lacework agent support containers/microservices?
Yes, a Lacework agent runs in the following environments:
- Agent runs as a Docker container—For more information, see Install on a Dockerized Host. For Docker containers, the Lacework agent must be run as a privileged container.
- Agent is deployed across a Kubernetes cluster as a daemonset—For more information, see Deploy Using Kubernetes.
What is a Pod?
A Pod defines a running process in Kubernetes and is the smallest entity that can be created or deployed in Kubernetes. A pod is a collection of one or more running containers. For more information, see Pod Overview. A Lacework agent can be deployed in Kubernetes.
What is the impact of the Lacework agent on CPU?
The number of connections made by the host determines the impact on the individual system. However, for an average workload, Lacework has observed CPU usage of 1-3% but the CPU usage varies depending on the number of connections. You can optionally configure a hard limit for CPU usage of the agent. For more information, see Configure Agent Behavior in config.json File.
How much disk size does the agent use on a machine?
The agent uses approximately 250 MBytes of disk space on a machine.
How much memory does the Lacework agent consume?
Lacework has observed an average of 250-300 Mbytes of memory usage but the memory usage can vary depending on the workload on the system, such as the number of network connections, running applications, running containers, the amount of metadata processing, etc. Lacework also has guardrails on the Lacework agent to prevent the agent from consuming an unlimited amount of memory and CPU on a system. A system is where the agent process is running, either a Docker container or as part of a Kubernetes cluster, Virtual Machine or standalone machine.
You can optionally configure a hard limit for the memory usage of the agent. For more information, see Configure Agent Behavior in config.json File. The limits configured in the config.json file also apply to agents hosted on containers. In addition to the limits specified in the config.json file, you can also use the Docker command line (docker run) or a Kubernetes orchestration file (k8s) to set upper bound limits in containers.
What is the impact of the Lacework agent on Network resources?
The number of network connections made by the host determines the impact on the individual system. Lacework has observed data usage of 1Kbps-2Kbps in current deployments which translates to around 100-150MB per system per day of data. A system is where the agent process is running, either a Docker or Kubernetes container, Virtual Machine or standalone machine.
Does the Lacework agent work in the kernel or user space?
The Lacework agent works in the user space in a passive mode. There is no dependency on IP tables and the agent does not slow down containerized applications and network connections.
How often does the Lacework agent collect data?
Lacework is a continuous monitoring system, that collects and monitors metadata of all the processes associated with a network activity. The Polygraph is computed every hour.
How is the Lacework agent updated?
The Lacework agent is automatically updated when a new version is available. Contact Lacework Support to alter the process of updating of the agent.
How can I deploy the agent?
You can deploy the agent with any configuration management tool like Chef, Puppet, Ansible, or Salt. You can also use the installation script provided by Lacework for these configuration management tools.
For single host installations, you can also use the Lacework installation script or embed the Lacework agent in a base image or AMI.
You can also install from Debian-based (APT) and RPM-based (YUM) repositories.
For more information, see Installations Options in Lacework for Workload Security.
Does the Lacework agent work with a proxy?
Lacework agent supports a proxy configuration. If required, the agent can be configured to use a network proxy by adding proxy information to a configuration file or by creating a https_proxy environment variable. For more information about configuring a Lacework agent to use a proxy, see Required Connectivity, Proxies & Certificates.
What Linux versions are supported by Agent?
The agent requires minimal system resources and runs on most 64-bit Linux distributions. For the supported agent Linux operating systems, see Supported Operating Systems.
What kind of connectivity is needed by Agent?
To be able to communicate with Lacework, the installed agents must be allowed to reach specific URLs. For more information, see Required Connectivity, Proxies & Certificates.
What authentication methods are used by the Lacework Agent to connect to Lacework Service?To connect to the Lacework cloud, Lacework agents require an active access token. If you have a Lacework account, an agent access token is automatically generated for you. In addition, you can create and disable agent access tokens. For more information, see Agent Access Tokens.
Is the data encrypted when in transit from Agent?
Lacework agent encrypts all data when it is in transit to our SAAS service. The data is encrypted over https with port 443 using TLS 1.2.
Does Agent support the ability to add custom Tags?
In addition to importing AWS tags, local tags can be added to agents. For more information, see Add Agent Tags.