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>
2.3 KiB
2.3 KiB
AOC dashboard
Purpose
- Monitor Aggregation-Only Contract (AOC) ingestion guardrails across Concelier and Excititor sources.
- Surface violations, verification results, and exportable evidence without mutating source data.
Access and dependencies
- Route: /console/sources.
- Feature flag: aocDashboard.enabled.
- Scopes: ui.read plus advisory.read and vex.read; aoc:verify for verify actions.
- Depends on Concelier and Excititor guard endpoints and Authority tenant scoping.
Layout
- Source tiles for Concelier and Excititor feeds.
- Violations and history table with filters.
- Action bar: run verify, schedule verify, export evidence, open raw docs.
Source tile fields
- Status badge: healthy, warning, critical based on last ingest age and ERR_AOC violations.
- Last ingest timestamp and relative age.
- Violations in the last 24 hours grouped by ERR_AOC code.
- Supersedes depth (average revision chain length).
- Signature pass rate.
- Ingestion latency P95.
Violation drilldown
- Filters by source, timeframe, ERR_AOC code, and severity.
- Detail drawer shows provenance, signature status, supersedes chain, and redacted raw JSON.
- Linked findings and policy overlays are shown as references only.
- Annotations and acknowledgements are stored as structured audit notes.
Verification and actions
- Run verify posts to /aoc/verify with a since window; results include counts and top codes.
- Schedule verify supports daily or weekly cadence with optional notifications.
- Export evidence bundles include tile metrics, verification summaries, and annotations.
- CLI parity: stella aoc verify --tenant --since .
Observability
- ingestion_write_total{source,tenant,result}
- aoc_violation_total{source,tenant,code}
- ingestion_signature_verified_total{source,result}
- ingestion_latency_seconds{source,quantile}
- advisory_revision_count{source}
Security and tenancy
- DPoP-bound tokens per tenant; data never crosses tenant boundaries.
- Sensitive fields are redacted using Concelier rules.
- Verify actions are rate limited and audited (action=aoc.verify.ui).
Offline behavior
- Offline snapshot banner shows snapshot time and bundle hash.
- Verification requests queue for later execution and provide CLI guidance.
- Evidence exports default to local paths for air-gap transfer.