> 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/qualys-macos.md).

# Qualys - MacOS

*<mark style="color:$info;">Installation on macOS</mark>*

This guide walks you through installing the Qualys Cloud Agent on a Mac. You'll run the
\
package installer first, then activate the agent from Terminal. The whole process takes
\
about 2–3 minutes.

### <mark style="color:$primary;">Before you Start</mark>

Make sure you have the following ready:

* An account on the Mac with administrator rights (you'll need to enter your password
  \
  during the install and for sudo).
* Access to CybaOps so you can open Asset Manager.
* A working internet connection.

## <mark style="color:$primary;">Step 1 — Download the Agent from Asset Manager</mark>

1. Sign in to CybaOps and open Asset Manager.
2. Click the Deploy Agent button in the top-right corner.
3. In the Deploy Agent window, set Select Agent to Qualys and Select Operating System to Mac.
4. Click Download Qualys and save QualysCloudAgent.pkg to your Downloads folder.

{% hint style="warning" %}
**Keep this window open: The Deploy Agent window shows the activation command with**
\
**your CustomerId and ActivationId pre-filled — you'll copy it in Step 3.**
{% endhint %}

## <mark style="color:$primary;">Step 2 — Install the Package</mark>

1. Open Finder and go to your Downloads folder.
2. Double-click QualysCloudAgent.pkg to launch the macOS installer.
3. Follow the prompts — click Continue, agree to the licence, then Install.
4. Enter your Mac login password when prompted to authorise the install.
5. When the installer reports success, click Close.

{% hint style="warning" %}
**If macOS blocks the package: If you see a warning saying the package can't be opened**
\
**because it's from an unidentified developer, open System Settings → Privacy & Security,**
\
**scroll to the Security section, and click Open Anyway next to the QualysCloudAgent.pkg**
\
**entry.**
{% endhint %}

## <mark style="color:$primary;">Step 3 — Activate the Agent</mark>

1. Open Terminal — through Applications → Utilities → Terminal, or by pressing Cmd + Space and typing Terminal.
2. Copy the activation command from the Deploy Agent window in CybaOps and paste it into Terminal. It will look like this, with your ActivationId in place of the placeholder:&#x20;

{% code overflow="wrap" %}

```
sudo /Applications/QualysCloudAgent.app/Contents/MacOS/qualys-cloud-agent.sh
CustomerId=4ced42b6-21b2-e6d5-80a3-bf1f6d2597f6 ActivationId=YOUR ACTIVATION CODE
ServerUri=https://qagpublic.qg1.apps.qualys.co.uk/CloudAgent/
```

{% endcode %}

3. Press Return. When prompted, type your Mac login password and press Return
   \
   again.

{% hint style="info" %}
**Tip: Always copy the command directly from Deploy Agent rather than typing it — that**
\
**way your activation code is guaranteed to be correct.**
{% endhint %}

{% hint style="info" %}
**About the password prompt: The cursor won't appear to move while you type your sudo**
\
**password — that's normal. The characters are being entered, just hidden.**
{% endhint %}

### <mark style="color:$primary;">What the Parameters Mean</mark>

* **CustomerId** — identifies your Qualys subscription. This is the same for every device in
  \
  your organisation.
* **ActivationId** — the unique activation key Qualys uses to register this device.
* **ServerUri** — the Qualys platform the agent reports into (UK platform in this case).

## <mark style="color:$primary;">Step 4 — Confirm it Installed</mark>

Terminal will show progress messages while the activation runs. When it finishes, the
\
Qualys Cloud Agent will start communicating with the platform automatically. The Mac
\
should also appear in Asset Manager shortly afterwards.

You can close the Terminal window at this point.

### <mark style="color:$primary;">Troubleshooting</mark>

* **Installer won't open** — Check System Settings → Privacy & Security and click Open
  \
  Anyway next to QualysCloudAgent.pkg.
* **“Permission denied” when activating** — Make sure you included sudo at the start of
  \
  the activation command.
* **“No such file or directory”** — This usually means the package install didn't complete.
  \
  Re-run Step 2 and confirm the installer reports success before moving on.
* **Activation rejected / agent doesn't appear** — Double-check the CustomerId and
  \
  ActivationId values. Copy and paste from Deploy Agent rather than typing.
* **Connection error** — Confirm the Mac has internet access and that no firewall is
  \
  blocking outbound HTTPS to qagpublic.qg1.apps.qualys.co.uk.

### <mark style="color:$primary;">Need Help?</mark>

If the install still won't complete, contact our support team and include the full output
\
shown in Terminal — that helps us identify the issue quickly.

Please contact <support@cybaops.help> for assistance.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cybaops.com/getting-started/onboarding/agent-deployment/qualys-macos.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.