CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cyber-detection-validation

Validates defensive controls with paired authorized action and observation evidence, distinguishing blocked, prevented, detected, responded, and telemetry-gap outcomes. Use for purple-team validation design or offline fixture review; not unsanctioned testing or production efficacy claims.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Cyber Detection Validation

Priority: P0 (CRITICAL)

No defensive outcome without linked action and observation evidence.

Input: control hypothesis, permitted action, scope/approval, mode (analysis, replay, isolated-lab-validation, defensive-verification), entity, window, expected observation, stop condition. Process: classify active effects (active: true for any interaction outside supplied-artifact reasoning; reading supplied events/files is non-active analysis); verify fresh host gate before active actions; capture ActionReceipt and ObservationRecord; enforce transitive binding chain: ObservationRecord.action_receipt_ref -> ActionReceipt.gate_ref -> GateDecision.request_ref -> ActionRequest. Output: purple outcome enum, finding status, evidence references, limitations, stage fidelity, owner.

Workflow

  1. Declare step mode and effects: analysis, replay, isolated-lab-validation, or defensive-verification.
  2. Preflight host gate for active effects: evaluate ActionRequest and GateDecision immediately before dispatch.
  3. Execute bounded action; bind ActionReceipt to correlation key (run_id, attempt_id, test_id).
  4. Capture ObservationRecord within defined time window; enforce unique observation_id and transitive binding chain.
  5. Classify purple defensive outcome: blocked, prevented, detected, responded, or telemetry-gap.
  6. Report stage fidelity: replay reports only exercised stages (e.g., parsing/correlation); lab reports observed sensor/control stages.
  7. Run teardown plan; record CleanupResult (verified-clean, residual, unverified, not-applicable).

Rules

  • Active operations require fresh host capability proofs; reading supplied synthetic events without host mutation is non-active analysis. Mode never overrides active effects classification.
  • Controlled synthetic fixtures only. No real credentials, malware, production targets, or data exfiltration.
  • Mandatory transitive binding: ObservationRecord must uniquely resolve through ActionReceipt to GateDecision. Cross-run, cross-fixture, or conflicting keys are rejected.
  • Replay stage fidelity: Replay of supplied synthetic events reports only exercised processing stages (e.g., ingestion, correlation), never sensor acquisition or prevention unless independently evidenced (AC-CLV-02).
  • Telemetry gap: An exercised action without usable matching observation is telemetry-gap (AC-CLV-12). An observation alone cannot prove an action occurred.
  • Purple enum definitions: blocked: denied or could not run; prevented: control stopped action; detected: observation identified behavior; responded: independently evidenced approved response; telemetry-gap: action exists without observation.
  • Teardown disclosure: Incomplete or unverified cleanup reports residual or unverified with accountable owner (AC-CLV-13).
  • Carry shared evidence fields from cyber-evidence and use lab execution gate when validating in labs.

Anti-Patterns

  • Never label blocked as prevented or observation-only as detected.
  • Never infer response from detection or claim efficacy/compliance from documentation.
  • Never simulate a successful action when runtime or approval is absent.

References

  • Shared evidence record
  • Lab validation and evidence record
  • Runtime authorization matrix
  • NIST SP 800-115: https://doi.org/10.6028/NIST.SP.800-115
  • MITRE ATT&CK Evaluations: https://attackevals.mitre-engenuity.org/
Repository

HoangNguyen0403/agent-skills-standard

Path

.agents/skills/cybersecurity/cyber-detection-validation/SKILL.md

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.