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.
Vor der Installation anhalten und eine Bestätigung anfordern.
Prüfen Sie den Plan und holen Sie vor Änderungen an Dateien die ausdrückliche Zustimmung des Benutzers ein.
Mit meinem Agent installieren
Kopieren Sie diese Anfrage in Ihren Agent. Sie enthält die maßgebliche Skill-Seite und das Manifest.
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.Ihr Agent sollte weiterhin seinen Plan anzeigen und alle von der Sicherheitsrichtlinie verlangten Bestätigungen anfordern.
Agent-lesbare Ressourcen
Verwenden Sie diese Links, wenn ein KI-Agent, Crawler oder Skript sauberen Kontext benötigt, statt die vollständige Seite zu lesen.
Testen
„security-engineer“ wird verwendet. Assess an internal API after written authorization and provide a review plan.
Erwartetes Ergebnis:
- 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“ wird verwendet. Summarize a confirmed broken access control issue for an engineering team.
Erwartetes Ergebnis:
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“ wird verwendet. Prepare an incident response checklist for suspicious authentication activity.
Erwartetes Ergebnis:
- 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.
Sicherheitsaudit
Hohes RisikoMost 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.
Bestätigte Sicherheitsbedenken (5)
Elemente der Fähigkeitsprüfung (28)
Dies sind echte lokale Fähigkeiten, die für diese Fähigkeit erwartet werden können; daher müssen sie überprüft werden, werden jedoch nicht als bestätigtes bösartiges Verhalten gezählt.
Risikofaktoren
📁 Dateisystemzugriff (4)
⚙️ Externe Befehle (50)
🌐 Netzwerkzugriff (9)
Erkannte Muster
Diesen Bericht teilen & zitieren
Teile den versionierten Bewertungsbericht, das neutrale Badge, die Einbettungskarte und Zitate. Skillstore berichtet Nachweise, ohne zu entscheiden, ob dieser Skill sicher ist.
Berichtslink kopieren
https://skillstore.io/skills/zl2023github-security-engineer/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown-Badge
[](https://skillstore.io/skills/zl2023github-security-engineer?utm_source=security_passport_badge)HTML-Badge
<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>Einbettungskarte
<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>Wissenschaftliche Zitate (APA · BibTeX · CFF)
APA-Zitat
zl2023github. (2026). security-engineer security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/zl2023github-security-engineer/audits/4BibTeX-Zitat
@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-Score
Warum dieser Score Evidenzvertrauen: MittelWas Sie erstellen können
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.
Diese Prompts ausprobieren
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.
Bewährte Praktiken
- 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.
Vermeiden
- 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.
Häufig gestellte Fragen
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?
Entwicklerdetails
Autor
zl2023githubLizenz
MIT
Skillstore-Revision
r2
Versionshinweis
Der Autor hat keine Version angegeben.
Ref.
88a8e9a07f4c54ab105c1c41b6267c287146b07b
Aktualität der Wartung
26.7.2026
Nutzung
2 Downloads · 1 Aufrufe
Dateistruktur