Blackbox Pentesting

The Blackbox Pentesting feature in Prancer allows users to quickly and comprehensively launch penetration tests with minimal configuration. Designed for ease-of-use, this capability provides both one-click automation and fine-grained control over advanced testing parameters such as MITRE ATT&CK techniques and custom tagging.

Launching a Blackbox Pentest

Blackbox tests typically begin in the Inventory page. Follow these steps:

1. Locate the Target:

Use the filters, search bar, or manually browse through the listed inventory items to find the one you want to test.

2. Click "Start":

If the selected inventory item is ready for testing, the Start button will be active. Simply click it to initiate the penetration test.

⚡ _Prancer supports one-click pentesting—a novel feature in the industry that eliminates complex setup steps._

The inventory item could have been created through:

Autonomous Security Wizard

PAC (Pentest) Wizard

Manual PAC File Configuration

Regardless of the origin, the process to begin testing remains consistent.

Advanced Configuration: MITRE ATT&CK Integration

Prancer offers direct integration with the MITRE ATT&CK framework for more targeted and scenario-based pentesting.

To enable MITRE scenarios:

1. Select an inventory item from the list.

2. Click the hamburger menu.

3. Choose MITRE ATT&CK.

You will be presented with a full matrix of Techniques and Tactics. From here:

Select the desired MITRE items.

Save your configuration.

These selections ensure that specific SOC-driven scenarios are covered during the pentest.

PAC Configuration and Tags

Within every inventory item, the PAC Configuration (YAML-based manifest) plays a central role in defining how the test is conducted.

Tags as Test Drivers:

When MITRE techniques are selected, Prancer automatically adds them as Tags to the PAC file.

You can manually edit these tags to add, remove, or refine them.

After making changes, click Keep Changes to save your configuration.

Tags are not just metadata—they directly influence the selection of attack scenarios during testing.

Decentralized Offensive Security™

One of Prancer’s core innovations is its Decentralized Offensive Security™ architecture. This approach allows Prancer to:

Dynamically pull attack scenarios from multiple distributed code repositories

Match attack scenarios to your configured tags

Automatically execute those attacks as part of the pentesting process

This gives customers the ability to:

Scale and customize testing methodologies

Ingest and use attack scenarios from open source or proprietary sources

Ensure repeatable, testable logic aligned with organizational or compliance standards

✅ Example: If a PAC file includes a tag like SQL-Injection, and a repository contains a corresponding scenario, that scenario is automatically loaded and executed against the target.

Summary of Capabilities

| Feature | Description |

| One-Click Pentesting | Instantly launch tests from inventory without manual setup |

| MITRE ATT&CK Support | Load and test against real-world Tactics & Techniques |

| Tag-Driven Configuration | Tags in PAC files determine which attacks are launched |

| Distributed Attack Sources | Pulls attack logic from multiple remote repositories |

| SOC Enablement | Supports scenario-based testing for Security Operations teams |

Additional Screenshots

Additional screenshots, in order of appearance.