aigroup-workflow 2.1.1 → 2.2.0

package/skills/security-reviewer/SKILL.md

@@ -1,103 +0,0 @@
----
-name: security-reviewer
-description: Identifies security vulnerabilities, generates structured audit reports with severity ratings, and provides actionable remediation guidance. Use when conducting security audits, reviewing code for vulnerabilities, or analyzing infrastructure security. Invoke for SAST scans, penetration testing, DevSecOps practices, cloud security reviews, dependency audits, secrets scanning, or compliance checks. Produces vulnerability reports, prioritized recommendations, and compliance checklists.
-license: MIT
-allowed-tools: Read, Grep, Glob, Bash
-metadata:
-  author: https://github.com/Jeffallan
-  version: "1.1.1"
-  domain: security
-  triggers: security review, vulnerability scan, SAST, security audit, penetration test, code audit, security analysis, infrastructure security, DevSecOps, cloud security, compliance audit
-  role: specialist
-  scope: review
-  output-format: report
-  related-skills: secure-code-guardian, code-reviewer, devops-engineer, cloud-architect, kubernetes-specialist, api-designer, mcp-developer
----
-
-# Security Reviewer
-
-Security analyst specializing in code review, vulnerability identification, penetration testing, and infrastructure security.
-
-## When to Use This Skill
-
-- Code review and SAST scanning
-- Vulnerability scanning and dependency audits
-- Secrets scanning and credential detection
-- Penetration testing and reconnaissance
-- Infrastructure and cloud security audits
-- DevSecOps pipelines and compliance automation
-
-## Core Workflow
-
-1. **Scope** — Map attack surface and critical paths. Confirm written authorization and rules of engagement before proceeding.
-2. **Scan** — Run SAST, dependency, and secrets tools. Example commands:
-   - `semgrep --config=auto .`
-   - `bandit -r ./src`
-   - `gitleaks detect --source=.`
-   - `npm audit --audit-level=moderate`
-   - `trivy fs .`
-3. **Review** — Manual review of auth, input handling, and crypto. Tools miss context — manual review is mandatory.
-4. **Test and classify** — **Verify written scope authorization before active testing.** Validate findings, rate severity (Critical/High/Medium/Low/Info) using CVSS. Confirm exploitability with proof-of-concept only; do not exceed it.
-5. **Report** — Confirm findings with stakeholder before finalizing. Document with location, impact, and remediation. Report critical findings immediately.
-
-## Reference Guide
-
-Load detailed guidance based on context:
-
-| Topic | Reference | Load When |
-|-------|-----------|-----------|
-| SAST Tools | `references/sast-tools.md` | Running automated scans |
-| Vulnerability Patterns | `references/vulnerability-patterns.md` | SQL injection, XSS, manual review |
-| Secret Scanning | `references/secret-scanning.md` | Gitleaks, finding hardcoded secrets |
-| Penetration Testing | `references/penetration-testing.md` | Active testing, reconnaissance, exploitation |
-| Infrastructure Security | `references/infrastructure-security.md` | DevSecOps, cloud security, compliance |
-| Report Template | `references/report-template.md` | Writing security report |
-
-## Constraints
-
-### MUST DO
-- Check authentication/authorization first
-- Run automated tools before manual review
-- Provide specific file/line locations
-- Include remediation for each finding
-- Rate severity consistently
-- Check for secrets in code
-- Verify scope and authorization before active testing
-- Document all testing activities
-- Follow rules of engagement
-- Report critical findings immediately
-
-### MUST NOT DO
-- Skip manual review (tools miss things)
-- Test on production systems without authorization
-- Ignore "low" severity issues
-- Assume frameworks handle everything
-- Share detailed exploits publicly
-- Exploit beyond proof of concept
-- Cause service disruption or data loss
-- Test outside defined scope
-
-## Output Templates
-
-1. Executive summary with risk assessment
-2. Findings table with severity counts
-3. Detailed findings with location, impact, and remediation
-4. Prioritized recommendations
-
-### Example Finding Entry
-
-```
-ID: FIND-001
-Severity: High (CVSS 8.1)
-Title: SQL Injection in user search endpoint
-File: src/api/users.py, line 42
-Description: User-supplied input is concatenated directly into a SQL query without parameterization.
-Impact: An attacker can read, modify, or delete database contents.
-Remediation: Use parameterized queries or an ORM. Replace `cursor.execute(f"SELECT * FROM users WHERE name='{name}'")`
-             with `cursor.execute("SELECT * FROM users WHERE name=%s", (name,))`.
-References: CWE-89, OWASP A03:2021
-```
-
-## Knowledge Reference
-
-OWASP Top 10, CWE, Semgrep, Bandit, ESLint Security, gosec, npm audit, gitleaks, trufflehog, CVSS scoring, nmap, Burp Suite, sqlmap, Trivy, Checkov, HashiCorp Vault, AWS Security Hub, CIS benchmarks, SOC2, ISO27001

package/skills/security-reviewer/references/infrastructure-security.md

@@ -1,268 +0,0 @@
-# Infrastructure Security
-
-## DevSecOps Integration
-
-### CI/CD Security Pipeline
-
-```yaml
-# GitHub Actions - Security scanning
-name: Security Pipeline
-on: [push, pull_request]
-jobs:
-  security:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: returntocorp/semgrep-action@v1
-      - uses: gitleaks/gitleaks-action@v2
-      - uses: aquasecurity/trivy-action@master
-        with:
-          scan-type: 'fs'
-          severity: 'CRITICAL,HIGH'
-```
-
-### Infrastructure as Code Security
-
-```bash
-# Terraform/CloudFormation scanning
-checkov -d terraform/ --framework terraform
-tfsec terraform/
-terrascan scan -d terraform/
-
-# Kubernetes manifest scanning
-kubesec scan deployment.yaml
-```
-
-## Cloud Security Controls
-
-### AWS Security Hardening
-
-```bash
-# Enable security services
-aws guardduty create-detector --enable
-aws securityhub enable-security-hub
-aws cloudtrail create-trail --name security-trail --s3-bucket-name logs
-
-# Check S3 bucket security
-aws s3api list-buckets --query "Buckets[].Name" | \
-  xargs -I {} aws s3api get-bucket-acl --bucket {}
-
-# IAM password policy
-aws iam update-account-password-policy \
-  --minimum-password-length 14 \
-  --require-symbols --require-numbers \
-  --require-uppercase-characters --require-lowercase-characters
-```
-
-### Azure Security
-
-```bash
-# Enable Security Center
-az security auto-provisioning-setting update --name default --auto-provision on
-
-# Enable disk encryption
-az vm encryption enable --resource-group myRG --name myVM --disk-encryption-keyvault myKV
-```
-
-### GCP Security
-
-```bash
-# Enable Security Command Center
-gcloud services enable securitycenter.googleapis.com
-
-# Enable VPC Flow Logs
-gcloud compute networks subnets update SUBNET --enable-flow-logs
-```
-
-## Container Security
-
-### Secure Dockerfile
-
-```dockerfile
-FROM node:18-alpine
-RUN addgroup -g 1001 -S nodejs && adduser -S nodejs -u 1001
-WORKDIR /app
-COPY --chown=nodejs:nodejs package*.json ./
-RUN npm ci --only=production
-USER nodejs
-EXPOSE 3000
-HEALTHCHECK --interval=30s CMD node healthcheck.js
-CMD ["node", "server.js"]
-```
-
-### Kubernetes Security
-
-```yaml
-# Pod Security Standards
-apiVersion: v1
-kind: Pod
-metadata:
-  name: secure-pod
-spec:
-  securityContext:
-    runAsNonRoot: true
-    runAsUser: 1000
-    fsGroup: 2000
-    seccompProfile:
-      type: RuntimeDefault
-  containers:
-  - name: app
-    image: myapp:1.0
-    securityContext:
-      allowPrivilegeEscalation: false
-      readOnlyRootFilesystem: true
-      capabilities:
-        drop: [ALL]
-    resources:
-      limits:
-        memory: "128Mi"
-        cpu: "500m"
----
-# Network Policy - Default deny
-apiVersion: networking.k8s.io/v1
-kind: NetworkPolicy
-metadata:
-  name: default-deny-all
-spec:
-  podSelector: {}
-  policyTypes:
-  - Ingress
-  - Egress
-```
-
-## Compliance Automation
-
-### CIS Benchmark Scanning
-
-```bash
-# Docker CIS benchmark
-docker run --net host --pid host --cap-add audit_control \
-  -v /var/lib:/var/lib -v /var/run/docker.sock:/var/run/docker.sock \
-  docker/docker-bench-security
-
-# Kubernetes CIS benchmark
-kube-bench run --targets master,node
-
-# Linux system hardening
-lynis audit system --quick
-```
-
-### Compliance as Code (InSpec)
-
-```ruby
-# controls/baseline.rb
-control 'ssh-hardening' do
-  impact 1.0
-  title 'SSH Security Configuration'
-
-  describe sshd_config do
-    its('Protocol') { should eq '2' }
-    its('PermitRootLogin') { should eq 'no' }
-    its('PasswordAuthentication') { should eq 'no' }
-  end
-end
-
-control 'encryption-at-rest' do
-  impact 1.0
-  title 'S3 Encryption Enabled'
-
-  describe aws_s3_bucket('my-bucket') do
-    it { should have_default_encryption_enabled }
-  end
-end
-```
-
-## Secrets Management
-
-### HashiCorp Vault
-
-```bash
-# Initialize and configure
-vault operator init
-vault secrets enable -path=secret kv-v2
-
-# Store secrets
-vault kv put secret/app/config api_key="secret123"
-
-# Dynamic database credentials
-vault secrets enable database
-vault write database/config/postgresql \
-  plugin_name=postgresql-database-plugin \
-  allowed_roles="app" \
-  connection_url="postgresql://{{username}}:{{password}}@localhost:5432/" \
-  username="vault" password="vaultpass"
-
-vault write database/roles/app \
-  db_name=postgresql \
-  creation_statements="CREATE ROLE \"{{name}}\" WITH LOGIN PASSWORD '{{password}}';" \
-  default_ttl="1h" max_ttl="24h"
-```
-
-### Kubernetes Secrets with External Secrets Operator
-
-```yaml
-apiVersion: external-secrets.io/v1beta1
-kind: SecretStore
-metadata:
-  name: vault-backend
-spec:
-  provider:
-    vault:
-      server: "https://vault.example.com"
-      path: "secret"
-      auth:
-        kubernetes:
-          role: "app-role"
----
-apiVersion: external-secrets.io/v1beta1
-kind: ExternalSecret
-metadata:
-  name: app-secrets
-spec:
-  refreshInterval: 1h
-  secretStoreRef:
-    name: vault-backend
-  target:
-    name: app-secrets
-  data:
-  - secretKey: api_key
-    remoteRef:
-      key: secret/app/config
-      property: api_key
-```
-
-## Security Monitoring
-
-### SIEM Log Shipping (Filebeat)
-
-```yaml
-filebeat.inputs:
-- type: log
-  paths:
-    - /var/log/auth.log
-    - /var/log/nginx/*.log
-  fields:
-    environment: production
-
-output.elasticsearch:
-  hosts: ["elasticsearch:9200"]
-  index: "security-logs-%{+yyyy.MM.dd}"
-```
-
-## Quick Reference
-
-| Area | Tool | Purpose |
-|------|------|---------|
-| Cloud Security | Prowler, ScoutSuite | AWS/Azure/GCP audit |
-| Container | Trivy, Clair | Image scanning |
-| IaC | Checkov, tfsec | Terraform/CloudFormation |
-| Secrets | Vault, Sealed Secrets | Secret management |
-| Compliance | InSpec, OpenSCAP | CIS benchmarks |
-| Monitoring | ELK, Splunk | SIEM |
-
-| Framework | Focus | Key Controls |
-|-----------|-------|--------------|
-| SOC 2 | Security controls | Access, encryption, monitoring |
-| ISO 27001 | ISMS | Policy, risk, audit |
-| PCI DSS | Payment security | Network segmentation, encryption |
-| HIPAA | Healthcare | Encryption, access logs |
-| GDPR | Data privacy | Consent, retention, DLP |

package/skills/security-reviewer/references/penetration-testing.md

@@ -1,268 +0,0 @@
-# Penetration Testing
-
-## Reconnaissance
-
-### Passive Information Gathering
-
-```bash
-# DNS enumeration
-dig example.com ANY
-nslookup -type=any example.com
-
-# Subdomain discovery
-subfinder -d example.com
-amass enum -d example.com
-
-# Certificate transparency
-curl -s "https://crt.sh/?q=%.example.com&output=json"
-```
-
-### Active Scanning
-
-```bash
-# Port scanning
-nmap -sV -p- target.com
-nmap -sC -sV -oA scan target.com
-
-# Web technology detection
-whatweb target.com
-```
-
-## Web Application Testing
-
-### Authentication & Authorization
-
-```bash
-# Session analysis - Check for:
-# - Session timeout, Secure/HttpOnly flags
-# - Session fixation, concurrent sessions
-
-# IDOR testing
-GET /api/users/123  # Your ID
-GET /api/users/124  # Another user - should fail
-
-# Privilege escalation
-GET /api/admin/users  # As standard user
-```
-
-### Input Validation
-
-```bash
-# SQL injection
-sqlmap -u "http://target.com/search?q=test" --batch
-
-# XSS payloads
-<script>alert(document.domain)</script>
-<img src=x onerror=alert(1)>
-<svg onload=alert(1)>
-
-# Command injection
-; ls -la
-| whoami
-$(whoami)
-
-# XXE
-<?xml version="1.0"?>
-<!DOCTYPE foo [<!ENTITY xxe SYSTEM "file:///etc/passwd">]>
-<root>&xxe;</root>
-```
-
-## API Security Testing
-
-### JWT & Token Security
-
-```bash
-# Decode JWT
-echo "eyJ..." | base64 -d
-
-# Test none algorithm
-# Modify header: {"alg": "none"}
-
-# Weak secret brute force
-hashcat -m 16500 jwt.txt wordlist.txt
-```
-
-### Rate Limiting & Data Exposure
-
-```bash
-# Test rate limits
-for i in {1..1000}; do
-  curl https://api.target.com/login -d "user=test&pass=test"
-done
-
-# Check for excessive data exposure
-GET /api/users/me
-# Look for: password hashes, internal IDs, sensitive PII
-
-# Mass assignment
-POST /api/users/profile
-{"email": "new@email.com", "isAdmin": true}
-```
-
-## Network Penetration
-
-### Privilege Escalation (Linux)
-
-```bash
-# SUID binaries
-find / -perm -4000 -type f 2>/dev/null
-
-# Sudo permissions
-sudo -l
-
-# Writable paths in PATH
-echo $PATH | tr ':' '\n' | xargs -I {} ls -ld {}
-
-# Kernel exploits
-uname -a
-searchsploit linux kernel $(uname -r)
-```
-
-### Lateral Movement
-
-```bash
-# Network enumeration
-arp -a
-netstat -ant
-
-# Service discovery
-nmap -sV 192.168.1.0/24
-
-# Credential harvesting
-grep -r "password" /home/*/
-cat ~/.bash_history | grep -i "pass\|pwd\|secret"
-```
-
-## Mobile Application Testing
-
-### Android
-
-```bash
-# Decompile APK
-apktool d app.apk
-jadx -d output app.apk
-
-# Check for secrets
-grep -r "api_key\|secret\|password" .
-
-# Insecure storage
-adb shell
-run-as com.app.package
-find . -type f -exec cat {} \;
-```
-
-### iOS
-
-```bash
-# Class dump
-class-dump App.app
-
-# Check data storage
-sqlite3 /var/mobile/Applications/.../Library/Caches/data.db
-```
-
-## Cloud Security Testing
-
-### AWS
-
-```bash
-# S3 bucket enumeration
-aws s3 ls s3://bucket-name --no-sign-request
-aws s3api get-bucket-acl --bucket bucket-name
-
-# IAM enumeration
-aws iam get-user
-aws iam list-attached-user-policies --user-name username
-```
-
-### Container & Kubernetes
-
-```bash
-# Docker escape testing
-docker inspect container_id | grep -i privileged
-docker inspect container_id | grep -A 5 Mounts
-
-# Kubernetes
-kubectl get pods --all-namespaces
-kubectl get secrets --all-namespaces
-kubectl auth can-i --list
-```
-
-## Exploitation Validation
-
-### Proof of Concept Guidelines
-
-```python
-# Always demonstrate impact SAFELY
-
-# SQL injection PoC
-# DON'T: Extract actual data
-# DO: Prove injection with sleep
-payload = "' OR SLEEP(5)--"
-
-# DON'T: Delete/modify production data
-# DO: Show you COULD with SELECT
-payload = "' UNION SELECT 'proof_of_concept'--"
-```
-
-### Rules of Engagement
-
-1. **Scope verification** - Only test authorized targets
-2. **Time windows** - Respect testing hours
-3. **DoS prevention** - Avoid resource exhaustion
-4. **Data handling** - Don't exfiltrate real data
-5. **Stop on discovery** - Don't exploit beyond proof
-6. **Immediate reporting** - Report critical findings ASAP
-7. **Documentation** - Record all actions
-8. **Cleanup** - Remove test artifacts
-
-## Vulnerability Classification
-
-### Severity Scoring
-
-| Severity | Exploitability | Impact | CVSS Range |
-|----------|---------------|---------|------------|
-| Critical | Easy | Full compromise | 9.0-10.0 |
-| High | Medium | Significant access | 7.0-8.9 |
-| Medium | Hard | Limited access | 4.0-6.9 |
-| Low | Very hard | Minimal impact | 0.1-3.9 |
-
-### Impact Assessment
-
-- **Critical**: Remote code execution, full data access, admin takeover
-- **High**: Authentication bypass, privilege escalation, sensitive data exposure
-- **Medium**: CSRF, XSS (non-admin), information disclosure
-- **Low**: Missing security headers, verbose errors, rate limiting issues
-
-## Testing Checklist
-
-### OWASP Top 10 Coverage
-
-- [ ] Broken Access Control (IDOR, path traversal)
-- [ ] Cryptographic Failures (weak encryption, plaintext)
-- [ ] Injection (SQL, XSS, command)
-- [ ] Insecure Design (missing auth flows)
-- [ ] Security Misconfiguration (defaults, debug mode)
-- [ ] Vulnerable Components (outdated dependencies)
-- [ ] Authentication Failures (weak passwords, session issues)
-- [ ] Data Integrity (deserialization, lack of verification)
-- [ ] Logging Failures (missing logs, exposed sensitive data)
-- [ ] SSRF (unvalidated URLs)
-
-## Quick Reference
-
-| Test Type | Tools | Focus |
-|-----------|-------|-------|
-| Web App | Burp Suite, OWASP ZAP | OWASP Top 10 |
-| API | Postman, curl | AuthN/AuthZ, data exposure |
-| Network | nmap, Metasploit | Services, exploits |
-| Mobile | MobSF, Frida | Data storage, crypto |
-| Cloud | ScoutSuite, Prowler | Misconfigurations |
-
-| Finding Type | Validation Method | Evidence Required |
-|--------------|------------------|-------------------|
-| SQL Injection | Sleep-based, error-based | Request/response, timing |
-| XSS | Alert box, DOM manipulation | Screenshot, payload |
-| IDOR | Access other user's resource | Two user accounts, IDs |
-| Auth Bypass | Unauthorized access | Before/after screenshots |
-| RCE | Command output (safe) | Whoami, id command output |