.svg?alt=media&token=0f6df7c7-5b98-4a62-98b8-a54e38a8329e){kind=logo}
Agent Management
Setup and management of agents such as OSSEC, ClamAV for anti-virus, CrowdStrike, and so forth
Last updated
Setup and management of agents such as OSSEC, ClamAV for anti-virus, CrowdStrike, and so forth
Last updated
© DuploCloud, Inc. All rights reserved. DuploCloud trademarks used herein are registered trademarks of DuploCloud and affiliates
Agents are typically required to be installed on virtual machines to collect data and send it to their respective controlling software running in a central location. For example, OSSEC is the agent for the SIEM Wazuh. CrowdStrike and Laceworks all have their respective agents. ClamAV anti-virus can also be considered an agent whose results we collect and send to Wazuh.
DuploCloud platform provides seamless installation and management of these agents. There are 3 types of agents that we install:
Docker-based agents
The Kubernetes DaemonSet runs in all or a subset of hosts in a cluster. Typically, these containers are launched with privileged access over the host operating system
Containers that run on all or a subset of hosts are orchestrated through DuploCloud's built-in container orchestration. Typically, these containers are launched with predefined access to the host operating system.
Non-Docker VM agents are Linux packages or Windows services installed and baked in virtual machine images before launch. They can also be installed via user data.
Create an Agent Type. Each vendor or agent software is considered a type. For example, OSSEC, ClamAV, Laceworks, and Crowdstrike are different agent types. To add a new agent type, navigate to Security -> Agents and click Add. The Add Security Agent pane displays. Enter the Agent Name and click Create.
Create an agent deployment. Under the desired Agent tab, Add a deployment to deploy the agent to the Hosts. You must deploy at least one agent per Kubernetes cluster. You can deploy on all hosts in a Kubernetes cluster or on all Hosts for a specific Tenant. Deploying on all hosts for one Tenant is useful for certain Kubernetes clusters or DuploCloud Infrastructures where you have Tenants on which you don't want specific agents to be run.
Behind the scenes, this deployment is just a regular Kubernetes DaemonSet deployment or a built-in container orchestration deployment within a tenant, as documented here.
When deploying or managing containers and cloud services, it is essential to ensure the security and integrity of your systems. Virus scans play a crucial role in this process by checking for malicious software, vulnerabilities, and any security threats within the defined scope. This includes all areas and items the virus scanning process covers during its operation, ensuring the safety of your network and systems.
You can create multiple deployments for multiple tenants. In the case of Kubernetes-based container orchestration, as against DuploCloud built-in orchestration, you can target all nodes in the cluster with just one deployment. The following are the fields in the Update Security Agent Deployment page:
Name is a desired name to track the deployment.
Cluster is the infrastructure name and is the maximum scope of deployment.
Host Tenant is the tenant namespace where the daemon set will be deployed.
Deployment Type is either a K8s DaemonSet or Docker Native for built-in container orchestration.
Once deployed, you can view the deployed instances of the agents under their respective agent tabs, as shown below:
