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

58 lines
1.5 KiB
Markdown

# API Reference: OWASP ZAP DAST Pipeline Integration
## ZAP Docker Scan Scripts
### Baseline Scan (Passive Only)
```bash
docker run --rm -v $(pwd):/zap/wrk zaproxy/zap-stable \
zap-baseline.py -t https://target.com -J report.json -I
```
### Full Scan (Active + Passive)
```bash
docker run --rm -v $(pwd):/zap/wrk zaproxy/zap-stable \
zap-full-scan.py -t https://target.com -J report.json -m 5 -I
```
### API Scan (OpenAPI/Swagger)
```bash
docker run --rm -v $(pwd):/zap/wrk zaproxy/zap-stable \
zap-api-scan.py -t https://target.com/openapi.json -f openapi -J report.json
```
### Return Codes
| Code | Meaning |
|------|---------|
| 0 | No alerts above threshold |
| 1 | Warnings found |
| 2 | Failures found |
### Common Flags
| Flag | Description |
|------|-------------|
| `-t` | Target URL |
| `-J` | JSON report filename |
| `-m` | Max scan duration in minutes |
| `-I` | Do not return failure on warnings |
| `-f` | API spec format (`openapi`, `soap`) |
| `-r` | HTML report filename |
| `-c` | Config file for rule tuning |
## ZAP JSON Report Structure
```json
{"site": [{"alerts": [{"name": "...", "riskdesc": "High (Medium)",
"cweid": "79", "count": 3, "solution": "..."}]}]}
```
### Risk Levels
| Level | Action |
|-------|--------|
| High | Block deployment |
| Medium | Require review |
| Low | Track as tech debt |
| Informational | Log only |
## References
- ZAP Docker: https://www.zaproxy.org/docs/docker/
- ZAP Automation: https://www.zaproxy.org/docs/automate/