Skip to main content

Provides support for some cryptographic primitives for .NET Framework and .NET Standard.

Total Downloads
427.7M
427,657,317
Published
Nov 10, 2026
12d ago

Get Started

dotnet add package Microsoft.Bcl.Cryptography --version 11.0.0
ProductVersions
.NET
net10.0net11.0
.NET Standard
netstandard2.0netstandard2.1
Other
.NETFramework4.6.2

README

About

This library provides some cryptographic types and functionality for .NET Standard and .NET Framework. This library is not necessary nor recommended when targeting versions of .NET that include the relevant support.

Key Features

  • Enables the use of some cryptographic functionality on older .NET platforms.

How to Use

This package should only be used by platforms where the desired functionality is not built-in.

using System.Security.Cryptography;

internal static class Program
{
    private static void Main()
    {
        byte[] key = LoadKey();
        using SP800108HmacCounterKdf kbkdf = new(key, HashAlgorithmName.SHA256);
        byte[] derivedKey = kbkdf.DeriveKey("label"u8, "context"u8, derivedKeyLengthInBytes: 32);
    }
}

Main Types

The main types provided by this library are:

  • System.Security.Cryptography.AesGcm
  • System.Security.Cryptography.CompositeMLDsa
  • System.Security.Cryptography.MLDsa
  • System.Security.Cryptography.MLKem
  • System.Security.Cryptography.SlhDsa
  • System.Security.Cryptography.SP800108HmacCounterKdf
  • System.Security.Cryptography.X509Certificates.X509CertificateLoader

Additional Documentation

Feedback & Contributing

Microsoft.Bcl.Cryptography is released as open source under the MIT license. Bug reports and contributions are welcome at the GitHub repository.

Downloads by Version

Depended On By

Find packages that declare this package as a dependency. NuGet does not provide a reverse-dependency endpoint, so candidates are checked on demand.

Adoption Assessment

A verified publisher signal is available. Assess fit from the package's supported frameworks, license and dependency graph rather than popularity alone.

Compatibility metadata lists 5 target frameworks; confirm the exact target used by your application.

Related Guides & Workflows

Learn how to evaluate, integrate, or audit this package in your .NET project.