Agent Skills › usestrix/strix › application-security-testing

application-security-testing

GitHub

基于Strix工具进行应用安全测试,自动识别资产并选择对应测试技能(代码、Web、API等),通过自主代理执行漏洞利用验证,最终生成按实际可访问性排序的修复计划。

skills/application-security-testing/SKILL.md usestrix/strix

触发场景

需要进行应用安全审查或审计 请求应用安全评估或漏洞扫描 发布前的安全检查 不确定需要哪种安全测试时

安装

npx skills add usestrix/strix --skill application-security-testing -g -y
更多选项

不安装直接使用

npx skills use usestrix/strix@application-security-testing

指定 Agent (Claude Code)

npx skills add usestrix/strix --skill application-security-testing -a claude-code -g -y

安装 repo 全部 skill

npx skills add usestrix/strix --all -g -y

预览 repo 内 skill

npx skills add usestrix/strix --list

SKILL.md

Frontmatter
{
    "name": "application-security-testing",
    "license": "Apache-2.0",
    "metadata": {
        "author": "usestrix",
        "homepage": "https:\/\/docs.strix.ai"
    },
    "description": "Application security testing (AppSec) across a whole product with Strix — decide which asset needs which test (source code, running web app, API, CI pipeline), run it, and turn the results into a ranked remediation plan. Autonomous agents exploit and prove each issue instead of emitting static-analysis alerts, so the plan is ordered by what is actually reachable. Use when the user asks for an application security review or audit, an appsec assessment, vulnerability scanning across their stack, a security review before a launch or a customer security questionnaire, or does not yet know which kind of security test they need."
}

Application security testing

Entry point for "make my application secure" requests, where the target is not yet a single URL or repo. The job here is to pick the right test per asset, run it, and produce one ranked plan — not to run everything at maximum depth.

Install, LLM setup, all CLI flags, and the managed-cloud path live in the penetration-testing-with-strix skill. Read it first 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).

Only test assets the user owns or is authorized to test. Confirm authorization before the first run, and prefer staging over production, because the agents send real exploit payloads and can change data.

1. Map the assets

Ask (or read from the repo) and write the answers down before scanning:

  • Source — one repo, a monorepo, several services? Which languages/frameworks?
  • Running environments — is there a staging deployment? A public production site? A local dev server only?
  • APIs — REST, GraphQL, gRPC? Is there an OpenAPI/GraphQL schema?
  • Authentication — can you get two test accounts in different tenants? Most high-impact bugs need them.
  • Constraints — out-of-scope paths, whether production may be touched, budget and wall-clock limits.

If there is no staging environment and production is off limits, say so early. A code-only review is still valuable, but it cannot prove exploitability against a live app.

2. Pick the right test per asset

Asset Skill to use
Repository or working tree find-security-vulnerabilities-in-code
Live web app or staging site web-app-penetration-testing
REST/GraphQL/gRPC API api-security-testing
Assessment mapped to OWASP categories owasp-top-10-testing
Every pull request, continuously ci-security-scanning-with-strix
No Docker, no LLM key, or a report an auditor will accept managed-pentesting-with-strix

Those skills carry the flags, credential handling, and result-reading details. Do not duplicate their instructions here.

Sequence for a first assessment:

  1. Review the code. It is the cheapest run and it maps the authorization model.
  2. Pentest staging with credentials, and pass the repo as a second target so the agents keep source context.
  3. Add CI scanning, so later regressions are caught without another manual pass.

Run one asset at a time and read each report before starting the next. Findings from the code review make the live run sharper.

3. Consolidate into one plan

Findings arrive per run in strix_runs/<run>/. Merge them into a single list and rank by proven impact, not by scanner severity:

  1. Validated exploits reachable without authentication.
  2. Validated cross-tenant or privilege-escalation issues.
  3. Validated issues needing an authenticated account.
  4. Unproven observations (configuration, dependency, and hardening notes) — flag as such, and never present them as confirmed vulnerabilities.

Deduplicate: the same root cause often surfaces in both the code review and the live pentest.

4. Be honest about coverage

State plainly what was not tested — assets with no staging environment, categories a black-box run cannot reach (logging and alerting, supply-chain integrity, insecure design), and any run that hit its budget or turn cap before finishing. Check run.json status and cost against --max-budget for each run. An empty result set from a truncated scan is not a clean bill of health.

Then remediate with fix-security-vulnerabilities-with-strix, which re-runs Strix against each fix to prove the exploit no longer works.

版本历史

  • 56e9ae9 当前 2026-09-22 22:58

    更新所有相关技能以指向 Strix Cloud CLI

  • 717ffc8 2026-08-28 20:29

同 Skill 集合

skills/managed-pentesting-with-strix/SKILL.md
skills/api-security-testing/SKILL.md
skills/ci-security-scanning-with-strix/SKILL.md
skills/find-security-vulnerabilities-in-code/SKILL.md
skills/fix-security-vulnerabilities-with-strix/SKILL.md
skills/owasp-top-10-testing/SKILL.md
skills/penetration-testing-with-strix/SKILL.md
skills/web-app-penetration-testing/SKILL.md

元信息

文件数
0
版本
a0f8ea2
Hash
b3041c80
收录时间
2026-08-28 20:29

首页 - Wiki
Copyright © 2011-2026 iteam. Current version is 2.156.0. UTC+08:00, 2026-11-22 08:31
浙ICP备14020137号-1