> For the complete documentation index, see [llms.txt](https://docs.cybaops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybaops.com/getting-started/onboarding/agent-deployment.md).
# Setting Up CybaAgent
*Install one agent for visibility, scanning and protection*
CybaAgent is the small program you install on each of your Windows, macOS and Linux devices. One install gives you full asset details, built-in vulnerability scanning and endpoint detection and response (EDR), so there's nothing else to deploy. Installing it is one of the first onboarding steps, because most of what CybaOps knows about your devices comes from the agent.
***
## Why Install CybaAgent
A device without the agent is a blind spot. Installing CybaAgent everywhere gives you a complete, up-to-date picture with almost no effort after the first install.
* **Asset data.** Each device appears in Asset Manager by itself, with its operating system, hardware, network details and security settings, and stays up to date. You always know what you have and how it's configured.
* **Vulnerability scanning.** Scanning installs with the agent: CybaAgent sets up the Qualys Cloud Agent for you and keeps it running, checking each device up to every 4 hours. The results are pulled into CybaOps and linked to the device, so you can see the impact straight away and fix the most important issues first. See [Vulnerability Scanning Requirements](/identify-and-protect/vulnerability-management/vulnerability-scanning-requirements.md).
* **EDR.** CybaAgent is the EDR part of CybaOps, working alongside Microsoft Defender to watch for suspicious activity on the device and help stop attacks early.
Read more in [CybaAgent](/identify-and-protect/asset-manager/cybaagent.md).
***
## What You Need
* **A supported device.** Windows 10 and 11 or Windows Server 2016 and later, macOS 10.13 (High Sierra) and later, or any Linux distribution that uses systemd, such as Ubuntu, Debian, Red Hat Enterprise Linux and Fedora. Intel or AMD (amd64) and ARM (arm64) processors are supported on all of them.
* **Administrator rights** on each device, or `sudo` on macOS and Linux, so the agent can install itself as a service.
* **Access to Asset Manager** in CybaOps, where you download the agent and copy your install command. If **Deploy Agent** is greyed out, ask your tenant admin.
* **Outbound HTTPS on port 443** to your CybaOps address, for example `cybaverse.cybaops.com`, and to `qagpublic.qg1.apps.qualys.co.uk` for vulnerability scanning. No inbound ports are needed.
Check the full list in [Requirements](/identify-and-protect/asset-manager/cybaagent/requirements.md) before you start, because a few minutes now saves a failed install later.
***
## Choose How to Install
* **One device at a time:** follow [Deploying CybaAgent](/identify-and-protect/asset-manager/cybaagent/deploying-cybaagent.md) to install from the command line on Windows, macOS or Linux in a few minutes.
* **Many devices at once:** follow [Deploying CybaAgent with Intune](/identify-and-protect/asset-manager/cybaagent/deploying-cybaagent-with-intune.md) to push the agent to your Windows devices through Microsoft Intune.
Once the agent is running, it keeps itself up to date. To check its health, restart it or remove it, see [Managing CybaAgent](/identify-and-protect/asset-manager/cybaagent/managing-cybaagent.md).
***
## Next steps
* [Requirements](/identify-and-protect/asset-manager/cybaagent/requirements.md): Check your devices and network are ready before you install.
* [Deploying CybaAgent](/identify-and-protect/asset-manager/cybaagent/deploying-cybaagent.md): Install the agent on your first device.
* [Deploying CybaAgent with Intune](/identify-and-protect/asset-manager/cybaagent/deploying-cybaagent-with-intune.md): Roll the agent out to all your Windows devices at once.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.cybaops.com/getting-started/onboarding/agent-deployment.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.