Armor Agent for Containers

Containers

Containers are a standardized unit or package of software that enables consistency when running applications from one environment to another. As more companies develop applications in the cloud or move platforms to microservices architecture, containers become a useful way to make that work happen. For more information on containers, please visit Docker's documentation.

Images

An image includes all the dependencies (such as frameworks) plus deployment and execution configuration to be used by a container runtime. Usually, an image derives from multiple base images that are layers stacked on top of each other to form the container's filesystem. An image is immutable once it has been created.

Registries

Registries inform the Armor Security Platform where to find your container images, and which repositories and tags are in-scope for vulnerability scanning.

Registry names do not reflect values from AWS, Azure, etc. Registry names in AMP are internal "friendly" names.

Connectors

Connectors give the Armor security platform permission to access your public cloud infrastructure. The connectors you configure for Container Security are different than connectors you may configure for other features such as Cloud Security Posture Management or Log Relay.

You will need one connector per public cloud registry you wish to eventually configure.

Sensors

A sensor is packaged and delivered as a Docker Image and can be deployed as a container alongside other application containers. The sensor automatically discovered images and containers on a deployed host and scans for vulnerabilities.

Sensor installation instructions are available here.

Vulnerabilities

Vulnerabilities are weaknesses that threat actors exploit to gain unauthorized access to computer systems. Once exploited, attackers can run malicious code, install malware and steal data.