saint-graves/sica-fondt
1
0
Fork 0
mirror of https://github.com/SHOGGOTH-SECTOR/sica-fondt.git synced 2026-08-01 08:30:20 +00:00
Code Issues Packages Projects Releases Wiki Activity
sica-fondt/knowledge/cyber-skills/skills/performing-web-application-vulnerability-triage/references/workflows.md
Claude 24f816b6a3
Consolidate 22 sibling repos into layered organism structure 
Place useful parts of the surrounding repos into sica-fondt by layer, per the
body model (Ada = membrane; brain/endocrine/capabilities/knowledge non-Ada):

- brain/        LLM reasoning + providers (dapr, hermes, MoMoA)
- capabilities/ REPRAG sidecars: hermes tools/skills, dapr tools, parallel
                dispatch, A51 channels, and the OSINT cluster
- knowledge/    LORAG corpus: 754 cyber-skills, agency personas, secure-coding,
                MITRE ATT&CK data
- reference/    defensive threat-reference (C3, shhbruh doc) + AdaYaml parser

License handling: AGPL sources (worldosint, advanced_evolution, mercury,
Reticulum) and GPL DeTTECT are SPEC-only clean-room/port descriptions — no
copyleft code copied. MIT/Apache/data parts copied as working trees.

Safety: shhbruh escape/persistence material and C3 covert-C2 kept as reference
only, not wired into the running organism. See CONSOLIDATION.md.

https://claude.ai/code/session_01UehUqEXXJJCsHoA4voCU5c
2026-06-10 06:53:01 +00:00

1.3 KiB
Raw Blame History

Workflows - Web Application Vulnerability Triage

Workflow 1: DAST Finding Triage

  1. Import DAST scan results (ZAP XML/JSON, Burp XML)
  2. Auto-classify findings by OWASP Top 10 category via CWE mapping
  3. Filter out known false positive patterns (missing headers on non-sensitive pages, etc.)
  4. Flag confirmed exploitation findings as true positives
  5. Queue remaining findings for manual validation
  6. Security analyst validates with manual testing in Burp/ZAP
  7. Assign OWASP risk rating to validated findings
  8. Push validated findings to DefectDojo/Jira

Workflow 2: SAST Finding Triage

  1. Import SAST scan results (Semgrep JSON, SonarQube)
  2. Filter out findings in test files, example code, and dead code
  3. Cross-reference against data flow analysis for injection findings
  4. Review code context to validate exploitability
  5. Assign severity based on data sensitivity and exposure
  6. Create development tickets for validated findings

Workflow 3: Combined Triage and Deduplication

  1. Import both DAST and SAST findings for same application
  2. Correlate SAST code findings with DAST runtime findings
  3. Findings confirmed by both DAST and SAST get elevated priority
  4. Deduplicate findings pointing to same root cause
  5. Generate unified triage report with remediation priority