> ## 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.

# N-Central

> Connect ThreatAware to N-Central for remote monitoring and management visibility

## Overview

The N-Central integration enables ThreatAware to collect remote monitoring and management data from your N-Central instance, providing visibility into managed devices and their configuration status.

<Info>
  **Connection Method**: Direct API
  **Setup Time**: 20 minutes
  **Access Required**: N-Central Administrator account
  **Network Requirements**: Port forwarding and IP whitelisting required
</Info>

## Data collected

The N-Central integration provides:

* Managed device information
* Device configuration details
* System health metrics
* Remote management status

## Use cases

<CardGroup cols={2}>
  <Card title="Device Management" icon="computer">
    Track managed devices across your N-Central infrastructure
  </Card>

  <Card title="Configuration Visibility" icon="gear">
    Monitor device configurations and compliance status
  </Card>

  <Card title="Health Monitoring" icon="heartbeat">
    View system health and availability across managed endpoints
  </Card>

  <Card title="Centralized Intelligence" icon="sitemap">
    Correlate N-Central data with other security systems
  </Card>
</CardGroup>

## Setup instructions

<Steps>
  <Step title="Create Dedicated User Account in N-Central">
    * Log in to the N-Central console with administrative credentials
    * Create a new user account specifically for ThreatAware integration
    * Assign the appropriate permissions for API access and device monitoring
    * Note the username and password for this account
  </Step>

  <Step title="Configure Firewall Port Forwarding">
    * Access your firewall configuration
    * Set up a port forward to the N-Central server
    * Configure the port to match your N-Central API port (typically 8040)
    * Restrict access to the current ThreatAware allowlist IP addresses, available in-product under **Settings → Integrations → AWS Account / IP Whitelist Info**

    <Info>
      Only the specified ThreatAware IPs will be allowed to connect to your N-Central instance through this port forward, ensuring security.
    </Info>
  </Step>

  <Step title="Identify N-Central Public IP and Forwarded Port">
    * Determine the public IP address of your N-Central server
    * Confirm the forwarded port configured in the firewall
    * Test connectivity to ensure the port is accessible from outside your network

    <Tip>
      You can test port accessibility using online tools or by accessing the URL from an external network: `https://<public-ip>:<forwarded-port>`
    </Tip>
  </Step>

  <Step title="Configure in ThreatAware">
    Complete the integration setup in ThreatAware:

    * Open ThreatAware and navigate to **Settings** > **Integrations**
    * Search for and select **N-Central**
    * Enter the required information:
      * **Public IP Address**: The public IP address of your N-Central server
      * **Forwarded Port**: The port configured in your firewall
      * **Username**: The dedicated user account created in N-Central
      * **Password**: The password for the dedicated user account
    * Click **Connect** to establish the integration
  </Step>

  <Step title="Verify Connection">
    After connecting, verify the integration is working:

    * Check that the **Integration Status** shows as **Active**
    * Wait up to 5 minutes for the initial data sync
    * Verify managed device data appears in ThreatAware
  </Step>
</Steps>

## Required credentials

<AccordionGroup>
  <Accordion title="Public IP Address" icon="globe">
    **Field Name**: N-Central Server Public IP
    **Type**: String
    **Description**: The public IP address of your N-Central server

    This is the external IP address accessible from the internet. Ensure your firewall port forward is configured to this address.

    Example: `203.0.113.42`
  </Accordion>

  <Accordion title="Forwarded Port" icon="plug">
    **Field Name**: Forwarded Port
    **Type**: String/Integer
    **Description**: The port configured in your firewall for N-Central access

    Typically this is port `8040` or another port configured during your port forward setup.

    Example: `8040`
  </Accordion>

  <Accordion title="Username" icon="user">
    **Field Name**: N-Central Username
    **Type**: String
    **Description**: Username for the dedicated N-Central user account

    Use the account created specifically for ThreatAware integration.
  </Accordion>

  <Accordion title="Password" icon="lock">
    **Field Name**: N-Central Password
    **Type**: Password (encrypted)
    **Description**: Password for the N-Central user account

    <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** > **Integrations** in ThreatAware
   * Confirm the N-Central integration shows **Active** status
   * Check the last sync timestamp

2. **Verify Data Collection**
   * Wait up to 5 minutes for initial data collection
   * Check that managed devices appear in ThreatAware
   * Verify device details match your N-Central console

3. **Test Connectivity**
   * Create a test device query in ThreatAware
   * Verify the results include devices from N-Central
   * Confirm data accuracy against your N-Central console

## Troubleshooting

<AccordionGroup>
  <Accordion title="Connection Errors" icon="triangle-exclamation">
    **Symptoms**: Integration fails to connect

    **Solutions**:

    * Verify the **Public IP Address** and **Forwarded Port** are correct
    * Test the connection manually by accessing the URL in a browser: `https://<public-ip>:<port>`
    * Confirm port forwarding rules are correctly applied in your firewall
    * Verify the N-Central server is running and accessible
    * Check that your firewall allows the connection through the specified port
  </Accordion>

  <Accordion title="Firewall Issues" icon="ban">
    **Symptoms**: Integration times out or fails to authenticate

    **Solutions**:

    * Verify IP whitelisting is correctly configured for the current ThreatAware allowlist IPs (see **Settings → Integrations → AWS Account / IP Whitelist Info**)
    * Confirm the firewall rules allow inbound connections from these IPs
    * Check that no other firewall rules are blocking the connection
    * Review firewall logs for blocked connection attempts
  </Accordion>

  <Accordion title="Authentication Failure" icon="lock-exclamation">
    **Symptoms**: Connection fails after entering credentials

    **Solutions**:

    * Verify the **Username** and **Password** are correct
    * Ensure the N-Central user account has not expired
    * Confirm the user account has the necessary permissions in N-Central
    * Check that no extra spaces were added when copying credentials
    * Verify the account is not locked due to failed login attempts
  </Accordion>

  <Accordion title="No Data After Connection" icon="database">
    **Symptoms**: Integration shows active but no data appears

    **Solutions**:

    * Wait up to 5 minutes for the initial data sync
    * Verify the N-Central user account has permissions to view devices
    * Confirm managed devices exist in your N-Central console
    * Check the N-Central server logs for API access errors
    * Verify the integration user can authenticate to N-Central directly
  </Accordion>
</AccordionGroup>

## Network security considerations

<Tip>
  **IP Whitelisting Best Practice**

  * Only allow ThreatAware's specified IP addresses to access your N-Central instance
  * Review the firewall rules regularly to ensure restrictions are still in place
  * Document the port forwarding configuration for future reference
  * Monitor N-Central access logs to verify only ThreatAware is connecting
</Tip>

<Warning>
  **Important Security Notes**

  * Do not expose your N-Central instance to the internet without proper firewall restrictions
  * Always use the specified IP whitelisting to restrict access
  * Regularly audit N-Central user accounts and revoke unused credentials
  * Ensure all traffic to N-Central is encrypted using HTTPS
</Warning>

## Additional resources

<CardGroup cols={2}>
  <Card title="N-Central Documentation" icon="book" href="https://www.n-able.com/">
    Official N-Central documentation and support resources
  </Card>

  <Card title="Firewall Configuration Help" icon="shield" href="#">
    Contact your network administrator for firewall port forwarding assistance
  </Card>
</CardGroup>