Manage Vulnerabilities

Overview

The Vulnerability Dashboard is the central workspace where you view, analyze, and act on security risks across your applications. 

It consolidates scan results, shows protection status, and allows you to take remediation actions directly from the interface.

A typical workflow in this dashboard follows this sequence:

1. Review overall risk (Open Vulnerabilities) 
2. Identify patterns (Top Categories) 
3. Track progress (Previous Scans) 
4. Run or manage scans 
5. Take action on individual vulnerabilities

Step 1: Select Application

Before analyzing vulnerabilities, select the required application from the domain/application selector at the top.

This determines:

• Which application’s vulnerabilities are displayed 
• Whether the data corresponds to a web application or API application

Step 2: Understand Open Vulnerabilities

This section provides a summary of all detected vulnerabilities for the selected application. It helps you quickly understand the current risk exposure and severity distribution.

If critical or high vulnerabilities exist under unpatched categories, your application is still exposed.

Step 3: Highest Open Vulnerabilities

This section highlights the top vulnerability categories contributing to risk. Instead of showing individual vulnerabilites, it groups them into patterns.

Resolve with SwyftComply

The Resolve with SwyftComply option allows you to initiate automated vulnerability remediation directly from this section.

• Applies virtual patches to open vulnerabilities 
• Reduces the need for manual rule creation 
• Helps accelerate remediation for high-risk categories 

For detailed steps and behavior, refer to SwyftComply Configuration and Usage.

Step 4: Previous Scans

4.1: Previous Scans (Review Scan Trends)

This section displays vulnerability trends across the last 5 scans. It helps you evaluate whether your remediation efforts are effective.

4.2 Manage Scan & Remediation

This section displays the current scan status, historical execution details, and available actions for vulnerability detection and remediation.

The available panels vary based on the type of application selected (Web or API).

4.2.1 Web Application Context

When a Web application is selected, this section displays the following panels:

• AUTO SCAN 
• MANUAL PENTESTING 
• SWYFTCOMPLY 

These panels together enable automated scanning, manual testing, and autonomous patching to ensure vulnerabilities are continuously identified and addressed.

Auto Scan

The AUTO SCAN panel provides details about scheduled and on-demand vulnerability scans for the selected application.

It reflects both:

• Scan execution status 
• Latest scan results

Actions

Accessing Auto Scan Configuration

Click the settings icon in the AUTO SCAN panel to open the Scan Configuration window

This is where:

• Auto Scan behavior is defined
• Global Scan settings are configured

Scan configuration can be defined at two levels:

1. Application-Level Scan Configuration 
2. Global Scan Configuration 

1. Application-Level Scan Configuration

Application-level configuration controls how scans are executed for a specific application.

Behavior

• Applies only to the selected application
• Overrides Global Scan settings if both are configured 
• Can be used for critical applications requiring different scan frequency

Global Scan Configuration

Enable the “Global Scan for Web Apps” toggle in the Scan Configuration to apply a centralized scan schedule across all web applications.

Global Scan allows you to define a centralized scan schedule across multiple web applications, eliminating the need to configure scans individually.

Scheduling Modes

1. Separate Scheduling  - Web and API applications can have independent schedules (Useful when APIs require different scan frequency)

2. Linked Scheduling - A single schedule is applied across both Web and API applications 

Enabled using “Link Web and API Global Scan Schedules”

Use this only when both application types require the same scan timing.

Global Scan Behavior: Web Applications

Newly onboarded web applications are automatically included in the global scan schedule 

Example: 
If a scan is scheduled every Thursday, all newly added web applications will follow the same schedule.

Manual Pentesting

The MANUAL PENTESTING panel allows you to request a manual penetration test for deeper vulnerability analysis. 

Manual Pentesting complements automated scanning by uncovering complex, business logic, and context-driven vulnerabilities that require expert validation.

• Click Request Manual PenTest.
• Result: A confirmation pop-up appears. 
• Provide the confirmation and the request will be forwarded to our AppTrana team.

Behavior

• Requests are handled by the AppTrana team 
• Results are updated in the dashboard after completion

SWYFTCOMPLY

The SWYFTCOMPLY panel provides autonomous virtual patching. It ensures identified vulnerabilities are virtually patched without requiring manual intervention.

For detailed steps and behavior, refer to SwyftComply for Auto Scan & Manual Pentest

4.2.2: API Context

Selected API Scan

• From the application menu, select the API application. 
• Navigate to Selected API Scan field. 

This section provides details about API scan execution and allows you to configure and initiate API scans.

API Scan Configuration

Clicking settings icon opens the Scan Configuration window for API applications. This window allows you to define scan behavior and scheduling for API applications.

The configuration window contains the following sections:

Global Scan settings defined here control scheduling across API applications

Schedule Scan

This section defines when and how frequently API scans are executed.

Link Web and API Global Scan Schedules

Enable “Link Web and API Global Scan Schedules” to apply a single unified scan schedule across both Web and API applications.

• When enabled → Web and API scans follow the same schedule 
• When disabled → API scans follow their own independent schedule 

Global Scan is not applied immediately after onboarding for API applications. Global Scan is automatically applied to web applications upon onboarding, whereas API applications require initial configuration and a first successful scan before being included.

Manage API

• To onboard and configure your API, go to Selected API Scan and click Manage APIs.

• You will be redirected to API Security → API Scanning. 

Click here to follow the step-by-step API onboarding process.

SwyftComply

The SWYFTCOMPLY panel provides autonomous virtual patching  of API vulnerabilities

For detailed steps and behavior, refer to SwyftComply for API Scan

Step 5: List of Vulnerabilities Detected

This is the primary action section where vulnerabilities are reviewed and remediated. 

Use the tabs to filter vulnerabilities based on their current status:

5.1 View all vulnerabilities

This section provides a detailed, row-level view of all detected vulnerabilities, enabling you to review, validate, and take action on each vulnerabilities.

Each row represents a vulnerability with the following details:

Click on the Vulnerability ID to open the detailed view of the selected vulnerability.

Request POC

Click Request POC to validate whether a vulnerability is practically exploitable. This helps you understand the real impact before taking remediation actions.

When you click Request POC, a confirmation pop-up appears asking you to proceed with the request.

Click View POC once it is generated to review detailed evidence demonstrating how the vulnerability can be exploited.

The POC may include request-response data, payloads, or visual proof such as browser errors, certificate issues, or application behavior that confirms the vulnerability.

Actions

Use the available actions to validate findings, apply protection, or track remediation based on your workflow. 

You can take the following actions to validate and remediate vulnerabilities:

5.2 Needs Action

The Needs Action tab displays vulnerabilities that are not yet fully remediated and require user or platform intervention.

Click on the Vulnerability ID in the Needs Action tab to open the detailed view of the selected vulnerability.

From this view, you can take the following actions:

5.3 Patched

The Patched tab displays vulnerabilities that are already protected through AppTrana.

5.4 Whitelisted

The Whitelisted tab displays vulnerabilities marked as safe or intentionally ignored.

To learn how to whitelisting vulnerabilities, see Whitelist Vulnerabilities.