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.5 KiB
1.5 KiB
SSL Certificate Lifecycle Management Template
Certificate Inventory Template
| Domain | Type | CA | Issued | Expires | Days Left | Status |
|---|---|---|---|---|---|---|
| example.com | DV | Let's Encrypt | 2024-01-01 | 2024-04-01 | 90 | OK |
| api.example.com | DV | DigiCert | 2024-01-01 | 2025-01-01 | 365 | OK |
Monitoring Thresholds
monitoring:
ok_threshold: 30 # days
warning_threshold: 15 # days
critical_threshold: 7 # days
check_interval: 86400 # seconds (daily)
notification:
email: security@example.com
slack: "#cert-alerts"
CSR Generation Command
# ECDSA (recommended)
openssl ecparam -genkey -name prime256v1 -out server.key
openssl req -new -key server.key -out server.csr -subj "/CN=example.com"
# RSA 4096
openssl genrsa -out server.key 4096
openssl req -new -key server.key -out server.csr -subj "/CN=example.com"
Renewal Automation (certbot)
# Initial issuance
certbot certonly --nginx -d example.com -d www.example.com
# Auto-renewal (cron)
0 0 * * * certbot renew --quiet --deploy-hook "systemctl reload nginx"
Revocation Checklist
- Identify affected certificate(s)
- Contact CA to initiate revocation
- Provide revocation reason (key compromise, cessation, etc.)
- Verify revocation in CRL/OCSP
- Issue replacement certificate
- Deploy replacement to all affected servers
- Update certificate inventory
- Document incident