# ServiceNow CMDB

The ServiceNow CMDB connector reads your configuration management database and
brings that inventory into Mesh, so your machines, software, certificates and
people are correlated with every other connected system.

It is **read-only**. Every **data** request is a read. Mesh never creates,
changes or deletes anything in ServiceNow.

## What it collects

| From ServiceNow | Becomes in Mesh |
| --- | --- |
| Computers | Machine assets |
| Containers, installed software and software models | Software assets |
| Certificates | Certificate records |
| Users | User accounts |
| Groups and their members | Groups and membership |
| Departments | Organization context |
| Locations | Location records |
| Vulnerability records | Application inventory records |

You choose which of these to collect. All are selected by default.

> **note**
Mesh reads containers into your **software** inventory. If you clear the
software sets, you lose containers too.

> **note**
Mesh has no vulnerability view today. Vulnerability records are kept as
inventory records — they don't feed risk scores or dashboards.

## What you need before you start

| You need | Notes |
| --- | --- |
| Your ServiceNow instance URL | Must be HTTPS on `service-now.com` — for example `https://acme.service-now.com` |
| A credential | One of five methods. See [Choose an authentication method](./set-up.mdx#step-5--choose-an-authentication-method) |
| A ServiceNow account that can read the tables | Read access is enough. The connector never writes |
| A Mesh administrator account | To add connectors |

> **tip**
Use a dedicated ServiceNow service account rather than a person's login. A
personal account stops working when that person leaves or changes role.

## Set it up

| Step | What you do |
| --- | --- |
| **[Set up ServiceNow CMDB](./set-up.mdx)** | Add the connector, pick what to collect, and test the connection |
| **[Troubleshooting](./troubleshooting.mdx)** | What to do when the test fails or data looks incomplete |

## How often it runs

The connector runs hourly. You can't change the schedule from the connector
form — contact Axiad if you need a different one.

Every collection is **incremental**: after the first run, Mesh asks ServiceNow
only for records that changed since last time. This keeps the load on your
instance low.

> **note**
The first collection reads your whole estate, so it can take a while on a large
CMDB. Later runs are much faster.