---
name: ethical-hacker
description: "Produces authorised security test scenarios for a named system, each with attack steps, expected defences and what to log, tied to your concerns and compliance needs. Use when a security owner needs structured penetration test or attack simulation scenarios for a system they are authorised to test. Do not use for exploiting systems without permission or writing working malware. Related topics: cybersecurity, hacking, ethical."
---

# Ethical Hacker

Produces authorised security test scenarios for a named system, each with attack steps, expected defences and what to log, tied to your concerns and compliance needs.

## When to use

Use this skill when a security owner needs structured penetration test or attack simulation scenarios for a system they are authorised to test. Do not use it for exploiting systems without permission or writing working malware.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Restate the system, scope and authorisation assumptions so every scenario sits inside an agreed boundary.
3. Map each stated vulnerability concern to the parts of the system most exposed to it, given the measures already in place.
4. Write each scenario with tester steps at method level, the expected defence, evidence to capture and the fix if it fails.
5. Order the scenarios by risk and align them to the desired outcome and any compliance requirement.

## Inputs

- **System type** (choose one: Network, Database, Application, Website)
- **System description** (longer free text)
- **Number of users** (number from 1 to 1000)
- **Vulnerabilities I am worried about** (choose any: SQL Injection, Cross-Site Scripting, Password Cracking, Phishing)
- **Security measures already in place** (longer free text)
- **Scenario type** (choose one: Simulated Attack, Penetration Test)
- **Goal of the scenario** (free text, e.g. "what the test should prove")
- **Desired outcome** (choose one: Identify Vulnerabilities, Test Incident Response, Evaluate Security Measures)
- **Compliance requirements** (free text, e.g. "PCI DSS or none")
- **Number of scenarios** (number from 1 to 10)

## Output

Scope notes followed by the requested number of scenarios, each with target, steps, expected defence, evidence to log and remediation, ordered by risk.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### Ethical Hacking Scenario Builder

Design security test scenarios for a system I am authorised to test. Treat this as defensive work: every scenario must end with detection and fix guidance.

- System type: {{System type}}
- System description: {{System description}}
- Number of users: {{Number of users}}
- Vulnerabilities I am worried about: {{Vulnerabilities I am worried about}}
- Security measures already in place: {{Security measures already in place}}
- Scenario type: {{Scenario type}}
- Goal of the scenario: {{Goal of the scenario}}
- Desired outcome: {{Desired outcome}}
- Compliance requirements: {{Compliance requirements}}
- Number of scenarios: {{Number of scenarios}}

For each scenario give a title, the target and assumptions, the tester steps in order at the level of method (not working exploit code), the defence expected to stop it, what evidence to capture, and the fix if it succeeds. Match scenarios to the stated concerns first, then to gaps the existing measures leave open. Begin with scope and rules of engagement, and remind me to get written authorisation before any test.

## Pitfalls

- Including working exploit code, which turns a test plan into an attack tool.
- Skipping written authorisation and scope, which makes the test itself a legal risk.
- Ignoring the existing controls, so scenarios test defences that are already covered.
