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

1.4 KiB

Google Workspace SSO - Standards Reference

SAML 2.0 Standard

OASIS SAML 2.0 Core

  • Assertions: Authentication statements, attribute statements
  • Protocols: AuthnRequest, Response, LogoutRequest
  • Bindings: HTTP Redirect, HTTP POST, Artifact
  • Profiles: Web Browser SSO, Single Logout

Google Workspace SAML Requirements

  • SAML 2.0 compliant IdP
  • HTTP POST binding for Assertion Consumer Service
  • Signed SAML assertions (RSA-SHA256 recommended)
  • NameID format: emailAddress (user's primary email)
  • X.509 PEM certificate for signature verification

Google Workspace SSO Parameters

Parameter Value
ACS URL https://www.google.com/a/{domain}/acs
Entity ID (domain-specific) google.com/a/{domain}
Entity ID (generic) google.com
NameID Format urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress
SAML Version 2.0
Binding HTTP-POST

Compliance Mapping

NIST SP 800-63-3 (Digital Identity Guidelines)

  • AAL2: Multi-factor authentication (enforced at IdP)
  • Federation assurance levels (FAL1-FAL3)
  • Assertion protection requirements

SOC 2 - CC6.1

  • Single sign-on centralizes access control
  • Audit trail of authentication events
  • Timely deprovisioning via IdP user removal

ISO 27001:2022 - A.8.5

  • Secure authentication through centralized IdP
  • MFA enforcement via SSO configuration
  • Session management controls