saint-graves/sica-fondt
1
0
Fork 0
mirror of https://github.com/SHOGGOTH-SECTOR/sica-fondt.git synced 2026-08-01 08:30:20 +00:00
Code Issues Packages Projects Releases Wiki Activity
sica-fondt/knowledge/cyber-skills/skills/implementing-passwordless-authentication-with-fido2/references/workflows.md
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.5 KiB
Raw Blame History

FIDO2 Passwordless Authentication Workflows

Workflow 1: Security Key Enrollment

  1. User receives FIDO2 security key (YubiKey, Titan Key)
  2. User navigates to enrollment portal
  3. System generates WebAuthn registration challenge
  4. Browser prompts user to insert/tap security key
  5. User verifies with PIN or biometric on key
  6. Key generates unique public/private key pair
  7. Public key registered with relying party
  8. User tests authentication with enrolled key

Workflow 2: Passkey Authentication Flow

  1. User visits login page, enters username
  2. Server sends WebAuthn authentication challenge
  3. Browser prompts for authenticator (key, biometric, passkey)
  4. User verifies identity (touch key, scan fingerprint, enter PIN)
  5. Authenticator signs challenge with private key
  6. Server validates signature with stored public key
  7. User authenticated, session created

Workflow 3: Migration from Passwords to Passwordless

  1. Phase 1: Deploy FIDO2 to pilot group (IT, security teams)
  2. Phase 2: Enable coexistence (password + FIDO2)
  3. Phase 3: Expand FIDO2 enrollment to all users
  4. Phase 4: Set FIDO2-only policy per group
  5. Phase 5: Disable password authentication for migrated groups
  6. Phase 6: Monitor for fallback authentication attempts

Workflow 4: Lost/Stolen Key Recovery

  1. User reports lost security key
  2. Admin disables lost key in identity provider
  3. User authenticates via backup method (recovery codes, backup key)
  4. User enrolls replacement security key
  5. Old key permanently revoked
  6. Security team reviews for unauthorized usage of lost key