Index of every page on this site: llms.txt
All skills
openai avatar

/attack-path-analysis

@ec0d6c1
by openaiopenai/codex-security14k stars
1,108
Run it yourself

Use when Codex is already in the attack-path-analysis phase of a security scan or the user explicitly asks to trace a security finding from source to sink and calibrate severity. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.

Use this Skill: https://skilld.dev/gh/openai/codex-security/attack-path-analysis

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesseverity-policy.md

≈661 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Severity and Policy Guidance

Apply this policy after establishing the attack path, scope, and counterevidence. Start from the candidate's severity hypothesis and adjust it using the impact, likelihood, prerequisites, and mitigations supported by the repository and supplied validation evidence. Do not reopen discovery during calibration.

Grade reportable findings with the scan's rubric or, when none is supplied, the default severity rubric.

For SSRF, a documented outbound-request feature or optional operator filter does not defeat a demonstrated destination-control bypass. For CSRF, evaluate browser credential attachment, cookie policy, preflight, request parsing, and effective controls; method or JSON content type alone is not a categorical defense. For XSS, distinguish self-only effects from victim impact; an alert reproduction proves script execution but does not alone establish the severity.

Reportability

  • Set ignore for a disproved finding or a bug without a meaningful security impact.
  • Do not discard a real, reportable finding solely because its impact or likelihood is low; use the corresponding lower severity.
  • Apply hard suppression to self-only impact or unachievable/highly unrealistic prerequisites.
  • Privileged-only, operator-only, developer-only, physical-access-only, or protected-write-path prerequisites imply ignore unless a privilege-escalation delta is the issue.
  • A realistic lower-privileged, in-scope attacker path can be established by repository evidence, supplied validation evidence, or both. Set ignore if the evidence does not support such a path.

Private or internal exposure alone does not suppress a supported authorization, identity, trust-boundary, or security-control failure in a real product or production workflow. Missing deployment or ingress evidence can lower confidence or leave facts unknown without defeating an otherwise supported finding.

Weight likelihood using the established attacker position and exposure:

  • remote usually supports high likelihood when the attacker position is realistic and in scope;
  • local_network usually supports medium likelihood unless the evidence supports a different level;
  • localhost usually supports low likelihood unless a lower-privileged attacker can realistically reach the listener;
  • none does not increase likelihood based on exposure.

Priority

Map the final reportable severity to a priority.

  • critical -> P0
  • high -> P1
  • medium -> P2
  • low -> P3

An ignored finding receives an ignore decision and severity, with no priority.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning1d3 checks · Risk SAFE
  • Gen Agent Trust Hub2d

    This skill provides a structured framework for analyzing security attack paths and calibrating finding severity. It includes a standard consideration for indirect prompt injection due to its processing of external security artifacts, which is handled through clear instructions for evidence-based validation.

  • Socket1d

    No alerts

  • Snyk2d

    Risk: MEDIUM · 1 issue

Signed by skilld at ec0d6c1. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 3 days ago

README badge

README badge for openai/codex-security/attack-path-analysis