Skip to content

Port / App Mapping

Purpose

Port / App Mapping is the Clarity Transform lookup table that turns a port number into a named service. When inference sees traffic or a listening port on TCP 1433, this table says that means SQL Server. The on-screen subtitle reads: "Reference table mapping known ports to suggested application names - used by inference to identify a service from network evidence alone."

The seeded set covers common infrastructure and database ports. Extend it with the ports specific to the estate, which a generic list does not know.

Where to find it

Discover → Application Inference → Port / App Mapping. The page header is Port / App Mapping.

What you see

Columns

  • Port
  • Protocol
  • Suggested App Name: the service name inference gives a candidate when this port is seen.
  • Suggested App Type
  • Is Seeded
  • Is Active

Seeded mappings

The seeded mappings, read from the product's own seed data rather than maintained here, so this list cannot drift from what a deployment actually contains. 20 ports are seeded, and a deployment can add its own alongside them.

Port Suggested application Type
6379/TCP Redis Cache Cache
11211/TCP Memcached Cache
1433/TCP SQL Server Database
1521/TCP Oracle DB Database
3306/TCP MySQL Database
5432/TCP PostgreSQL Database
27017/TCP MongoDB Database
389/TCP LDAP Directory Directory
636/TCP LDAPS Directory Directory
445/TCP SMB File Share File
2049/TCP NFS File Share File
25/TCP SMTP Mail Service Messaging
5671/TCP RabbitMQ Messaging
9092/TCP Kafka Messaging
22/TCP SSH Service Remote Access
3389/TCP RDP Remote Desktop Remote Access
8500/TCP Consul Service Mesh
80/TCP HTTP Web Service Web
443/TCP HTTPS Web Service Web
8080/TCP HTTP App Service Web

Ports 389 and 636 are also listed on Flow Exclusions, which excludes them from inference.

Actions

The grid uses the standard toolbar: Create New, Edit, Remove selected, Clear selection, Reload table data, Enable spreadsheet editing, Export CSV and Import CSV. The rows have no row actions.

Form

Create New opens the Create new entry form. Edit opens the Edit entry form for the selected row, with the same fields filled in. The fields, in order:

  • Port
  • Protocol
  • Suggested App Name
  • Suggested App Type: text.
  • Is Seeded
  • Is Active: a checkbox, unchecked by default.

The footer has Cancel and Save.

Filters

Each column has a filter row, and the grid has a Search: box and a page-size selector (10, 25, 50 or All entries per page).

The grid remembers its Search: text, column filters, sort order and page size between visits. If the grid shows fewer rows than you expect, clear the Search: box and the filter row.

How to

Add a mapping for the estate's own port

  1. Go to Discover → Application Inference → Port / App Mapping.
  2. Select Create New. The Create new entry form opens.
  3. Enter the Port, the Protocol and the Suggested App Name, and a Suggested App Type if you want one.
  4. Select Is Active.
  5. Select Save, or Cancel to close the form without saving.

Saving a mapping does not start a run: mappings apply on the next inference run. To apply them now, select Run inference on Candidate Applications, then Run grouping.

Correct a reused port

Where a registered port is used for something else in this estate, change the mapping to what it is:

  1. In the grid, select the port's row.
  2. Select Edit. The Edit entry form opens with the mapping's values.
  3. Change the Suggested App Name and Suggested App Type, then select Save.