Global Scan Agent Requirements

This article covers the requirements every endpoint needs before you install the Cyrisma Agent, regardless of operating system. Check these items before deployment to support reliable installation, accurate data collection, and consistent communication with the Cyrisma platform.

The Scan Agent runs local assessments on each endpoint and sends the results securely to the Cyrisma cloud platform. OS-specific installation steps and troubleshooting are covered in separate articles.

Related articles:

• Whitelisting the Cyrisma Agent in Common Endpoint Protection Platforms

• Scan Agent Supported Operating Systems

How the Agent Works

The Cyrisma Agent provides continuous vulnerability and configuration baseline management. You do not need to maintain scheduled vulnerability or baseline scans for endpoints running the agent.

The agent collects software version and machine configuration telemetry in the background and securely sends it to the Cyrisma cloud. Cyrisma analyzes that telemetry in the cloud to identify vulnerabilities and configuration weaknesses. Moving this analysis off the endpoint reduces local CPU, memory, and storage use. The agent sends changes to telemetry as they occur, reducing the amount of data transferred.

Network scanning remains a separate activity. Scans of other devices on the local subnet can still be scheduled and run from a Cyrisma Agent machine on that subnet. These scans help identify network devices, including machines that could benefit from an agent installation.

Windows Agent Services

On Windows, the agent uses the following services and executables:

These details can help you identify the agent's services and processes when troubleshooting or configuring endpoint protection.

1. Hardware Requirements

Processor

• Minimum: 2 virtual CPUs

• Recommended: 2.8–2.9 GHz processor

Allow sufficient CPU capacity for the agent and any additional activities performed by the endpoint, including network and data scans.

Memory (RAM)

• Recommended minimum: 1 GB (1024 MB)

If the endpoint runs other heavy workloads or performs large data scans, allocate additional memory to avoid slowdowns or instability.

Disk Space

• Minimum free space: Approximately 500 MB

• Temporary usage: Up to 1–2 GB during data scans, depending on scan scope

2. Network Connectivity Requirements

The agent needs outbound access to the Cyrisma cloud to install, update, check in, receive configuration changes, and upload telemetry and scan results.

Connection Requirements

No inbound firewall rules are needed for agent-to-cloud communication. The agent does not listen for inbound connections.

Required Destinations

Allow outbound HTTPS (443) from each endpoint to the following:

1. Your Tenant URL. This is unique to your tenant and is shown in Agent Setup, for example, https://ccXXXXXX.cyrisma.com. The agent uses it for ongoing communication with your tenant.

2. https://dl.cyrisma.com. Used to download and update the agent.

3. The management (auth) endpoint for your region. Used for tenant, MSP, and agent management, including versioning and security.

If any required destination is blocked, agent installation, upgrades, or communication may fail.

TLS/SSL Inspection

If your network uses TLS/SSL inspection, make sure it does not interfere with traffic to the Cyrisma destinations listed above.

3. Endpoint Protection and Antivirus Configuration

Your EDR or antivirus software must allow Cyrisma agent processes to run normally. Depending on its configuration, a security tool may block legitimate agent activity such as:

• Telemetry collection for vulnerability and configuration monitoring

• Port scanning

• Remote attribute collection

• Data scans

• Compression of scan results

To prevent interference:

• Exclude the Cyrisma agent installation directory. The path depends on the operating system.

• If your policy does not allow directory exclusions, allow-list the agent's executable processes instead.

For platform-specific steps, see Whitelisting the Cyrisma Agent in Common Endpoint Protection Platforms.

4. Cyrisma Platform and Registration Requirements

Installation Information

You need two tenant-specific values to register the agent:

• Installation Key

• Tenant URL, for example, https://ccXXXXXX.cyrisma.com

Both are available in Agent Setup for the selected tenant.

Agent Setup also provides sample deployment scripts with the selected tenant's Installation Key and Tenant URL already included. Review the scripts and make any adjustments your deployment environment requires before running them.

Important: Confirm the selected tenant before copying installation values or deployment scripts. The endpoint registers to the tenant identified by those values.

Registration and Communication

The agent:

1. Registers with your tenant using the Tenant URL and Installation Key.

2. Uses the Tenant URL for ongoing communication.

3. Downloads installation packages and updates through dl.cyrisma.com.

4. Uses your regional management (auth) endpoint for versioning, security, and management.

Common Causes of Installation or Registration Failure

• The Installation Key is incorrect.

• The Tenant URL is incorrect.

• Access to the Tenant URL or regional management endpoint is blocked.

• Access to dl.cyrisma.com is blocked.

5. Permissions

Local Permissions

• Installing the agent requires administrator privileges on Windows or root privileges on macOS and Linux.

• The agent service needs elevated permissions to access system configuration, security settings, and file metadata required for telemetry collection and data scans.

Network Scanning Permissions

If you use the agent for agentless or network-based scans that collect remote system information, provide a service account with appropriate administrative rights on the target systems. The agent uses this account to collect OS, configuration, and security details from remote machines.

Impact of Missing Requirements

Insufficient memory, restricted permissions, or overly strict endpoint security filtering can cause:

• Slower performance

• Failed communication with the Cyrisma platform

• Incomplete or inaccurate data collection

Check system readiness before installation to reduce these issues.

6. Supported Operating Systems

For the current list of supported operating systems and versions, see Scan Agent Supported Operating Systems.

7. Pre-Deployment Readiness Checklist

Confirm each item before installing the Cyrisma Agent:

• The endpoint meets the CPU, memory, and disk space requirements (Section 1).

• The operating system is supported (Section 6).

• Outbound HTTPS (443) is allowed to your Tenant URL, dl.cyrisma.com, and your regional management endpoint (Section 2).

• TLS/SSL inspection does not interfere with Cyrisma traffic (Section 2).

• Antivirus and EDR tools allow the agent to run through directory exclusions or process allow-listing (Section 3).

• You have the Installation Key and Tenant URL for the correct tenant from Agent Setup (Section 4).

• Administrator or root privileges are available on the endpoint (Section 5).

• (Network scans that collect remote system information only) A service account with the required administrative rights is available (Section 5).