> ## Documentation Index
> Fetch the complete documentation index at: https://docs.noscope.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Application details

> The first step of the wizard is a quick sanity check on what we're about to pentest. Nothing fancy here, just three fields that help us scope the work and gi...

The first step of the wizard is a quick sanity check on what we're about to pentest. Nothing fancy here, just three fields that help us scope the work and give you a useful report at the end.

## What you'll enter

<Steps>
  <Step title="Application name">
    Whatever makes sense to your team. Something like Customer Portal (Prod) or Mobile API v2 works well. This is the name you'll see in lists, reports, and scan history, so pick something you'll recognize months from now.
  </Step>

  <Step title="Why do you need a pentest">
    A short dropdown on your reason for running this. Compliance, pre-launch sign-off, recurring security review, incident follow-up, that kind of thing. It's a generic question, but your answer tells the agent where to bias coverage and what to emphasize in the report.
  </Step>

  <Step title="Environment">
    Which environment the agent will hit. Staging, pre-prod, or production. If you're setting this up for the first time, pointing at staging is the safer call. Production is fine once you know what you're getting, but go in with your team on alert.
  </Step>
</Steps>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.