Skip to content
Back to skills

Webapp Authenticated Surface Mapping

ASecurity

Mapping authenticated routes, role boundaries, and session behavior for authorized access-control…

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
securitygobashtesting

Security analysis

A96/100
  • mediumUses curl or wget to download content

Pro shows the line behind each finding and how to fix it

Scanned November 7, 2026

npx -y skills add bitbytelabio/arsenal --skill webapp-authenticated-surface-mapping --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Webapp Authenticated Surface Mapping?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Webapp Authenticated Surface Mapping
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/bitbytelabio-webapp-authenticated-surface-mapping/badge)](https://www.skillsdirectory.com/skills/bitbytelabio-webapp-authenticated-surface-mapping)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: webapp-authenticated-surface-mapping
description: Mapping authenticated routes, role boundaries, and session behavior for authorized access-control…
domain: webapp
category: authz
hide: true
license: Apache-2.0
metadata:
  manifest_entry: src/corpus/webapp-authenticated-surface-mapping/SKILL.md
---
# Authenticated Surface Mapping

## When to Use
When the target has authentication and you have credentials (operator-supplied or discovered). If no credentials exist, mark this dimension "blocked" and continue.

## Prerequisites
- At least one valid account/session
- Do NOT brute-force credentials or create accounts on production systems without authorization

## Methodology

### Login Flow Analysis
```bash
# Capture the login request
curl -sk -X POST https://TARGET/login -H "Content-Type: application/json" \
  -d '{"username":"user","password":"pass"}' -D tmp/login_headers.txt

# Record: session cookie name, token format, redirect target, error messages
```

### Authenticated Route Discovery
```bash
# Compare anonymous vs authenticated surface
curl -sk https://TARGET/ -o tmp/anon.html
curl -sk https://TARGET/ -H "Cookie: SESSION=test" -o tmp/auth.html
diff tmp/anon.html tmp/auth.html | head -50
```

### Role Boundary Mapping
If multiple roles exist (admin/user/readonly):
```bash
# For each role, capture the accessible routes
curl -sk https://TARGET/admin -H "X-Auth-Token: ADMIN_TOKEN" -o tmp/admin_view.html
curl -sk https://TARGET/admin -H "X-Auth-Token: USER_TOKEN" -o tmp/user_view.html
```

### Session Token Analysis
```bash
# Record the session mechanism: cookie, JWT, Bearer token, custom header
# Record expiry, refresh, logout behavior
```

## Stopping Criteria
- Login flow understood (method, endpoint, session format)
- Authenticated-only routes identified
- Role differences mapped (if multiple roles exist)
- Session mechanism documented

## When Blocked
If no credentials exist:
- Mark the auth-surface dimension as blocked
- Document what was observed about the auth mechanism anonymously
- Continue with unauthenticated testing

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.