> ## Documentation Index
> Fetch the complete documentation index at: https://docs.threataware.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Cynet 360

> Connect ThreatAware to Cynet 360 for endpoint threat detection and response data

## Overview

The Cynet 360 integration enables ThreatAware to collect endpoint threat detection and response data from your Cynet 360 environment, providing visibility into security incidents and endpoint protection status.

<Info>
  **Connection Method**: API
  **Setup Time**: 10 minutes
  **Access Required**: Cynet 360 Administrator account
</Info>

## Data collected

The Cynet 360 integration provides:

* Endpoint threat detection events
* Security incident data
* Endpoint protection status
* Threat response information
* Device security posture

## Use cases

<CardGroup cols={2}>
  <Card title="Endpoint Threat Monitoring" icon="shield-virus">
    Monitor threats detected on endpoints across your environment
  </Card>

  <Card title="Incident Tracking" icon="triangle-exclamation">
    View and track security incidents from Cynet 360 in ThreatAware
  </Card>

  <Card title="Endpoint Health" icon="heart-pulse">
    Monitor endpoint protection status and security agent health
  </Card>

  <Card title="Security Reporting" icon="chart-line">
    Generate compliance reports showing endpoint threat coverage
  </Card>
</CardGroup>

## Setup instructions

<Steps>
  <Step title="Access ThreatAware Dashboard">
    Log in to your ThreatAware dashboard and navigate to **Settings** > **Systems**.
  </Step>

  <Step title="Locate Cynet 360">
    Use the search bar to find "Cynet 360" in the integrations list.
  </Step>

  <Step title="Click Connect">
    Click **Connect** to open the connection popup window.
  </Step>

  <Step title="Prepare Cynet 360 Credentials">
    Gather the following information from your Cynet 360 account:

    * Your Cynet 360 URL domain (e.g., if your URL is `https://example.api.cynet.com/`, extract `example`)
    * **Client ID** (from API credentials)
    * **Username** (for API access)
    * **Password** (for API access)

    <Info>
      Log in to your Cynet 360 admin console to find these credentials in your API settings
    </Info>
  </Step>

  <Step title="Enter Domain in ThreatAware">
    In the ThreatAware connection popup:

    * Enter **only the domain portion** of your Cynet 360 URL
    * For example, if your URL is `https://YOURDOMAIN.api.cynet.com/`, enter only `YOURDOMAIN`
    * Do not include `api.cynet.com` or the protocol

    <Warning>
      Ensure you extract only the subdomain. Including extra text will cause connection failures.
    </Warning>
  </Step>

  <Step title="Input API Credentials">
    Complete the remaining fields:

    * **Client ID**: Your Cynet 360 API Client ID
    * **Username**: The username for API access
    * **Password**: The password for API access
  </Step>

  <Step title="Authorize Connection">
    Click the **Save & Authorize** button to establish the integration.
  </Step>

  <Step title="Verify Connection">
    After authorising:

    * Confirm the connection is successful by checking the status in the ThreatAware dashboard
    * Verify endpoint threat data begins appearing within 5-10 minutes
    * Check the **Integration Status** shows as **Active**
  </Step>
</Steps>

## Required credentials

<AccordionGroup>
  <Accordion title="Domain" icon="globe">
    **Field Name**: Cynet 360 Domain
    **Type**: String
    **Description**: The subdomain of your Cynet 360 instance

    **Format**: Enter only the subdomain (e.g., `yourdomain`)
    **Example**: If your URL is `https://example.api.cynet.com/`, enter `example`

    <Tip>
      Do not include "api.cynet.com" or the protocol
    </Tip>
  </Accordion>

  <Accordion title="Client ID" icon="id-card">
    **Field Name**: Cynet 360 Client ID
    **Type**: String
    **Description**: Your API client identifier

    Found in Cynet 360 API settings
  </Accordion>

  <Accordion title="Username" icon="user">
    **Field Name**: Cynet 360 Username
    **Type**: String
    **Description**: Username for Cynet 360 API access

    Should be an account with sufficient API permissions
  </Accordion>

  <Accordion title="Password" icon="lock">
    **Field Name**: Cynet 360 Password
    **Type**: Password (encrypted)
    **Description**: Password for Cynet 360 API access

    <Tip>
      Store this credential securely in your organisation's password manager
    </Tip>
  </Accordion>
</AccordionGroup>

## Verification and testing

After setup, verify the integration is working correctly:

1. **Check Integration Status**
   * Navigate to **Settings** > **Systems** in ThreatAware
   * Confirm Cynet 360 shows **Active** status
   * Check the last sync timestamp

2. **Verify Data Collection**
   * Wait 5-10 minutes for the initial data poll
   * Check for endpoint threat data in ThreatAware
   * Verify the data matches what you see in Cynet 360

3. **Test Queries**
   * Create a test query to filter endpoints with Cynet 360 data
   * Verify the threat data matches your expectations

## Troubleshooting

<AccordionGroup>
  <Accordion title="Invalid Domain Error" icon="map-pin">
    **Symptoms**: Connection fails with domain validation error

    **Solutions**:

    * Verify you entered **only the domain** (e.g., `yourdomain`) without `api.cynet.com`
    * Check your Cynet 360 URL and extract the correct subdomain
    * Ensure no extra spaces or special characters were included
    * Example: For URL `https://example.api.cynet.com/`, enter `example`
  </Accordion>

  <Accordion title="Invalid Credentials Error" icon="triangle-exclamation">
    **Symptoms**: Authentication failure or invalid credentials message

    **Solutions**:

    * Verify the **Client ID**, **Username**, and **Password** are correct
    * Ensure the account has sufficient API permissions in Cynet 360
    * Check that credentials were copied without extra spaces
    * Confirm the API account is still active and not locked
    * Test credentials directly in Cynet 360 admin console
  </Accordion>

  <Accordion title="Permission Issues" icon="ban">
    **Symptoms**: Connection succeeds but no endpoint data appears

    **Solutions**:

    * Verify the API account has read permissions in Cynet 360
    * Check that the account is not restricted to specific organisational units
    * Confirm API access is enabled for your account
    * Review Cynet 360 API documentation for required permissions
  </Accordion>

  <Step title="No Data After 10 Minutes" icon="database">
    **Symptoms**: Integration shows active but no endpoint threat data appears

    **Solutions**:

    * Verify there are endpoints and threat data in Cynet 360
    * Check that the API account has access to the required data
    * Review ThreatAware integration logs for errors
    * Wait up to 30 minutes for initial data sync to complete
    * Contact ThreatAware support if issues persist
  </Step>

  <Accordion title="Connection Timeout" icon="clock">
    **Symptoms**: Integration fails to connect or times out

    **Solutions**:

    * Verify Cynet 360 is accessible and online
    * Check firewall rules allow outbound HTTPS (443) to Cynet 360
    * Test the Cynet 360 URL in a browser to ensure connectivity
    * Verify your internet connection is stable
    * Try connecting again after waiting a few minutes
  </Accordion>
</AccordionGroup>

## Additional resources

<CardGroup cols={2}>
  <Card title="Cynet 360 API Documentation" icon="book" href="https://docs.cynet.com/">
    Official Cynet 360 API documentation for detailed API information
  </Card>

  <Card title="ThreatAware Support" icon="life-ring" href="mailto:help@threataware.com">
    Contact ThreatAware support for integration assistance
  </Card>
</CardGroup>

## Best practices

<Tip>
  **Credential Management**

  * Create a dedicated API account specifically for ThreatAware
  * Document credentials in your organisation's password manager
  * Rotate credentials annually or per your security policy
  * Monitor for authentication failures in ThreatAware regularly
</Tip>

<Tip>
  **Security Considerations**

  * Use read-only API accounts (never grant write permissions)
  * Limit API account scope to necessary organisational units
  * Review Cynet 360 audit logs periodically to monitor API usage
  * Follow your organisation's principle of least privilege
</Tip>