Files
NeuroSploit/examples/scopes/nasa.yaml
T
CyberSecurityUPandClaude Opus 4.8 3a820f09e6 feat: one-file engagement configs; scope-file reseeds stale target; English UI + any-language input; docs
- /scope-file now reads optional engagement keys from the SAME YAML (target,
  models, focus, objective, authorization, classes) so one file defines the
  whole engagement, not just scope. examples/scopes/nasa.yaml and
  engagement.example.yaml show the keys.
- When importing a scope (/scope-file) or declaring one (/authorize), a target
  left over from a previous session that falls OUTSIDE the new scope is reset to
  a host inside it (was: silently kept, then denied on /run — the "nothing
  changed" confusion). Added scope_seed_target() + in_hard_scope() check.
- UI/help strings are English; the natural-language REPL still accepts input in
  any language (the two example lines are now English).
- README + TUTORIAL updated: new REPL commands (/authorize, /scope-file, /class,
  /research, /quick, /authorization, /guardrail), a "Scope — three ways" section
  with the one-file YAML, version/counts refreshed to 4.2.1 / 480 agents.

422 tests passing.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-10-04 00:03:50 -03:00

74 lines
3.4 KiB
YAML

# ===========================================================================
# NeuroSploit scope config — NASA (TEMPLATE)
# ---------------------------------------------------------------------------
# ⚠ BEFORE YOU RUN: confirm this matches NASA's CURRENT VDP scope.
# NASA Vulnerability Disclosure Policy: https://www.nasa.gov/nasa-vulnerability-disclosure-policy/
# (coordinated via https://bugcrowd.com/nasa-vdp). Open the policy/program
# page and align `hard` / `exclude` with the EXACT in- and out-of-scope assets
# it lists today. A VDP is for good-faith disclosure — follow its rules.
#
# `*.nasa.gov` authorizes the apex AND every subdomain, so NeuroSploit's recon
# will enumerate subdomains and test within this boundary. NASA runs MANY
# subdomains/mission sites; several are explicitly out of scope and some are
# third-party hosted — verify before testing.
#
# Import it:
# neurosploit run "*.nasa.gov" --scope-file examples/scopes/nasa.yaml --subscription
# or in the REPL:
# /scope-file examples/scopes/nasa.yaml
# /authorization https://www.nasa.gov/nasa-vulnerability-disclosure-policy/
# /target *.nasa.gov
# /run
# ===========================================================================
# --- Optional: define the whole engagement in this one file -----------------
# These top-level keys are read by `/scope-file` (and ignored by the CLI's
# --scope-file, which only reads scope). All optional.
target: "*.nasa.gov" # seed; must fall inside `hard` below
# models: # provider:model list (uncomment to pin)
# - anthropic:claude-opus-5-5
# classes: idor, ssrf, xss # focus the run on these vuln classes
focus: "prioritize auth, access control and SSRF on in-scope subdomains"
authorization: "https://www.nasa.gov/nasa-vulnerability-disclosure-policy/"
# --- HARD: the allowlist. Only these are testable. ------------------------
hard:
- "*.nasa.gov" # apex + every subdomain (VERIFY against the VDP)
- nasa.gov
# --- EXCLUDE: carve-outs that always beat the allowlist. ------------------
# Fill from the VDP's OUT-OF-SCOPE list. Typical for a large gov org: auth/SSO
# providers, third-party-hosted services, APIs with their own terms, and any
# system the policy names as excluded. Examples are PLACEHOLDERS — verify.
exclude:
# - auth.launchpad.nasa.gov
# - "*.ndc.nasa.gov"
# - api.nasa.gov # has its own API terms / key system — check first
# --- SOFT: guardrails inside the boundary (VDP-safe, conservative) ---------
soft:
observe_only: []
# No state-mutating verbs, no account creation — a government VDP expects
# minimal-impact, good-faith testing.
allow_destructive_methods: false
allow_account_creation: false
max_accounts: 0
# Low rate: these are production government systems.
max_requests_per_minute: 60
forbidden_payloads:
- "drop table"
- "truncate table"
- "delete from"
- "rm -rf /"
- "shutdown"
- "while(true)"
notes:
- "Authorized under NASA's Vulnerability Disclosure Policy (good-faith research only)."
- "No DoS, no social engineering, no physical testing, no disruption of operations or spacecraft/mission systems."
- "Access only the minimum data needed to demonstrate a vulnerability; never exfiltrate or retain PII/ITAR/sensitive data; stop and report if you encounter it."
- "Verify in/out-of-scope on the VDP page before each run — scope changes."