mirror of
https://github.com/SHOGGOTH-SECTOR/sica-fondt.git
synced 2026-08-01 00:23:15 +00:00
24f816b6a3
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
3.7 KiB
3.7 KiB
Workflows: Android Static Analysis with MobSF
Workflow 1: Standalone APK Assessment
[Obtain APK] --> [Deploy MobSF Docker] --> [Upload via API] --> [Run Static Scan]
| |
v v
[Verify APK integrity] [Review Manifest Analysis]
[Check signing certificate] [Review Code Analysis]
[Review Binary Analysis]
[Review Network Analysis]
|
v
[Triage HIGH/CRITICAL findings]
[Validate false positives]
[Generate PDF report]
Workflow 2: CI/CD Pipeline Integration
[Developer pushes code] --> [Build APK] --> [Upload to MobSF] --> [Static Scan]
|
+-----------+-----------+
| |
[Score >= 60] [Score < 60]
| |
[Pass gate] [Fail build]
[Archive report] [Notify developer]
[Continue pipeline] [Block deployment]
Workflow 3: Third-Party App Vetting
[Receive third-party APK] --> [MobSF Static Scan] --> [Automated scoring]
|
v
[Manual review of:]
- Excessive permissions
- Data exfiltration indicators
- Known malware signatures
- C2 communication patterns
|
v
[Risk assessment report]
[Approve/Reject for enterprise use]
Workflow 4: Comparative Analysis Across Versions
[APK v1.0] --> [MobSF Scan] --> [Baseline report]
|
[APK v2.0] --> [MobSF Scan] --> [Compare findings] --> [New vulnerabilities introduced?]
| |
v [Yes: Block release]
[Regression report] [No: Approve release]
Decision Matrix: When to Escalate
| Finding Severity | MobSF Category | Action |
|---|---|---|
| CRITICAL | Hardcoded production API keys | Immediate key rotation, block release |
| HIGH | Exported activity with sensitive data | Manual verification, fix before release |
| MEDIUM | Missing certificate pinning | Add to sprint backlog, risk acceptance if internal app |
| LOW | Debug logging of non-sensitive data | Track in issue tracker, fix in next release |
| INFO | Missing ProGuard rules | Recommend but do not block |