C# application loads versioned package
C# key, sign and verify APIs
NET · PROVIDER / SDK PROFILE
Enable C# applications to create, verify and exchange classical, hybrid or project-approved PQC artifacts.
CUSTOMER PROBLEM
.NET applications need a supported SDK and native-provider bridge for hybrid and PQC artifacts without relying on undocumented runtime behavior.
PRODUCT-SPECIFIC IMPLEMENTATION FLOW
.NET applications through approved native/provider bridges and project APIs. NuGet/internal package record, test vectors, application matrix and exception log.
C# key, sign and verify APIs
CMS/CAdES and document examples
Native provider / HSM bridge
ASP.NET and Windows service integration
NuGet/internal package lifecycle
Test vectors and exception handling
NAMED COMPONENTS AND RESPONSIBILITIES
The descriptions below state concrete technical behaviour rather than generic support language.
Exposes typed C# APIs for key references, signing, verification and approved KEM workflows with cancellation, async handling and structured errors.
Includes CMS/CAdES and document samples that show signed attributes, certificate chains, timestamp integration and verification policy.
Connects managed code to CNG, PKCS#11, HSM or remote services through a controlled native/API bridge without exporting private key material.
Provides ASP.NET dependency injection, Windows-service lifecycle and secure configuration patterns for long-running backend deployments.
Versions NuGet or internal packages with signed binaries, dependency lock files, compatibility notes, deprecation and upgrade guidance.
Ships positive and negative test vectors and preserves native/provider error detail in a safe exception model suitable for support diagnostics.
.NET applications through approved native/provider bridges and project APIs.
A pinned provider/SDK build, sample application, test key backend and diagnostics are supplied for repeatable integration.
One named application and runtime are integrated with exact algorithms, key backend, test corpus and rollback.
Signed packages, compatibility matrix, upgrade policy, monitoring and support ownership govern broader rollout.
PRODUCT-SPECIFIC BOUNDARIES
These points come from the product profile, not from a shared disclaimer.
NEXT STEP
Select one application, exact versions, measurable acceptance criteria and rollback.