NET · PROVIDER / SDK PROFILE

Trusted PQC .NET SDK
Controlled pilot

Enable C# applications to create, verify and exchange classical, hybrid or project-approved PQC artifacts.

CUSTOMER PROBLEM

Enable C# applications to create, verify and exchange classical, hybrid or project-approved PQC artifacts.

.NET applications need a supported SDK and native-provider bridge for hybrid and PQC artifacts without relying on undocumented runtime behavior.

Controlled pilot
Portfolio class
Provider / SDK profile
Public profile
2026.07
Version rule
Confirmed in quotation / release record

PRODUCT-SPECIFIC IMPLEMENTATION FLOW

How Trusted PQC .NET SDK operates from input to evidence.

.NET applications through approved native/provider bridges and project APIs. NuGet/internal package record, test vectors, application matrix and exception log.

01

C# application loads versioned package

C# key, sign and verify APIs

02

SDK validates profile and request

CMS/CAdES and document examples

03

Native bridge or API resolves protected key

Native provider / HSM bridge

04

Operation creates CMS or raw result

ASP.NET and Windows service integration

05

Application verifies and maps errors

NuGet/internal package lifecycle

06

Telemetry records package and backend versions

Test vectors and exception handling

NAMED COMPONENTS AND RESPONSIBILITIES

What Trusted PQC .NET SDK contains and what each component does.

The descriptions below state concrete technical behaviour rather than generic support language.

01

C# key, sign and verify APIs

Exposes typed C# APIs for key references, signing, verification and approved KEM workflows with cancellation, async handling and structured errors.

02

CMS/CAdES and document examples

Includes CMS/CAdES and document samples that show signed attributes, certificate chains, timestamp integration and verification policy.

03

Native provider / HSM bridge

Connects managed code to CNG, PKCS#11, HSM or remote services through a controlled native/API bridge without exporting private key material.

04

ASP.NET and Windows service integration

Provides ASP.NET dependency injection, Windows-service lifecycle and secure configuration patterns for long-running backend deployments.

05

NuGet/internal package lifecycle

Versions NuGet or internal packages with signed binaries, dependency lock files, compatibility notes, deprecation and upgrade guidance.

06

Test vectors and exception handling

Ships positive and negative test vectors and preserves native/provider error detail in a safe exception model suitable for support diagnostics.

CUSTOMER OUTCOMES
  • C# integration package
  • CMS/CAdES examples
  • Backend and desktop pilots
INTEGRATION BOUNDARY

.NET applications through approved native/provider bridges and project APIs.

DEPLOYMENT PATTERNS

Developer sandbox

A pinned provider/SDK build, sample application, test key backend and diagnostics are supplied for repeatable integration.

Application pilot

One named application and runtime are integrated with exact algorithms, key backend, test corpus and rollback.

Enterprise release channel

Signed packages, compatibility matrix, upgrade policy, monitoring and support ownership govern broader rollout.

EVIDENCE REQUIRED
  • NuGet/internal package record, test vectors, application matrix and exception log.
  • Version and configuration manifest for: .NET applications through approved native/provider bridges and project APIs.
  • Negative, failure and recovery tests for “Application verifies and maps errors” and “Telemetry records package and backend versions”.
  • Signed acceptance record, accountable owner, published limitations and next review date.
STANDARDS & PROFILES
  • .NET / C#
  • CMS / CAdES
  • CNG or native provider bridges
  • Release-specific packaging

PRODUCT-SPECIFIC BOUNDARIES

Conditions that must remain true for Trusted PQC .NET SDK.

These points come from the product profile, not from a shared disclaimer.

NEXT STEP

Define a controlled pilot: Trusted PQC .NET SDK

Select one application, exact versions, measurable acceptance criteria and rollback.