rtexit-method 0.1.0 → 0.1.1

package/packaged-assets/.agents/skills/rt-exploit-web/owasp-checklist.csv

@@ -0,0 +1,14 @@
+category,area,status,notes
+WSTG-INFO,Information Gathering,TODO,
+WSTG-CONF,Configuration and Deployment,TODO,
+WSTG-IDNT,Identity Management,TODO,
+WSTG-ATHN,Authentication,TODO,
+WSTG-ATHZ,Authorization,TODO,
+WSTG-SESS,Session Management,TODO,
+WSTG-INPV,Input Validation,TODO,
+WSTG-ERRH,Error Handling,TODO,
+WSTG-CRYP,Cryptography,TODO,
+WSTG-BUSL,Business Logic,TODO,
+WSTG-CLNT,Client-side Testing,TODO,
+WSTG-APIT,API Testing,TODO,
+

package/packaged-assets/.agents/skills/rt-exploit-web/workflow.md

@@ -0,0 +1,68 @@
+# Workflow - rt-exploit-web
+
+## Purpose
+
+This workflow standardizes how $skill is executed inside RTExit. It is designed for authorized engagements, evidence-first documentation, and consistent handoff into reporting.
+
+## Authorization Gate
+
+Before execution, confirm:
+
+- SEAD exists and explicitly covers the target asset or activity.
+- Rules of Engagement define allowed techniques, rate limits, and stop conditions.
+- The operator knows the evidence handling rules.
+- Any active or sensitive validation has client approval.
+
+If any item is unclear, pause and invoke 
+
+## Required Inputs
+
+| Input | Source | Notes |
+|---|---|---|
+| Engagement reference | _rtexit/config.toml or SEAD | Used in output names. |
+| Target asset(s) | Scope document | Must be explicitly approved. |
+| Operator name | Config/user context | Used in timeline entries. |
+| Evidence directory | _rtexit-output/docs/evidence/ | Store logs, screenshots, and artifacts. |
+| Finding tracker | _rtexit-output/docs/findings/ | Create/update findings when confirmed. |
+
+## Execution Steps
+
+1. Load current engagement configuration.
+2. Read scope, exclusions, and current findings.
+3. Build a small test plan for this skill with target, expected control, and evidence type.
+4. Run the lowest-risk validation first.
+5. Capture baseline behavior before proof behavior.
+6. Record exact timestamp, account/role used, and affected asset.
+7. Stop when evidence is sufficient; avoid unnecessary data access.
+8. Create or update findings through the RTExit finding tracker.
+9. Map remediation owner and recommended timeline.
+10. Add a timeline entry and evidence chain entry.
+
+## Evidence Requirements
+
+| Evidence | Required? | Notes |
+|---|---|---|
+| Command or action summary | Yes | Redact secrets and tokens. |
+| Screenshot or transcript | If useful | Store under evidence folder. |
+| Request/response pair | For web/API | Redact cookies and bearer tokens. |
+| Config excerpt | For cloud/infra | Include only relevant lines. |
+| Business impact note | Yes | Explain why it matters. |
+
+## Autodoc Commands
+
+`ash
+python _rtexit/scripts/autodoc_engine.py log --skill rt-exploit-web --phase auto --cmd "workflow execution" --output "summary"
+python _rtexit/scripts/finding_tracker.py list
+`
+
+## Completion Criteria
+
+- Scope and authorization are referenced.
+- Evidence is stored and redacted.
+- Findings are added or explicitly marked as not found.
+- Remediation guidance is actionable.
+- Timeline and chain of custody are updated where applicable.
+
+## Handoff
+
+Send confirmed findings to 

package/packaged-assets/.agents/skills/rt-exploit-wireless/SKILL.md

@@ -0,0 +1,71 @@
+---
+name: rt-exploit-wireless
+description: "Wireless security assessment skill for authorized WiFi, Bluetooth, and RFID posture review with facility scope controls, non-interference rules, evidence handling, and remediation."
+---
+
+# rt-exploit-wireless - Wireless Security Assessment
+
+## Overview
+
+Wireless testing evaluates radio-facing access controls, guest isolation, enterprise authentication, rogue device monitoring, and facility exposure. Because wireless tests can affect nearby third parties, authorization must be precise.
+
+## Prerequisites
+
+- Approved physical locations.
+- Approved SSIDs, devices, bands, and test times.
+- Non-interference requirements.
+- Client notification to SOC/facilities.
+- Rules for capture files and device identifiers.
+
+## Assessment Areas
+
+| Area | Checks |
+|---|---|
+| WiFi | WPA mode, 802.1X, guest isolation, weak PSK process. |
+| Enterprise Auth | Certificate validation, EAP method, onboarding. |
+| Rogue Networks | Detection and response process. |
+| Bluetooth | Discoverability, pairing policy, sensitive devices. |
+| RFID/NFC | Badge technology review if explicitly approved. |
+| Monitoring | WIDS/WIPS coverage, alert response, asset inventory. |
+
+## Workflow
+
+1. Confirm location and test boundaries.
+2. Inventory authorized wireless networks and visible security settings.
+3. Review guest-to-internal segmentation.
+4. Review enterprise authentication configuration.
+5. Validate rogue detection with approved benign identifiers.
+6. Document risk without capturing unrelated third-party traffic.
+
+## Evidence
+
+Store redacted SSID/BSSID lists, screenshots of client-approved tests, segmentation results, and policy observations. Protect capture files as sensitive evidence.
+
+## Remediation
+
+- Use WPA3 Enterprise or strong WPA2 Enterprise.
+- Validate server certificates in supplicants.
+- Isolate guest networks.
+- Rotate and protect PSKs.
+- Monitor rogue access points.
+- Maintain wireless asset inventory.
+
+
+## Evidence Handling
+
+Wireless evidence may include identifiers for nearby third parties. Redact unrelated SSIDs/BSSIDs, protect capture files, and store only what is needed to prove the client-owned control gap.
+
+## Finding Examples
+
+| Finding | Severity Driver |
+|---|---|
+| Guest network reaches internal services | Segmentation failure. |
+| Weak enterprise certificate validation | Credential interception risk. |
+| Shared PSK reused broadly | Unauthorized access risk. |
+| Rogue AP not detected | Monitoring/control gap. |
+
+## Autodoc
+
+```bash
+python _rtexit/scripts/autodoc_engine.py log --skill rt-exploit-wireless --phase exploitation --cmd "wireless posture review" --output "redacted wireless risk summary"
+```