stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 2 Releases Wiki Activity
Files
dac8e10e361e03690a2e1ffa374f4617ffbd9705
git.stella-ops.org/docs2/ui/advisories-vex.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.5 KiB
Raw Blame History

Advisories and VEX

Purpose

  • Display Concelier advisories and Excititor VEX consensus without mutating upstream data.
  • Highlight provenance, conflicts, and verification status under Aggregation-Only rules.

Access and dependencies

  • Routes: /console/advisories and /console/vex.
  • Scopes: advisory.read, vex.read; advisory.verify and vex.verify for verification actions; downloads.read for exports.
  • Depends on Concelier and Excititor aggregation APIs and Authority tenancy.
  • Feature flags: advisoryExplorer.enabled, vexExplorer.enabled, aggregation.conflictIndicators.

Layout

  • Shared header with tenant badge, global filters, status ticker, and actions.
  • Tabs for Advisories and VEX; last view remembered per tenant.
  • Left rail includes saved views and provider filters.

Advisory grid

  • Columns: vulnerability ID, title, source set, last merged, severity, KEV flag, affected count, merge hash.
  • Source chips list providers with precedence and timestamps.
  • Filters: ID search, provider, severity, KEV, affected count, time window.
  • Actions: open detail, compare sources, queue verify, copy CLI.

Advisory detail drawer

  • Summary cards: title, timestamps, merge hash, total sources, exploited flag.
  • Sources timeline with signature status, precedence, and raw links.
  • Affected products table with semver or distro view toggle.
  • Conflict indicators for severity, fixed versions, affected sets.
  • References list and raw JSON viewer.
  • CLI parity for show, sources, and export commands.

VEX explorer

  • Consensus table keyed by vulnerability and product.
  • Status badges: affected, not_affected, fixed, under_investigation.
  • Provider breakdown shows accepted or ignored claims with weights and justification.
  • Filters: product PURL, status, provider, justification code, confidence threshold.
  • Saved views for common triage scenarios.

VEX detail drawer

  • Consensus summary with policy revision and confidence data.
  • Claims list grouped by provider tier with provenance and supersedes chains.
  • Conflict explainers show why claims were ignored.
  • Timeline events with correlation IDs.
  • Raw JSON viewer with CLI parity.

Provenance and raw viewers

  • Provenance banner shows source URI, document digest, signature status, timestamps, collector version.
  • Raw documents are read-only and include DSSE bundle download when available.
  • Log pivot links copy correlation ID queries.

Conflict indicators and AOC alignment

  • Conflicts are surfaced rather than merged in the UI.
  • Winning values and precedence are shown from Concelier metadata.
  • UI copy reminds users policy decisions happen elsewhere.

Verification workflows

  • Verify actions call Concelier or Excititor endpoints scoped by tenant and filters.
  • Results summarize documents checked, signatures verified, and ERR_AOC codes.
  • Verification history is accessible from the status ticker.

Exports and automation

  • Advisory exports: normalized advisory, affected products CSV, source bundle.
  • VEX exports: consensus snapshot, raw claims, provider deltas.
  • Export manifests include merge hash or consensus digest and signature state.
  • Webhook subscription snippets for export completion.

Real-time updates

  • SSE refreshes advisory and VEX grids with delta badges.
  • Status ticker shows ingest lag and verification queue depth.

Offline behavior

  • Snapshot banner shows staleness and disables live verification.
  • Raw downloads use local snapshot paths with checksum guidance.
  • Exports queue locally with removable media instructions.
  • Tenants missing from the snapshot are hidden.