GitHub Defense Suite — CYBER Defense Contour

Mission

Provide 30 governed CYBER Defense NCA with defensive security knowledge, routing, detection engineering, secure-code review, vulnerability/SBOM analysis, secret detection, runtime/network monitoring, endpoint visibility, malware signature analysis, and software supply-chain verification.

Authority boundary

DEFENSIVE_ONLY; AUTHORIZED_IMPERIAL_ASSETS_ONLY; NO_RETALIATION; NO_OFFENSIVE_INTRUSION; NO_FALSE_ATTRIBUTION; T3_AUTONOMOUS_ALWAYS_DENY; APPROVAL_GATE_REQUIRED_FOR_HIGH_IMPACT_ACTIONS.

Verified upstream capability packs

  • SigmaHQ/sigma — SIGMA-DETECTION — portable detection rules.
  • aquasecurity/trivy — TRIVY-SCAN — vulnerability/misconfiguration/artifact scanning.
  • gitleaks/gitleaks — GITLEAKS-SECRETS — repository secret detection.
  • semgrep/semgrep — SEMGREP-SAST — static application security analysis.
  • falcosecurity/falco — FALCO-RUNTIME — runtime/container detection.
  • zeek/zeek — ZEEK-NSM — network security monitoring.
  • OISF/suricata — SURICATA-IDS — IDS rules/events; IPS requires approval.
  • osquery/osquery — OSQUERY-ENDPOINT — endpoint read-only visibility.
  • VirusTotal/yara — YARA-MALWARE — defensive signature matching; never execute malware.
  • ossf/scorecard — OPENSSF-SCORECARD — supply-chain posture scoring.
  • anchore/syft — SYFT-SBOM — SBOM generation/interpretation.
  • anchore/grype — GRYPE-VULN — vulnerability analysis.
  • google/osv-scanner — OSV-SCANNER — dependency vulnerability analysis.
  • sigstore/cosign — COSIGN-VERIFY — signature/provenance verification; signing needs approval.
  • github/codeql — CODEQL-SAST — semantic code security analysis.
  • trufflesecurity/trufflehog — TRUFFLEHOG-SECRETS — secret discovery; never log raw secret values.

Runtime truth boundary

INSTALLED_SKILL_PACK means the NCA has reviewed workflow/routing knowledge and an explicit governed capability binding. It does NOT mean every upstream native binary is running inside Val Town. Native Linux/CI/network engines remain EXTERNAL_ENGINE_REQUIRED until a compatible worker, CI job, or sensor is deployed and live-tested. Do not report NATIVE/LIVE without evidence.

Operating sequence

ASSET/SCOPE -> PASSIVE OBSERVE -> DETECT -> VALIDATE -> CLASSIFY -> SAFE REMEDIATION PROPOSAL -> APPROVAL GATE IF HIGH IMPACT -> VERIFY -> EVIDENCE SHA-256 -> HANTER REPORT.

Safety

  • Never scan or test third-party systems without explicit authorization.
  • Never exploit a finding to prove it.
  • Never reveal recovered credentials/secrets; report only redacted metadata/hashes.
  • Network tools are passive IDS/NSM by default. Blocking/IPS changes require approval and rollback plan.
  • Unknown is not PASS.
  • PROTECTIVE_READY != PROOF_AN_EXTERNAL_ATTACK_WAS_BLOCKED.