mirror of
https://github.com/SHOGGOTH-SECTOR/sica-fondt.git
synced 2026-08-01 08:30:20 +00:00
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
1.4 KiB
1.4 KiB
Workflows - Cryptographic Audit
Workflow 1: Automated Source Code Scan
[Target Application Source]
|
[Scan for Crypto Patterns]:
- Deprecated algorithms (MD5, SHA-1, DES, RC4)
- Insecure modes (ECB)
- Hardcoded secrets (keys, passwords, tokens)
- Weak KDF parameters
- Insecure random number generation
|
[Scan Configuration Files]:
- TLS/SSL settings
- Cipher suite configurations
- Certificate paths and validity
|
[Generate Findings with Severity]
|
[Produce Audit Report]
Workflow 2: Manual Crypto Review
[Identify All Crypto Touchpoints]:
- Encryption/decryption operations
- Hashing operations
- Key generation and storage
- TLS/SSL connections
- Token generation (JWT, API keys)
- Password handling
|
[For Each Touchpoint]:
[Verify algorithm choice]
[Verify mode/padding]
[Verify key management]
[Verify entropy sources]
[Verify error handling]
|
[Document Findings]
Workflow 3: Remediation Prioritization
[All Findings]
|
[Classify by Severity]:
CRITICAL: Hardcoded keys, broken encryption
HIGH: Weak algorithms, ECB mode, weak KDF
MEDIUM: Short key sizes, deprecated protocols
LOW: Missing best practices, informational
|
[Prioritize by Risk]:
1. CRITICAL findings (immediate fix)
2. HIGH findings (fix in current sprint)
3. MEDIUM findings (plan for next release)
4. LOW findings (backlog)