exposure-validation

Continuous exposure validation (CTEM) — prove which vulnerabilities are actually exposed, exploitable and impactful in an authorized environment, then prove the exploit window is closed after remediation. Treats vulnerability, exposure, exploitability, impact, detection, remediation and verification as independent evidence-backed states. Triggers for: exposure management programme design, CTEM, breach and attack simulation planning, validating scanner findings, KEV rapid response, attack-path impact analysis, remediation verification, retesting, or proving risk reduction to leadership.

securityexposure-managementctemvalidationretestremediation-verificationattack-pathskevbasmitre-attackssvcnist-800-115ctem
01

Use it now

Single-file prompt

Every phase in one file · Intel as of unknown · 41 KB

Paste it into any chat AI, or add the file to a Project, Gem or custom instructions.

Download .md

Skill zip

SKILL.md, skill.json and references/ · 21 KB

Upload to Claude.ai (Settings → Capabilities → Skills) or unzip into any Agent Skills folder.

Download .zip
02

Phases

This skill has 6 authored phases. Each phase represents a distinct analysis step with its own context window.

01exposure-state-model1,799 tokens
02validation-authorization-and-scope1,581 tokens
03impact-and-attack-paths1,309 tokens
04evidence-and-confidence1,390 tokens
05remediation-verification1,403 tokens
06rapid-exposure-response1,389 tokens
03

Scope and authorization

  • Purpose: Prove which exposures are real, exploitable and closed, using the least invasive test under recorded approval.
  • Use only on systems you own or are explicitly authorized to assess.
  • Out of scope: any test without written authorization, explicit scope and named-human approval, and persistence, credential theft or lateral movement beyond what the test requires.
  • No network or API calls by the assistant: it never makes network requests, calls APIs or contacts outside services. Commands here are for a human operator to review and run. Redact secrets, credentials, personal data and samples before sharing anything.

A scanner finding is a hypothesis. This skill turns hypotheses into evidence: whether the vulnerability actually applies, whether it is reachable, whether it can be exploited in an environment you are authorized to test, what an attacker reaches through it, whether your controls noticed — and, after the fix, proof that the exploit window is closed.

04

Install the whole pack

Installs every Aegis skill, including this one, into your coding assistant.

Inside Claude Code:

Claude Code
/plugin marketplace add drupadsachania/aegis-skills
/plugin install aegis-skills@aegis-skills

Or from a terminal:

shell
npx aegis-skills install --platform claude

Prefer MCP? Connect the hosted Aegis MCP and ask for get_skill with name "exposure-validation".