Why should you care?

SOC2 audits ask which tools touch customer data; enterprise SK wiring answers with registration logs and version pins.

See it live — copy this example

Paste into an ASP.NET Core 8+ / AgentNest project, then run with dotnet run (set your API keys in user-secrets).

// AgentNest.Infrastructure/EnterpriseKernelBuilder.cs
public sealed class EnterpriseKernelBuilder(
    IChatClient chat, ITenantAiContextAccessor tenant, IEnumerable<IPluginProvider> providers)
{
    public Kernel Build()
    {
        var kb = Kernel.CreateBuilder();
        kb.Services.AddSingleton(chat);
        foreach (var name in tenant.Current.AllowedPlugins)
            kb.Plugins.Add(providers.Single(p => p.Name == name).CreatePlugin());
        return kb.Build();
    }
}

What happened?

• EnterpriseKernelBuilder registers only plugins listed in TenantAiContext via IPluginProvider factories.
• Follow the steps below — typing the code yourself is the fastest way to learn.

Practice next

1. build IPluginProvider per domain assembly.
2. Pin Microsoft.SemanticKernel version in Directory.Packages.props.
3. Log AllowedPlugins at kernel build time.
4. Cache Kernel metadata per tenant in IMemoryCache.
5. Add health check that verifies required plugins load.

Remember

Enterprise kernels filter plugins by tenant allow list. Centralize Kernel build in Infrastructure. Pin SK versions and audit plugin registration.

SOC2 plugin review

Auditors request proof hospital plugins cannot run on CRM tenants.

Outcome: EnterpriseKernelBuilder logs prove allow-list enforcement at build time.