rtexit-method 0.1.0 → 0.1.2

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

@@ -0,0 +1,68 @@
+---
+name: rt-exploit-redis
+description: "Redis security assessment skill for authorized exposure review, authentication, ACLs, TLS, command restrictions, sensitive cache-data handling, availability risk, and remediation."
+---
+
+# rt-exploit-redis - Redis Assessment
+
+## Overview
+
+Redis is often treated as internal-only infrastructure. Risk increases when it is exposed, unauthenticated, overprivileged, used for session data, or configured with unsafe persistence/command access.
+
+## Prerequisites
+
+- In-scope instances and environments.
+- Safe test window.
+- Permission to inspect configuration or use client-provided output.
+- Rules for key inspection and sensitive cache data.
+
+## Assessment Areas
+
+| Area | Checks |
+|---|---|
+| Exposure | Public access, VPC rules, protected mode. |
+| Authentication | AUTH/ACL users, default user state, shared passwords. |
+| TLS | Encrypted transport and client verification. |
+| Commands | Dangerous command availability and role restrictions. |
+| Data | Session tokens, PII, credentials, excessive retention. |
+| Persistence | RDB/AOF storage permissions and backups. |
+| Monitoring | Auth failures, command anomalies, memory pressure. |
+
+## Workflow
+
+1. Confirm safe inspection boundaries.
+2. Inventory exposure, auth, TLS, and Redis version.
+3. Review ACL model and sensitive command access.
+4. Inspect only approved keys or metadata samples.
+5. Evaluate business impact: data exposure, session compromise, outage risk.
+6. Recommend controls.
+
+## Evidence
+
+Use redacted config summaries, ACL summaries, key metadata, and screenshots. Do not dump full keyspaces.
+
+## Remediation
+
+- Private networking only.
+- Enforce ACLs and disable default user where possible.
+- Use TLS.
+- Restrict dangerous commands.
+- Avoid storing long-lived secrets.
+- Secure persistence files and backups.
+- Alert on auth failures and unusual command patterns.
+
+
+## Finding Examples
+
+| Finding | Severity Driver |
+|---|---|
+| Public Redis instance | Internet exposure and availability risk. |
+| Default user with broad access | Privilege and data exposure risk. |
+| Session tokens in cache | Account takeover potential. |
+| No TLS | Credential interception risk. |
+
+## Autodoc
+
+```bash
+python _rtexit/scripts/autodoc_engine.py log --skill rt-exploit-redis --phase exploitation --cmd "Redis posture review" --output "redacted cache risk summary"
+```

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

@@ -0,0 +1,61 @@
+---
+name: rt-exploit-ruby
+description: "Authorized Ruby and Rails security review skill covering Rails configuration, dependency risk, unsafe deserialization patterns, mass assignment, authorization, secrets handling, and remediation."
+---
+
+# rt-exploit-ruby - Ruby and Rails Security Testing
+
+## Overview
+
+Ruby applications often concentrate risk in Rails conventions, background jobs, serializers, dependency versions, admin panels, and authorization boundaries. This skill turns Ruby/Rails-specific review into a repeatable workflow.
+
+## Prerequisites
+
+- Application URL or code access in scope.
+- Framework and Ruby version identified.
+- Test accounts for each role.
+- Permission to review dependency manifests if available.
+- Data access limits confirmed.
+
+## Testing Areas
+
+| Area | What To Review |
+|---|---|
+| Rails Configuration | Environment, debug exposure, host authorization, cookies, CSRF. |
+| Authentication | Devise/custom auth, password reset, session lifetime, MFA. |
+| Authorization | Pundit/CanCanCan policies, controller filters, object ownership. |
+| Mass Assignment | Strong parameters and nested attributes. |
+| Serialization | YAML, Marshal, JSON parsing, signed/encrypted payloads. |
+| File Handling | ActiveStorage configuration, content type, direct upload access. |
+| Background Jobs | Sidekiq/Resque dashboards, job argument sensitivity. |
+| Dependencies | Gem advisories, outdated Rails, vulnerable plugins. |
+
+## Workflow
+
+1. Fingerprint framework, versions, routes, and major gems.
+2. Build role/object authorization matrix.
+3. Review high-risk endpoints: admin, upload, export, import, webhook, search.
+4. Validate mass assignment and authorization with safe role-pair tests.
+5. Review secrets and credentials handling.
+6. Document root cause with controller/action/gem where known.
+
+## Evidence
+
+Use paired requests from different roles, redacted dependency advisory output, screenshots, and code snippets if code review is authorized.
+
+## Remediation
+
+- Enforce strong parameters.
+- Centralize authorization policy checks.
+- Patch Rails and vulnerable gems.
+- Avoid unsafe object deserialization.
+- Protect Sidekiq/admin dashboards.
+- Set secure cookie and CSRF defaults.
+- Rotate exposed secrets.
+
+## References
+
+- Rails Security Guide
+- OWASP ASVS
+- RubySec Advisory Database
+