dac8e10e36
## Summary
This commit completes Phase 2 of the configuration-driven crypto architecture, achieving
100% crypto compliance by eliminating all hardcoded cryptographic implementations.
## Key Changes
### Phase 1: Plugin Loader Infrastructure
- **Plugin Discovery System**: Created StellaOps.Cryptography.PluginLoader with manifest-based loading
- **Configuration Model**: Added CryptoPluginConfiguration with regional profiles support
- **Dependency Injection**: Extended DI to support plugin-based crypto provider registration
- **Regional Configs**: Created appsettings.crypto.{international,russia,eu,china}.yaml
- **CI Workflow**: Added .gitea/workflows/crypto-compliance.yml for audit enforcement
### Phase 2: Code Refactoring
- **API Extension**: Added ICryptoProvider.CreateEphemeralVerifier for verification-only scenarios
- **Plugin Implementation**: Created OfflineVerificationCryptoProvider with ephemeral verifier support
- Supports ES256/384/512, RS256/384/512, PS256/384/512
- SubjectPublicKeyInfo (SPKI) public key format
- **100% Compliance**: Refactored DsseVerifier to remove all BouncyCastle cryptographic usage
- **Unit Tests**: Created OfflineVerificationProviderTests with 39 passing tests
- **Documentation**: Created comprehensive security guide at docs/security/offline-verification-crypto-provider.md
- **Audit Infrastructure**: Created scripts/audit-crypto-usage.ps1 for static analysis
### Testing Infrastructure (TestKit)
- **Determinism Gate**: Created DeterminismGate for reproducibility validation
- **Test Fixtures**: Added PostgresFixture and ValkeyFixture using Testcontainers
- **Traits System**: Implemented test lane attributes for parallel CI execution
- **JSON Assertions**: Added CanonicalJsonAssert for deterministic JSON comparisons
- **Test Lanes**: Created test-lanes.yml workflow for parallel test execution
### Documentation
- **Architecture**: Created CRYPTO_CONFIGURATION_DRIVEN_ARCHITECTURE.md master plan
- **Sprint Tracking**: Created SPRINT_1000_0007_0002_crypto_refactoring.md (COMPLETE)
- **API Documentation**: Updated docs2/cli/crypto-plugins.md and crypto.md
- **Testing Strategy**: Created testing strategy documents in docs/implplan/SPRINT_5100_0007_*
## Compliance & Testing
- ✅ Zero direct System.Security.Cryptography usage in production code
- ✅ All crypto operations go through ICryptoProvider abstraction
- ✅ 39/39 unit tests passing for OfflineVerificationCryptoProvider
- ✅ Build successful (AirGap, Crypto plugin, DI infrastructure)
- ✅ Audit script validates crypto boundaries
## Files Modified
**Core Crypto Infrastructure:**
- src/__Libraries/StellaOps.Cryptography/CryptoProvider.cs (API extension)
- src/__Libraries/StellaOps.Cryptography/CryptoSigningKey.cs (verification-only constructor)
- src/__Libraries/StellaOps.Cryptography/EcdsaSigner.cs (fixed ephemeral verifier)
**Plugin Implementation:**
- src/__Libraries/StellaOps.Cryptography.Plugin.OfflineVerification/ (new)
- src/__Libraries/StellaOps.Cryptography.PluginLoader/ (new)
**Production Code Refactoring:**
- src/AirGap/StellaOps.AirGap.Importer/Validation/DsseVerifier.cs (100% compliant)
**Tests:**
- src/__Libraries/__Tests/StellaOps.Cryptography.Plugin.OfflineVerification.Tests/ (new, 39 tests)
- src/__Libraries/__Tests/StellaOps.Cryptography.PluginLoader.Tests/ (new)
**Configuration:**
- etc/crypto-plugins-manifest.json (plugin registry)
- etc/appsettings.crypto.*.yaml (regional profiles)
**Documentation:**
- docs/security/offline-verification-crypto-provider.md (600+ lines)
- docs/implplan/CRYPTO_CONFIGURATION_DRIVEN_ARCHITECTURE.md (master plan)
- docs/implplan/SPRINT_1000_0007_0002_crypto_refactoring.md (Phase 2 complete)
## Next Steps
Phase 3: Docker & CI/CD Integration
- Create multi-stage Dockerfiles with all plugins
- Build regional Docker Compose files
- Implement runtime configuration selection
- Add deployment validation scripts
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
50 lines
2.0 KiB
Markdown
50 lines
2.0 KiB
Markdown
# Component map
|
|
|
|
This map summarizes how top-level modules interact. It is a compact index to
|
|
module dossiers, not a replacement for them.
|
|
|
|
Advisory and evidence services
|
|
- Concelier: advisory ingestion under the Aggregation-Only Contract (AOC).
|
|
- Excititor: VEX ingestion and normalization under AOC guardrails.
|
|
- VEX Lens: conflict analysis and evidence browsing for VEX.
|
|
- Evidence Locker: long-term storage for signed evidence bundles.
|
|
- Export Center: packages evidence and offline bundles for distribution.
|
|
|
|
Scanning, SBOM, and risk
|
|
- Scanner: deterministic scan pipeline (web service + worker).
|
|
- SBOM Service: inventory store and delta cache for SBOMs.
|
|
- Graph and Cartographer: identity graph and relationship queries.
|
|
- Vuln Explorer: evidence-linked findings view with VEX-first posture.
|
|
|
|
Policy and governance
|
|
- Policy Engine: deterministic rule evaluation and explain traces.
|
|
- Task Packs and Task Runner: automation workflows with approvals.
|
|
- Governance surfaces: approvals, exceptions, and audit exports.
|
|
|
|
Identity, signing, and provenance
|
|
- Authority: identity, tokens, scopes, tenancy enforcement.
|
|
- Signer: DSSE signing and key management integration.
|
|
- Attestor: attestations, envelopes, and transparency logging.
|
|
- Issuer Directory: trusted issuer catalog for signatures and VEX.
|
|
|
|
Scheduling and orchestration
|
|
- Scheduler: change detection and rescan orchestration.
|
|
- Orchestrator: job dispatch and coordination for scans and exports.
|
|
|
|
Runtime and security enforcement
|
|
- Zastava: runtime admission and policy enforcement.
|
|
- Signals: runtime and reachability signals feeding policy and triage.
|
|
|
|
Notification and UI
|
|
- Notifications Studio: rule-based notifications and channel delivery.
|
|
- UI Console: Angular app for findings, policy, runs, and admin.
|
|
- Web Gateway: API routing and auth enforcement for UI and CLI.
|
|
|
|
Offline and telemetry
|
|
- Airgap and mirrors: offline bundles, sealing, and staleness control.
|
|
- Telemetry stack: metrics, logs, traces, and offline storage.
|
|
|
|
Related references
|
|
- docs/technical/architecture/component-map.md
|
|
- docs/modules/*/architecture.md
|