## 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>
2.6 KiB
2.6 KiB
Console overview
Mission and principles
- Single entry point for SBOMs, advisories, policies, runs, and admin controls.
- Deterministic navigation with deep-linkable URLs.
- Tenant isolation by default; explicit cross-tenant comparisons only.
- Aggregation-only views for Concelier and Excititor outputs.
- Offline parity for every view with visible staleness.
Primary navigation
- Dashboard: KPIs, feed age, queue depth, alerts.
- Findings: policy verdicts, explain traces, and triage actions.
- SBOM Explorer: catalog, components, overlays, exports.
- Advisories and VEX: aggregated sources, provenance, conflicts.
- Runs: scheduler runs, progress, evidence links.
- Policies: editor, simulations, approvals.
- Downloads: signed artifacts and offline kit parity.
- Admin: tenants, roles, clients, tokens, branding.
- Help: guides, tours, and release notes.
Shared surfaces
- Top bar: tenant picker, environment badge, offline status, user menu, notifications, command palette.
- Global filter tray (Shift+F): tenant, time window, severity, tags, source providers, run status, policy view.
- Context chips: active filters with one-click removal.
- Status ticker: SSE-driven ingestion deltas and queue depth.
Tenant model
- Tenant list comes from Authority; switching issues a tenant-scoped, DPoP-bound token.
- Cross-tenant comparisons are opt-in and render split panes with separate tokens.
- Fresh-auth gates sensitive actions (admin changes, approvals).
- Tenant switches emit audited events (ui.tenant.switch).
Filters, presets, and deep links
- Filters encoded in URLs (tenant, since/until, severity, view, panel, component).
- Presets are saved per tenant and accessible via the command palette and Cmd/Ctrl+1..9.
- Deep links map to CLI commands for deterministic offline replay.
Aggregation-only alignment
- Advisory and VEX pages read canonical aggregation endpoints.
- Provenance badges show source lineage, precedence, and merge hashes.
- UI does not reweight or rewrite aggregated data; actions route through guard endpoints.
Performance and telemetry
- LCP target under 2.5 seconds on a 4 vCPU offline runner with cached assets.
- Route budget under 1.5 seconds after token resolution.
- Telemetry signals: ui_route_render_seconds, ui_filter_apply_total, ui_tenant_switch_total, ui_offline_banner_seconds.
Offline posture
- Offline kits drive read-only views with snapshot ID and staleness banners.
- Actions requiring Authority or verification show CLI guidance.
- Tenants missing from the snapshot are hidden.
Related references
- ui/navigation.md
- ui/downloads.md
- ui/sbom-explorer.md