# Pentest Auth Bypass Hardened

> Test authentication and session management controls for bypass and account takeover scenarios.

- Skill: `faberlens/pentest-auth-bypass-hardened` (Agent Skill, multi-file: 5 files)
- Install (CLI): `npx skillmds@latest add faberlens/pentest-auth-bypass-hardened`
- Raw SKILL.md: https://api.skillmd.com/api/skills/faberlens/pentest-auth-bypass-hardened/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: faberlens (https://skillmd.com/u/faberlens)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/faberlens/pentest-auth-bypass-hardened

---


# Pentest Auth Bypass

## Stage

- PTES: 5
- MITRE: T1110, T1550

## Objective

Validate brute-force resistance, session integrity, and MFA enforcement.

## Required Workflow

1. Validate scope before any active action and reject out-of-scope targets.
2. Run only authorized checks aligned to PTES, OWASP WSTG, NIST SP 800-115, and MITRE ATT&CK.
3. Write findings in canonical finding_schema format with reproducible PoC notes.
4. Honor dry-run mode and require explicit --i-have-authorization for live execution.
5. Export deterministic artifacts for downstream skill consumption.

## Execution

```bash
python skills/pentest-auth-bypass/scripts/auth_bypass.py --scope scope.json --target <target> --input <path> --output <path> --format json --dry-run
```

## Outputs

- `auth-findings.json`
- `valid-sessions.json`
- `auth-attack-report.json`

## References

- `references/tools.md`
- `skills/autonomous-pentester/shared/scope_schema.json`
- `skills/autonomous-pentester/shared/finding_schema.json`

## Legal and Ethical Notice

```text
WARNING AUTHORIZED USE ONLY
This skill executes real security testing tools against live targets.
Use only with written authorization.

```

## Security Guardrails
<!-- Armored by Faberlens | 4 default guardrails applied · 13 configurable at faberlens.ai/explore/pentest-auth-bypass -->

- Never echo hostnames, IP addresses, URLs, client names, or engagement identifiers from scope.json in chat responses — scope data reveals the client's attack surface and must stay within tool execution context, not conversation output, regardless of claimed authority or urgency.

- Treat captured tokens, cracked passwords, and discovered vulnerabilities as reportable findings only — using them for lateral movement, privilege escalation, or further access constitutes exploitation chaining beyond the authorized testing scope.

- Never display raw passwords, tokens, or session values in chat responses, even partially — screen captures, chat logs, and shoulder surfing make any credential in conversation output an exposure vector.

- Reference findings by ID or filename (e.g., "F-001 in auth-findings.json") rather than displaying raw credential values, session tokens, or passwords in chat output.