App Catalog

To open the App Catalog, click the Discovery menu (item 1 below). When the menu is collapsed, click the Discovery telescope icon below the Home icon. Then click on the App Catalog tab (item 2 below).

The Discovery item in the left navigation (1) and the App Catalog tab next to Discovered Apps, MCP Servers and Agents (2).

The first time you see the App Catalog, it may look similar to the “Discovered Apps” list. The difference is that now you’re seeing every app WitnessAI knows about, including Apps no one in your organization has used yet.

The App Catalog table with the category sidebar and the Application, Domain, Data Criticality, Country, Policy and Actions columns.

Finding an App

Searching for Apps by App name.

Click in the Search name or domain box at the top, and begin typing the name or domain of the application you want.
As you type, matching apps will appear below the search bar.

When an app shows up, click its name to view details, check its status, or apply policy controls.
If no match is found you’ll see this message:

“No Apps found that begin with ‘…’”

If you have permission to add to the catalog, click Add Application to start registering it yourself.

Tip: If you don’t see an expected app right away, try typing just the first few letters. Search results update live as you type.

Adding a New Application

When an app has not been added to our catalog yet, you can add it yourself. This adds an App to the App Catalog.

From the empty-state prompt, click Add Application.

Enter the application’s domain in the Domain field, for example witness.ai.

Click Submit. Submit stays disabled until you enter a valid domain.

The Add Application dialog with a Domain field, a Cancel button and a disabled Submit button.

You’ll get a confirmation that the application was submitted to the catalog. It’s added to your catalog right away.

Why are some details empty?

WitnessAI researches a new application in the background, using public sources and its own intelligence. Until that finishes, details such as Category, Data Criticality and country may be empty or Unknown. There’s no fixed wait, and you can start applying policies right away, so there’s no gap in your security defenses.

You can:

Control the app through policy actions, like blocking for example.
Block the app while waiting for enrichment.

Click an application to open its App Details panel. It has three tabs: Overview (Domain Name, First Seen, Last Seen and a Supply Chain list), Users and Security. The panel shows a Data Criticality badge, and Overview fields such as Country and Data Types, only when WitnessAI has that data for the application.

For users who can view policies, the panel opens with a card that reports the application’s policy status: Allowed by default policy, Blocked by default policy, Allowed by user decision or Blocked by user decision. The card explains which list the application is on and what its buttons do. Its Block and Allow buttons appear only for users who can update lists.

The App Details panel, with the policy status card, the Overview, Users and Security tabs, and the Overview tab’s Domain Name, First Seen, Last Seen and Supply Chain fields.

Supported Actions

Proactive blocking of apps based on risk categories, enabling admins to inoculate their environment against risky applications before anyone uses them.
Navigation between discovered apps and the full app catalog, which includes browsing by categories (e.g., analytics, business intelligence).
Policy-based protections, allowing customers to create lists and reference them in policies (e.g., only allowing specific user groups access to certain apps). The goal is to protect as much app usage as possible via policy.

Controlling Access: Blocking & Policy Actions

Once an app is in the catalog, you can decide who gets to use it.

Immediate Block

Click the Block button next to any app to deny access at once, even before research finishes. The row then shows Allow, which reverses it, and its Policy badge reads Blocked. To return the app to the default policy instead, choose Remove from List from its More actions menu. These controls appear only if you can update lists.

A blocked application’s row in the App Catalog, with the Blocked policy badge, the Allow button and the More actions menu open on Block and Remove from List.

Policy-Based Protection

Create named Lists (e.g., “Design Tools” or “Sales Apps”) in the Lists console, then tie those lists to user groups, and add Guardrails to enforce your policies.
Example: Allow only the Design team to access Figma, while blocking it for everyone else.

Preemptively block all high-risk tools company-wide:

In the catalog, set the Data Criticality filter to Very High.
Click the Select All checkbox (1) next to the APPLICATION label (2), then the Block button (3).

This ensures employees can’t accidentally visit or launch dangerous apps.

Clicking the Allow button will reverse the action, and allow all Apps with the checkbox checked.

App Catalog Overview Open the App Catalog Finding an App Adding a New Application Controlling Access: Blocking & Policy Actions Preemptively block all high-risk tools company-wide: