Status: **blocked** Assumption: this is a live DNS threat-hunting query; no entities, time window, query text, or engagement/scope reference were supplied. I cannot run it because: - DNS collection is disabled, so the dataset is unavailable/incomplete. - No `cyber-authorization` or engagement/scope reference exists. - Active collection or network operations require documented scope and runtime-proven controls. No query was executed, and no evidence or hunt metrics were generated. This is **no...
Pro scans all 11 files and shows the line behind each finding
Scanned 9/24/2026
Skills Directorynpx -y skills add HoangNguyen0403/agent-skills-standard --skill cyber-threat-hunting --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Cyber Threat Hunting?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/hoangnguyen0403-cyber-threat-hunting-2b4ead97)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
Status: **blocked**
Assumption: this is a live DNS threat-hunting query; no entities, time window, query text, or engagement/scope reference were supplied.
I cannot run it because:
- DNS collection is disabled, so the dataset is unavailable/incomplete.
- No `cyber-authorization` or engagement/scope reference exists.
- Active collection or network operations require documented scope and runtime-proven controls.
No query was executed, and no evidence or hunt metrics were generated. This is **not** a clean result and does not support a negative conclusion.
To proceed:
1. Provide the engagement/scope reference and authorization under `cyber-authorization`.
2. Enable DNS telemetry for the approved scope and window.
3. Preserve the original records and provenance under `cyber-evidence`, including query/version, fixture or source provenance, retention, clock, identity, and source limitations.
4. Run the narrowest query, correlate by entity and time, and map findings through `cyber-framework-mapping` using MITRE ATT&CK data sources.
5. Record status as `confirmed`, `suspected`, `false-positive`, `blocked`, or `not-tested`, with evidence references, limitations, observation time, skill/version/source, and an accountable owner.
Observation time: **2026-09-22, Asia/Ho_Chi_Minh**.
Evidence references: **none**.
Owner: **unassigned hunt owner/requester**.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
