FIGR / UI TEMPLATE

Penetration Test Findings

Penetration Test Findings for security teams to triage risk, assign ownership, preserve evidence, and move the highest-priority work toward resolution.

This table reference covers cybersecurity. Its sample screen includes Identity service and Payments API and the Add finding action. Adapt its workflow to your product and design system.

Penetration Test Findings

BUILD ON THIS

Make it yours in Figr.

Explore this screen, then bring in your own product and design system to shape the next version.

Use this template ↗

At a glance

Screen

Table

Primary action

Add finding

Pattern

Penetration Test Findings table

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps with

The penetration test findings screen supports “Add finding” while keeping overview and risk in view. It should show the current state even when data is missing or access is restricted.

What to look for

  • Primary action: Add finding
  • Main area: Overview brings the user to the relevant workflow
  • Related area: Risk keeps nearby context accessible
  • Open risk: 26 in the sample screen
  • Critical: 3 in the sample screen
  • Example 1: Identity service
  • Example 2: Payments API

States to consider

  • Default: Show the main workflow and its available next step
  • Loading: Retain table headers, sort order, and selected filters
  • Empty: Distinguish no records from no matches for the current filters
  • Error: Preserve selected rows and clarify whether any batch changes saved
  • Access: Show which actions require a role or permission
  • Success: Confirm the result after Add finding and say what happens next

Where it fits

Overview → Risk → Add finding → Review result

Patterns in this screen

Penetration Test Findings table, Overview, Risk, permission handling, error recovery

UX choices to review

Show the columns that help someone choose the next action

In this example, Identity service is one of the records worth checking. Keep the sample data clearly separate from a live system.

Preserve filters and sort order as people open records and return

Make status, ownership, and exceptions easy to scan, including smaller screens

Try a similar screen in Figr

Design a penetration test findings screen for an existing cybersecurity product. Use our actual design system, components, and content rules. Cover Overview and Risk, include believable records such as Identity service, and make "Add finding" easy to find. Map empty, loading, error, permission, and success states. Keep the result editable in Figma.

Open Figr

KEEP EXPLORING

More ways to approach your next screen.

Browse other product UI examples, compare patterns, and pick the direction that suits your product.

Explore all 500 templates ↗