mirror of
https://github.com/SHOGGOTH-SECTOR/sica-fondt.git
synced 2026-08-01 08:30:20 +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
54 lines
1.7 KiB
Markdown
54 lines
1.7 KiB
Markdown
# Identity Federation with SAML Azure AD - Standards Reference
|
|
|
|
## Federation Protocols
|
|
|
|
### SAML 2.0 (OASIS)
|
|
- Security Assertion Markup Language version 2.0
|
|
- XML-based framework for exchanging authentication/authorization data
|
|
- Profiles: Web Browser SSO, Enhanced Client or Proxy, Single Logout
|
|
- Bindings: HTTP Redirect, HTTP POST, HTTP Artifact, SOAP
|
|
|
|
### WS-Federation (OASIS)
|
|
- Web Services Federation Language
|
|
- Used by AD FS for passive federation (browser-based)
|
|
- Token types: SAML 1.1, SAML 2.0
|
|
|
|
### OpenID Connect
|
|
- Built on OAuth 2.0
|
|
- JSON/REST-based (vs. SAML XML)
|
|
- Used by Azure AD as primary protocol for modern applications
|
|
- JWT tokens instead of SAML assertions
|
|
|
|
## Microsoft Entra ID Federation Requirements
|
|
|
|
### Supported Federation Protocols
|
|
| Protocol | Use Case | Token Format |
|
|
|----------|----------|-------------|
|
|
| SAML 2.0 | Enterprise SSO, third-party apps | SAML assertion (XML) |
|
|
| WS-Federation | Legacy applications, AD FS | SAML token |
|
|
| OpenID Connect | Modern web/mobile apps | JWT |
|
|
|
|
### Domain Federation Requirements
|
|
- Domain must be verified in Azure AD
|
|
- Only one federation configuration per domain
|
|
- Password hash sync recommended as backup
|
|
- Azure AD Connect for hybrid identity sync
|
|
|
|
## Compliance Mapping
|
|
|
|
### NIST SP 800-63C - Federation and Assertions
|
|
- FAL1: Bearer assertion, direct presentation
|
|
- FAL2: Bearer assertion with additional security
|
|
- FAL3: Holder-of-key assertion
|
|
|
|
### FedRAMP
|
|
- IA-2: Identification and Authentication
|
|
- IA-5: Authenticator Management
|
|
- IA-8: Identification and Authentication (Non-Organizational Users)
|
|
- Federation required for cross-organization access
|
|
|
|
### ISO 27001:2022
|
|
- A.5.16: Identity management
|
|
- A.5.17: Authentication information
|
|
- A.8.5: Secure authentication
|