Skip to content
Back to skills

Cyber Incident Triage

ASecurity

Status: `suspected`; host isolation is `blocked` because the approval scope is expired. The alert is not proof of credential theft, and severity reflects urgency/impact—not confirmation. - Preserve the original memory image read-only. Record its acquisition method, timestamp, custodian, hashes where available, and original reference; maintain chain of custody. The supplied custodian and timestamp are useful, but missing acquisition method, hash, or original reference are limitations. - Contin...

  • 571 stars
  • 0 votes
  • 1 copy
  • 1 view
  • Added September 24, 2026
developmentsecurity

Security analysis

A100/100

Pro scans all 15 files and shows the line behind each finding

Scanned September 24, 2026

npx -y skills add HoangNguyen0403/agent-skills-standard --skill cyber-incident-triage --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Cyber Incident Triage?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Cyber Incident Triage
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/hoangnguyen0403-cyber-incident-triage/badge)](https://www.skillsdirectory.com/skills/hoangnguyen0403-cyber-incident-triage)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
Status: `suspected`; host isolation is `blocked` because the approval scope is expired. The alert is not proof of credential theft, and severity reflects urgency/impact—not confirmation.

- Preserve the original memory image read-only. Record its acquisition method, timestamp, custodian, hashes where available, and original reference; maintain chain of custody. The supplied custodian and timestamp are useful, but missing acquisition method, hash, or original reference are limitations.
- Continue safe offline analysis only: assess the credential-theft hypothesis against the preserved image and alert context. Separate analysis from containment, eradication, and recovery.
- Do not isolate, scan, reset credentials, delete artifacts, or modify production. Missing or expired scope blocks active collection and response operations.
- Assign the incident-response owner and evidence custodian. Obtain a renewed engagement/scope reference, approved isolation operation, system/security owner, independent approval for disruptive containment, and runtime-proven permissions, credentials, network scope, and cancellation controls.
- After authorization, execute isolation under that scope and record the action and efficacy. Until then, preserve evidence and escalate the approval gap under NIST SP 800-61r3 and NIST SP 800-86.

Files in this skill

  • eval-1.baseline.md1 KB
  • eval-1.with-skill.md1.3 KB
  • eval-2.baseline.md361 B
  • eval-2.with-skill.md779 B
  • eval-3.baseline.md385 B
  • eval-3.with-skill.md884 B
  • pressure-1.baseline.md542 B
  • pressure-1.with-skill.md1.1 KB
  • pressure-2.baseline.md403 B
  • pressure-2.with-skill.md820 B
  • trigger-1.md136 B
  • trigger-2.md156 B
  • trigger-3.md158 B
  • trigger-4.md176 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…