跳到正文
cccskills
免费在 GitHub 公开

web-app-penetration-testing

Test a running web application with Strix to find authentication, access control, and other security flaws. Review working proof-of-concept exploits, which demonstrate each issue, and use the evidence to guide fixes and retesting.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

Pentest a web app or website end to end — black-box testing of a live URL, staging environment, or local dev server that finds and exploits real vulnerabilities (auth bypass, broken access control, IDOR, injection, XSS, SSRF, business logic) and proves each one with a working proof-of-concept instead of a signature match. Runs with Strix, either the self-hosted open-source CLI or the managed app.strix.ai cloud. Use when the user asks to pentest, hack, security-test, or audit their web app, website, web application, or staging site.

集成工具Docker
查看安装方法

适用场景

  • Security testing a staging web application
  • Checking access between accounts and organizations
  • Testing a local development server
  • Reviewing exploit evidence before retesting fixes

包含的文件(1)

  • SKILL.md4.2 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Pentest a web application

Black-box (and optionally source-assisted) penetration testing of a running web app with Strix's autonomous agents. Every reported finding is validated with a working exploit, so there are no signature-based false positives to triage.

Install, LLM setup, all CLI flags, and the managed-cloud alternative are covered in the penetration-testing-with-strix skill — read it if the target is not a running web app, or if strix --version fails. For a run with no Docker and no LLM key, the same binary drives the managed platform: strix cloud login, then strix cloud scans start ... (details in managed-pentesting-with-strix). This skill is the web-app-specific workflow.

1. Confirm authorization and scope

Before running anything, establish:

  • The target is the user's (or they are explicitly authorized to test it). Never pentest a third-party site on a hunch.
  • Which environment. Prefer staging over production; agents send real exploit payloads and will create/modify data.
  • Out-of-scope paths — payment flows, mass-email endpoints, admin destructive actions, third-party SSO providers.
  • Credentials. Most real vulnerabilities live behind login. Without a test account, the agents only ever see the marketing surface.

Ask for anything missing rather than guessing.

2. Run the scan

strix -n -t https://staging.example.com --max-budget 20 \
  --instruction "Test account: qa@example.com / <password>. In scope: /app/*, /api/*. Do not touch /billing or send email. Focus on access control between the two seeded orgs."

Notes that matter for web apps specifically:

  • Give it credentials via --instruction (or --instruction-file for anything long), including how to log in if the flow is unusual (magic link, SSO, MFA-exempt test user).
  • Two accounts beat one. Multi-tenant IDOR and broken-access-control bugs — consistently the highest-impact class in web apps — can only be proven when the agent can attempt cross-account access.
  • Add the repo for white-box depth when you have the source: -t https://github.com/org/app -t https://staging.example.com (or a local path). Source access materially improves coverage of business-logic and authorization flaws.
  • Localhost works. Point at http://host.docker.internal:3000 (Docker Desktop) so the sandbox can reach a dev server on the host.
  • --scan-mode quick for a fast dev-loop pass, standard (~30 min) for a normal review, deep for pre-release assurance. Always set --max-budget.

For a hosted run with no Docker/LLM key, or when the user wants a shareable dashboard and an auditor-ready PDF, use the cloud path in managed-pentesting-with-strix instead — same engine, same findings.

3. Review results

Read strix_runs/<run>/penetration_test_report.md first, then per-finding files in vulnerabilities/. Each contains the PoC — re-run it yourself to confirm before reporting to the user.

Exit codes: 0 no validated vulns in what was analyzed, 2 vulnerabilities found, 1 fatal error. A 0 is not proof of full coverage — if the budget or turn cap was hit the scan wraps up early, so check run.json status and cost against --max-budget before calling the app clean.

4. Fix and verify

Hand findings to the fix-security-vulnerabilities-with-strix skill: patch the root cause, then re-run Strix against the same target to prove the exploit no longer works. Re-testing is the only reliable confirmation a fix landed.

To keep the app tested on every change rather than once, wire Strix into CI with ci-security-scanning-with-strix.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Test REST, GraphQL, and gRPC APIs with Strix using schemas, credentials, and example data. Investigate authorization flaws, excessive data exposure, and other API risks, then verify findings with requests that reproduce the issue.

中文简介正在准备中。当前显示英语简介。

  • Testing an API from its specification
  • Checking data access across tenants
  • Verifying restrictions on administrator routes
usestrix/strix7万2026年10月18日 更新

Plan and coordinate Strix security assessments across source code, running applications, APIs, and continuous integration pipelines. Combine findings into one prioritized remediation plan based on demonstrated impact, removing duplicates and documenting gaps in test coverage.

中文简介正在准备中。当前显示英语简介。

  • Choosing suitable security tests for a product
  • Planning a security assessment before launch
  • Combining findings into a prioritized remediation plan
usestrix/strix7万2026年10月18日 更新

Set up Strix security checks in CI/CD to test pull request changes, report verified vulnerabilities, and gate merges. Covers both a CLI running on your own infrastructure and a managed service with pull request comments.

中文简介正在准备中。当前显示英语简介。

  • Check pull request changes for vulnerabilities before merging
  • Add Strix scans to GitHub Actions or GitLab CI
  • Choose between managed reviews and scans on your own runners
usestrix/strix7万2026年10月18日 更新

Review source code with Strix to trace data flow and authorization checks, then test suspected vulnerabilities in a running environment. Receive proven findings with exploit examples and code locations, while keeping unconfirmed observations clearly identified.

中文简介正在准备中。当前显示英语简介。

  • Reviewing a repository for security vulnerabilities
  • Checking authorization logic in a specific service
  • Reviewing security risks introduced by a branch
usestrix/strix7万2026年10月18日 更新

Turn Strix vulnerability findings into focused code fixes, prioritized by severity. Address root causes, rerun security scans and original exploit examples, and report the changes and verification results for each issue.

中文简介正在准备中。当前显示英语简介。

  • Fixing vulnerabilities reported by Strix
  • Prioritizing remediation by severity
  • Retesting original exploits after code changes
usestrix/strix7万2026年10月18日 更新

Run security tests for web apps, APIs, and source code on Strix Cloud without local Docker or an LLM key. Register targets, review findings in a team dashboard, export results, and configure recurring scans or PR reviews.

中文简介正在准备中。当前显示英语简介。

  • Running security tests without local Docker
  • Tracking vulnerability status across a team
  • Scheduling scans and starting PR security reviews
usestrix/strix7万2026年10月18日 更新

查看 usestrix 的全部技能

报告此技能的问题