Skip to main content

Upgrading from 1.x to 2.0

Cortex 2.0 has a couple upgrade considerations.

1. Cortex now requires a read-write connection (to its own database)​

NOTE: Cortex does not require read-write access to Cherwell data and never will.

However, many features of Cortex require that some configuration be saved to a database somewhere. In order to support many different security postures, you can choose any of the following options.

  • Cortex can use the Cherwell/Default connection string with a read/write user
  • Cortex can use the Cherwell/Default connection string with a SQL user that has read/write access to the cortex "schema".
  • (RECOMMENDED) Cortex can use a separate Cortex connection string with a read/write user to a separate database on the same server.
  • Cortex can use a separate Cortex connection string to a different database on a different server (or even on PostgreSQL or SQLite)

2. Cortex will create several new tables in its own database​

However, if you aren't using those features, the tables will remain empty and consume negligible disk space.

Some of them are in support of some of the other variants of Cortex (Cherwell, ServiceNow, or Mail Monitoring); others are in support of experimental features that may be included in a future version, but no part of those features is active in this version.