security-engineer
Audit Systems and Applications Securely
Security reviews require consistent scope, evidence, and remediation guidance across many tools. This skill provides practical workflows for authorized assessment, monitoring, hardening, and reporting.
インストール前に停止して確認を求めてください。
計画を確認し、ファイルを変更する前にユーザーの明示的な同意を得てください。
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
Review the Skillstore skill "security-engineer" from https://skillstore.io/skills/zl2023github-security-engineer.md and its manifest at https://skillstore.io/api/skills/zl2023github-security-engineer/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「security-engineer」を使用しています。 Assess an internal API after written authorization and provide a review plan.
期待される結果:
- Scope: the approved API hosts, accounts, methods, and testing window.
- Sequence: passive review, low-impact validation, approved active checks, manual confirmation, and reporting.
- Evidence: timestamps, affected endpoints, sanitized requests, observed impact, and tool versions.
- Stop conditions: unexpected service degradation, scope uncertainty, or sensitive data exposure.
「security-engineer」を使用しています。 Summarize a confirmed broken access control issue for an engineering team.
期待される結果:
High severity: a standard user can access another account record by changing its identifier. Enforce server-side ownership checks and add negative authorization tests.
「security-engineer」を使用しています。 Prepare an incident response checklist for suspicious authentication activity.
期待される結果:
- Validate the alert source, affected identities, time range, and authentication method.
- Preserve relevant identity, application, endpoint, and network evidence.
- Contain confirmed abuse while protecting evidence and required business access.
- Document recovery criteria, monitoring changes, owners, and follow-up actions.
セキュリティ監査
高リスクMost critical static alerts are false positives caused by defensive examples, public references, and Markdown syntax. Actionable scanning, sensitive-data inspection, destructive removal, and an unaudited hidden-path script remain confirmed risks. The broad post-exploitation workflow creates additional high dual-use risk despite its authorization reminder.
確認済みのセキュリティ上の懸念 (5)
機能レビュー項目 (28)
これらは、このスキルに期待される可能性のある実際のローカル機能であるため、レビューが必要ですが、確認済みの悪意ある動作としてはカウントされません。
リスク要因
📁 ファイルシステムへのアクセス (4)
⚙️ 外部コマンド (50)
検出されたパターン
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/zl2023github-security-engineer/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/zl2023github-security-engineer?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/zl2023github-security-engineer?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/zl2023github-security-engineer/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/zl2023github-security-engineer.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>学術引用 (APA · BibTeX · CFF)
APA形式の引用
zl2023github. (2026). security-engineer security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/zl2023github-security-engineer/audits/4BibTeX形式の引用
@techreport{zl2023github-zl2023github-security-engineer-2026,
author = {zl2023github},
title = {security-engineer security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/zl2023github-security-engineer/audits/4},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "security-engineer security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "zl2023github"
date-released: "2026-07-24"
url: "https://skillstore.io/skills/zl2023github-security-engineer/audits/4"
identifiers:
- type: other
value: "skillstore:zl2023github-security-engineer:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
Review Application Security
Assess code and application behavior, validate scanner findings, and prepare prioritized remediation guidance.
Build DevSecOps Controls
Select source, dependency, container, and configuration checks for a controlled delivery pipeline.
Investigate Security Alerts
Organize triage, evidence collection, containment, recovery, and post-incident reporting.
これらのプロンプトを試す
Create an authorized security review plan for [system]. Define scope, assumptions, evidence, low-impact checks, approval gates, and report sections.
Review [repository or files] for injection, access control, secret handling, unsafe uploads, SSRF, XXE, and deserialization risks. Explain evidence and fixes.
Design security checks for [stack and pipeline]. Include SAST, dependency, secret, container, and configuration scanning with validation and release criteria.
Build an incident workflow for [alert and environment]. Prioritize preservation, triage, containment, forensic questions, recovery criteria, communication, and lessons learned.
ベストプラクティス
- Confirm written authorization, exact targets, timing, and stop conditions before active testing.
- Use least-impact checks first and request separate approval before exploitation or destructive actions.
- Redact sensitive evidence, validate automated findings manually, and record reproducible remediation steps.
回避
- Do not scan public or third-party targets without verified authorization.
- Do not run destructive flags or broad filesystem commands without backups, bounded paths, and confirmation.
- Do not report scanner output as confirmed vulnerabilities without manual evidence and impact analysis.
よくある質問
Does this skill perform penetration testing automatically?
Can it review source code?
Does it replace a security professional?
Can it support incident response?
Which security standards does it reference?
What should I provide before using it?
開発者情報
作成者
zl2023githubライセンス
MIT
Skillstore リビジョン
r2
バージョンに関する注意
作者はバージョンを宣言していません。
参照
88a8e9a07f4c54ab105c1c41b6267c287146b07b
メンテナンスの新しさ
2026/7/26
利用状況
2 ダウンロード · 1 閲覧
ファイル構成