MinimalCleanArch.Security 0.1.18-preview

MinimalCleanArch.Security

Security components for MinimalCleanArch.

Version

• Current preview: 0.1.18-preview (net9.0, net10.0). Latest stable: 0.1.17.

Why Use It

• encrypt sensitive values at the infrastructure layer instead of leaking encryption logic into entities or handlers
• support both development-friendly ASP.NET Core Data Protection encryption and production-oriented key management
• apply encrypted EF property conversions consistently across your data model

When to Use It

• use it when the application stores secrets or sensitive fields that should be encrypted at rest, especially in EF-backed persistence models
• keep it in infrastructure where encryption services, key management, and EF model configuration belong
• skip it when the application has no encrypted persistence requirements

Dependency Direction

• Depends on: no other MCA package
• Typically referenced by: infrastructure projects
• Can be used with: MCA apps or independently of the rest of MCA
• Do not reference from: domain projects; encryption concerns should stay outside the domain model

Overview

• Column-level encryption for EF Core.
• AES and Data Protection implementations of IEncryptionService.
• Value converters for encrypted properties.
• Extensions to configure encryption on your model.

Usage

dotnet add package MinimalCleanArch.Security --version 0.1.18-preview

Recommended service registration:

builder.Services.AddDataProtectionEncryptionForDevelopment("YourApp");

Production-style registration:

builder.Services.AddEncryption(new EncryptionOptions
{
    Key = "YOUR_SECURE_AES_KEY"
});

Model configuration:

protected override void OnModelCreating(ModelBuilder modelBuilder)
{
    base.OnModelCreating(modelBuilder);
    modelBuilder.UseEncryption(encryptionService);
}

Recommended guidance:

• use Data Protection-based encryption for new application development
• use AddDataProtectionEncryptionForDevelopment(...) only for local development
• use persistent key storage in production
• use the hybrid Data Protection and AES support when migrating legacy encrypted data
• keep encryption registration in infrastructure, not in domain or application layers

Key Components

• EncryptedAttribute - Marks properties for encryption
• IEncryptionService - Interface for encryption services
• AesEncryptionService - AES implementation of IEncryptionService
• EncryptedConverter - Value converter for encrypted properties