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

# CSC Global

> Configure the CSC Global DomainManager integration with RAD Security to ingest domain portfolio, DNS posture, and TLS data.

# CSC Global Integration Setup

This guide walks you through integrating CSC Global **DomainManager** with RAD Security to ingest your domain portfolio and DNS security posture, DNS zone records, and TLS certificates for external attack-surface and brand-protection analysis.

CSC Global DomainManager manages enterprise domain registration, DNS, and digital certificates. RAD Security connects to the DomainManager API and pulls your domain, DNS, and certificate data on a scheduled basis. CSC Global covers domain **registration** and **TLS** — it complements DNS Made Easy, which covers operational DNS.

<Info>
  **Read-only integration:** RAD Security only reads data from CSC Global. It never registers, modifies, or deletes domains, DNS records, or certificates in your CSC account.
</Info>

## Prerequisites

Before you begin, ensure you have:

<Check>
  * A CSC Global DomainManager account with API access enabled
  * An API-enabled admin login for the CSC DomainManager portal (weblogin.cscglobal.com)
  * Ability to generate a bearer API token and copy the API key
  * Knowledge of which environment to target — `production` or `ote`
  * Access to a RAD Security workspace with integration permissions
</Check>

## Understanding Integration Components

<AccordionGroup>
  <Accordion title="Dual-Credential Authentication" icon="key">
    The CSC DomainManager API uses **two** credentials together on every request: a Bearer **API Token** (sent as `Authorization: Bearer`) and a per-account **API Key** (sent as the `apikey` header). Both are required.
  </Accordion>

  <Accordion title="Environments" icon="globe">
    CSC Global offers a production environment and an OTE sandbox. **Production** uses `apis.cscglobal.com`; the **OTE** sandbox uses `apis-ote.cscglobal.com`. Credentials are environment-specific — OTE credentials will not work against production and vice versa.
  </Accordion>

  <Accordion title="Token Lifecycle" icon="clock">
    The CSC API token expires after roughly **30 days of inactivity** and can be refreshed or regenerated in the portal. Because RAD polls continuously, the token normally stays alive — but if sync is disabled for a long period, you may need to regenerate it.
  </Accordion>
</AccordionGroup>

***

## Step 1: Generate API Credentials in CSC DomainManager

<Steps>
  <Step title="Sign in to DomainManager">
    Sign in to the CSC DomainManager portal at [weblogin.cscglobal.com](https://weblogin.cscglobal.com) as an API-enabled admin.
  </Step>

  <Step title="Generate the Bearer Token">
    Under the API settings, generate the **bearer token**. This is sent as `Authorization: Bearer` on every request.

    <Warning>
      The CSC API token expires after about **30 days of inactivity** and can be refreshed or regenerated in the portal. RAD's continuous polling keeps it alive, but if the integration is disabled for an extended period you may need to regenerate the token and update it in RAD Security.
    </Warning>
  </Step>

  <Step title="Copy the API Key">
    Copy your per-account **API key**. This is sent as the `apikey` header on every request.
  </Step>

  <Step title="Determine the Environment">
    Decide whether to target **production** or the **ote** sandbox, and use the credentials issued for that environment.
  </Step>
</Steps>

<Note>
  Exact portal navigation and labels may vary. See the [CSC DomainManager API documentation](https://www.cscglobal.com/cscglobal/docs/dbs/domainmanager/api-v2/) for the current steps to generate the bearer token and API key.
</Note>

***

## Configure in RAD Security

Navigate to your RAD Security workspace and configure the CSC Global integration with the following parameters:

### Required Parameters

| Parameter       | Description                                                                      |
| --------------- | -------------------------------------------------------------------------------- |
| **API Token**   | Bearer token generated in the CSC admin portal (sent as `Authorization: Bearer`) |
| **API Key**     | Per-account API key (sent as the `apikey` header)                                |
| **Environment** | `production` or `ote` (the CSC OTE sandbox)                                      |

***

## Verify Integration

<Steps>
  <Step title="Check Connection Status">
    1. Navigate to **Data Sources > Integrations > Domain Security** in RAD Security
    2. Locate your CSC Global integration
    3. Verify the connection status shows as **Connected**
  </Step>
</Steps>

<Check>
  Your CSC Global integration is now configured! RAD Security will ingest your domain portfolio, DNS records, and TLS certificates on a scheduled basis.
</Check>

## What Data is Synced

<AccordionGroup>
  <Accordion title="Domain Portfolio & DNS Posture" icon="globe">
    * DKIM/SPF/DMARC and DNSSEC presence
    * Registrar locks: serverDelete, serverTransfer, and serverUpdate prohibited; multilock; vital flag
    * MX/A record counts and HTTP reachability
  </Accordion>

  <Accordion title="DNS Zone Records" icon="server">
    * A/AAAA/CNAME/MX/TXT/NS/SRV/CAA records
  </Accordion>

  <Accordion title="TLS Certificates" icon="certificate">
    * Common name
    * Validity dates
    * Certificate status
  </Accordion>
</AccordionGroup>

This data feeds external attack-surface and brand-protection analysis in RAD Security.

## Use Cases

<CardGroup cols={2}>
  <Card title="Attack Surface Analysis" icon="diagram-project">
    Map your external footprint across registered domains, DNS records, and certificates.
  </Card>

  <Card title="DNS Posture Hygiene" icon="shield-check">
    Track DKIM/SPF/DMARC, DNSSEC, and registrar locks across your portfolio.
  </Card>

  <Card title="Certificate Lifecycle" icon="certificate">
    Catch expiring or misconfigured TLS certificates before they cause outages.
  </Card>

  <Card title="Brand Protection" icon="shield-halved">
    Monitor your registered domains to support brand-protection workflows.
  </Card>
</CardGroup>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Authentication Failed" icon="triangle-exclamation">
    **Possible causes:**

    * Incorrect API token or API key
    * The API token has expired (after \~30 days of inactivity)

    **Solution:**

    * Verify both the **API Token** and **API Key** are copied correctly (no extra spaces)
    * Regenerate the bearer token in the CSC portal if it has expired, then update it in RAD Security
    * Confirm the credentials belong to the environment you selected
  </Accordion>

  <Accordion title="Wrong Environment" icon="globe">
    **Possible causes:**

    * OTE sandbox credentials used against production (or vice versa)

    **Solution:**

    * Ensure the **Environment** parameter matches the credentials: `production` for `apis.cscglobal.com`, `ote` for `apis-ote.cscglobal.com`
    * Generate credentials for the correct environment if needed
  </Accordion>

  <Accordion title="Empty Results" icon="inbox">
    **Possible causes:**

    * RSQL filters scoping out all records
    * The account has no domains

    **Solution:**

    * Confirm the account has domains in the CSC DomainManager portal
    * Review any configured filters that may exclude results
  </Accordion>
</AccordionGroup>

## Security Best Practices

<CardGroup cols={2}>
  <Card title="Use a Service Login" icon="user-gear">
    Generate API credentials under a dedicated admin login rather than a personal account.
  </Card>

  <Card title="Rotate Credentials" icon="rotate">
    Regenerate the bearer token and API key periodically according to your security policy.
  </Card>

  <Card title="Secure Storage" icon="vault">
    Store the API token and API key in a secrets vault. Never commit them to version control.
  </Card>

  <Card title="Use OTE for Testing" icon="flask">
    Validate configuration against the OTE sandbox before connecting production.
  </Card>
</CardGroup>

## Additional Resources

<CardGroup cols={2}>
  <Card title="CSC DomainManager API" icon="book" href="https://www.cscglobal.com/cscglobal/docs/dbs/domainmanager/api-v2/">
    Official CSC DomainManager API v2 documentation
  </Card>

  <Card title="Domain Security Overview" icon="globe" href="/rad-security/integrations/domain-security/overview">
    Learn about RAD's domain security integrations
  </Card>
</CardGroup>

## Next Steps

<CardGroup cols={2}>
  <Card title="DNS Made Easy Setup" icon="server" href="/rad-security/integrations/domain-security/dns-made-easy-setup">
    Complement CSC Global with operational DNS from DNS Made Easy
  </Card>

  <Card title="Domain Security Overview" icon="globe" href="/rad-security/integrations/domain-security/overview">
    Explore other domain security integration options
  </Card>

  <Card title="Data Sources" icon="database" href="/rad-security/integrations/data-sources">
    Connect additional security data sources
  </Card>
</CardGroup>