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

# SFTP and CB Secure File Transfer

> Connection requirements for Credit Benchmark SFTP and CB Secure file transfer.

Credit Benchmark supports two secure file transfer channels:

* **SFTP** for automated or scheduled file exchange between systems.
* **CB Secure** for manual upload and download through a browser.

## Standard Feed File Delivery

Credit Benchmark can make standard output files available through SFTP. In this model, Credit Benchmark publishes an agreed feed file to the secure transfer location on the agreed schedule, and your systems collect it from there.

SFTP and CB Secure can also support custom file exchange, including files you send to Credit Benchmark and managed workflows such as [Matching as a Service](/delivery-channels/feed-file/managed-entity-resolution).

Both channels use encrypted transport and are restricted to approved client IP addresses. The sections below cover the connection setup rather than the contents of a specific feed.

## Choose a Channel

| Channel   | Use when                                                | Protocol              | Authentication                          |
| --------- | ------------------------------------------------------- | --------------------- | --------------------------------------- |
| SFTP      | Files are produced or consumed by an automated process. | SSH / SFTP on port 22 | SSH public key, password, or both       |
| CB Secure | A person needs to upload or download files manually.    | HTTPS on port 443     | Username and password; MFA is available |

## Channel Setup

<AccordionGroup>
  <Accordion title="SFTP">
    Use SFTP when files need to move between Credit Benchmark and a client-controlled system without manual browser steps.

    ### Endpoints

    Use DNS hostnames when connecting. IP addresses are provided for firewall allowlisting only.

    | Environment | Hostname                          | IP address       | Port |
    | ----------- | --------------------------------- | ---------------- | ---- |
    | Production  | `cbsecure.creditbenchmark.com`    | `206.142.214.50` | `22` |
    | UAT         | `uatcbsecure.creditbenchmark.com` | `206.142.214.52` | `22` |

    ### Client Requirements

    * Install or configure an SFTP client or automated transfer job.
    * Allow outbound access to the relevant Credit Benchmark hostname on port `22`.
    * Provide the public source IP addresses that Credit Benchmark should allowlist.
    * Choose public key authentication, password authentication, or both.

    ### SSH Public Key Requirements

    | Requirement          | Value                          |
    | -------------------- | ------------------------------ |
    | Key type             | SSH-RSA                        |
    | Minimum strength     | 2,048-bit RSA                  |
    | Recommended strength | 4,096-bit RSA                  |
    | Format               | OpenSSH single-line public key |
    | Maximum key lifetime | 2 years                        |

    Only send Credit Benchmark the public key. Private keys must remain under your control.
  </Accordion>

  <Accordion title="CB Secure">
    Use CB Secure when users need a browser-based upload and download portal instead of an automated SFTP connection.

    ### Endpoints

    | Environment | URL                                       | IP address       | Port  |
    | ----------- | ----------------------------------------- | ---------------- | ----- |
    | Production  | `https://cbsecure.creditbenchmark.com`    | `206.142.214.50` | `443` |
    | UAT         | `https://uatcbsecure.creditbenchmark.com` | `206.142.214.52` | `443` |

    ### Client Requirements

    * Use a browser that supports HTTPS.
    * Allow outbound access to the relevant Credit Benchmark URL on port `443`.
    * Provide the public source IP addresses that Credit Benchmark should allowlist.
    * Use username and password authentication. MFA is available.

    <Note>
      SSH public key authentication is not available for CB Secure.
    </Note>
  </Accordion>
</AccordionGroup>

## Information Credit Benchmark Needs

Provide these details before an account is created.

| Value                 | What it is                                                                | Example format                                   |
| --------------------- | ------------------------------------------------------------------------- | ------------------------------------------------ |
| Company name          | The legal or operating entity that will use the connection.               | `Example Bank Ltd`                               |
| IT contact            | A named technical contact for setup, changes, and operational issues.     | Name, phone number, and email address            |
| Channel               | The file transfer channel you need.                                       | `SFTP`, `CB Secure`, or both                     |
| Source IP addresses   | The public IP addresses or CIDR ranges that should be allowed to connect. | `203.0.113.10` or `203.0.113.0/28`               |
| Authentication method | Required for SFTP only.                                                   | Public key, password, or public key and password |
| Public key            | Required for SFTP public key authentication only.                         | OpenSSH single-line RSA public key               |

<Note>
  Credit Benchmark will not create or maintain a connection without current technical contact details.
</Note>

## IP Allowlisting

Access is limited to IP addresses supplied by the client and approved by Credit Benchmark.

| Allowlist type          | Limit                                                              |
| ----------------------- | ------------------------------------------------------------------ |
| Individual IP addresses | 5 or fewer                                                         |
| CIDR ranges             | 5 or fewer ranges                                                  |
| Total address coverage  | Up to 1,280 IP addresses across individual entries and CIDR ranges |

Client teams are responsible for firewall changes in their own environment.

## Password Requirements

Passwords must:

* Be 10 to 30 ASCII characters.
* Include at least one uppercase letter, one lowercase letter, one number, and one supported special character.
* Not contain spaces or non-printable characters.
* Be stored securely and shared only with authorised users.

Passwords expire 18 months after creation.

Supported special characters:

```text theme={null}
_ % + = - [ ] , . { } $ \ ` & ( ) < " > | ; ' ^ * ? : # @ !
```

## File Size and Retention

Credit Benchmark file transfer is a store-and-forward service, not an archive. Clients are responsible for retaining their own copies of transferred files.

| Limit                                   | Value                                          |
| --------------------------------------- | ---------------------------------------------- |
| Maximum storage per account             | 5 gigabytes                                    |
| File retention                          | Files may be removed on a rolling 30-day basis |
| Maximum single file, one-time delivery  | 1.5 gigabytes                                  |
| Maximum single file, automated delivery | 400 megabytes                                  |

Files above accepted limits may be blocked or deleted.

## Processing Expectations

Uploaded files are generally processed within 30 minutes end to end. Some workflows run once every 24 hours.

SFTP is not a real-time interface. If your workflow requires real-time data transfer, use a real-time protocol agreed separately with Credit Benchmark.

## Account Lifecycle

Accounts that are not accessed for more than 6 months may be deleted, including associated files.

For setup or connection changes, contact your Credit Benchmark representative or [support@creditbenchmark.com](mailto:support@creditbenchmark.com).