Files
git.stella-ops.org/docs2/ui/findings.md
master dac8e10e36 feat(crypto): Complete Phase 2 - Configuration-driven crypto architecture with 100% compliance
## 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>
2025-12-23 18:20:00 +02:00

3.0 KiB

Findings workspace

Purpose

  • Present materialized policy verdicts with explainability, filtering, and export support.
  • Preserve aggregation-only provenance while enabling triage and automation.

Access and dependencies

  • Route: /console/findings with optional panel=explain.
  • Scopes: findings.read, policy:runs, policy:simulate, downloads.read.
  • Depends on Policy Engine effective findings, Concelier and Excititor provenance, SBOM service metadata.
  • Feature flags: findings.explain.enabled, findings.savedViews.enabled, findings.simulationDiff.enabled.

Layout

  • Header with tenant badge, policy selector, global filters, and actions.
  • Summary cards: affected assets, critical count, KEV count.
  • Findings grid (virtualized) with right-side drawer for details.

Filters and saved views

  • Status: affected, at_risk, quieted, fixed, not_applicable, mitigated.
  • Severity: critical, high, medium, low, informational, untriaged.
  • KEV toggle and exploitability hints.
  • Policy view: active, staged, simulation.
  • Component search by PURL or substring.
  • SBOM filter by image digest or SBOM ID.
  • Tags from policy outputs.
  • Run window and explain hints (rule ID, justification, VEX provider).
  • Saved views persist per tenant and policy; shared views appear in the rail.

Grid columns and badges

  • Status badge with rationale and quieted expiry.
  • Severity with score tooltip.
  • Component PURL and SBOM link.
  • Policy name and revision digest.
  • Source signals (VEX, advisory, runtime overlays).
  • Age since last evaluation.
  • Row badges: KEV, override, simulation only, determinism alert.

Bulk actions

  • Open explains (batch drawer).
  • Export CSV or JSON.
  • Copy CLI batch explain commands.
  • Create ticket using configured integrations.

Explain drawer

  • Summary: status, severity, policy decision, rule ID, run ID, SBOM link.
  • Rule chain: ordered rule hits with actions and score contributions.
  • Evidence: advisory, VEX, runtime signals, overrides.
  • VEX impact: claims used, justification, acceptance.
  • History: state transitions with timestamps and operators.
  • Raw trace: canonical policy trace with CLI parity.

Simulations and comparisons

  • Compare active vs staged or simulation snapshots with diff banners.
  • Side-by-side view highlights added, removed, and severity changes.
  • Simulation results expire after a retention window and prompt re-run.

Exports and automation

  • Immediate CSV, JSON, and Markdown summary exports.
  • Scheduled exports produce full tenant reports with manifests.
  • Explain bundle export packages traces for audit.
  • Webhook subscription hints for export completion.

Real-time updates

  • SSE stream updates new findings, status changes, and quieted expirations.
  • Metrics cards mirror findings_critical_total, findings_quieted_total, findings_kev_total.
  • Errors surface correlation IDs for logs.

Offline behavior

  • Snapshot banner shows offline dataset and staleness.
  • Explain drawer notes cached evidence sources.
  • Exports default to local paths with transfer guidance.
  • Tenants missing in the snapshot are hidden.