- Modified task status update instructions in AGENTS.md files to refer to corresponding sprint files as `/docs/implplan/SPRINT_*.md` instead of `docs/implplan/SPRINTS.md`. - Added a comprehensive document for Secret Leak Detection operations detailing scope, prerequisites, rule bundle lifecycle, enabling the analyzer, policy patterns, observability, troubleshooting, and references.
2.4 KiB
2.4 KiB
Team 8 — Security Guild (Authority & Shared Crypto)
Role
Team 8 owns the end-to-end security posture for StellaOps Authority and its consumers. That includes password hashing policy, audit/event hygiene, rate-limit & lockout rules, revocation distribution, and sovereign cryptography abstractions that allow alternative algorithm suites (e.g., GOST) without touching feature code.
Operational Boundaries
- Primary workspace:
src/__Libraries/StellaOps.Cryptography,src/Authority/StellaOps.Authority/StellaOps.Authority.Plugin.Standard,src/Authority/StellaOps.Authority/StellaOps.Authority.Storage.Mongo, and Authority host (src/Authority/StellaOps.Authority/StellaOps.Authority). - Coordinate cross-module changes via TASKS.md updates and PR descriptions.
- Never bypass deterministic behaviour (sorted keys, stable timestamps).
- Tests live alongside owning projects (
*.Tests). Extend goldens instead of rewriting.
Expectations
- Default to Argon2id (Konscious) for password hashing; PBKDF2 only for legacy verification with transparent rehash on success.
- Emit structured security events with minimal PII and clear correlation IDs.
- Rate-limit
/tokenand bootstrap endpoints once CORE8 hooks are available. - Deliver offline revocation bundles signed with detached JWS and provide a verification script.
- Maintain
docs/security/authority-threat-model.mdand ensure mitigations are tracked. - All crypto consumption flows through
StellaOps.Cryptographyabstractions to enable sovereign crypto providers. - Every new cryptographic algorithm, dependency, or acceleration path ships as an
ICryptoProviderplug-in underStellaOps.Cryptography.*; feature code must never bind directly to third-party crypto libraries.
Required Reading
docs/modules/platform/architecture-overview.md
Working Agreement
-
- Update task status to
DOING/DONEin both correspoding sprint file/docs/implplan/SPRINT_*.mdand the localTASKS.mdwhen you start or finish work.
- Update task status to
-
- Review this charter and the Required Reading documents before coding; confirm prerequisites are met.
-
- Keep changes deterministic (stable ordering, timestamps, hashes) and align with offline/air-gap expectations.
-
- Coordinate doc updates, tests, and cross-guild communication whenever contracts or workflows change.
-
- Revert to
TODOif you pause the task without shipping changes; leave notes in commit/PR descriptions for context.
- Revert to