NIST AI Agent Critical Infrastructure Alignment

Audience

Security and compliance reviewers mapping HELM AI Kernel receipts and conformance evidence to NIST critical-infrastructure concerns.

Outcome

After this page you should know what this surface is for, which source files own the behavior, which public route or adjacent page to use next, and which validation command to run before changing the claim.

Source Truth

• Public route: helm-ai-kernel/compliance/nist-ai-agent-critical-infrastructure
• Source document: helm-ai-kernel/docs/compliance/nist-ai-agent-critical-infrastructure.md
• Public manifest: helm-ai-kernel/docs/public-docs.manifest.json
• Source inventory: helm-ai-kernel/docs/source-inventory.manifest.json
• Validation: make docs-coverage, make docs-truth, and npm run coverage:inventory from docs-platform

Do not expand this page with unsupported product, SDK, deployment, compliance, or integration claims unless the inventory manifest points to code, schemas, tests, examples, or an owner doc that proves the claim.

Troubleshooting

Diagram

This scheme maps the main sections of NIST AI Agent Critical Infrastructure Alignment in reading order.

flowchart TD
    subgraph Ingestion["1. Ingestion & Context Plane"]
        Page["NIST AI Agent Critical Infrastructure Alignment"]
        A["Source Status"]
        B["Control Crosswalk"]
        C["Reference Pack Semantics"]
        D["Operator Notes"]
    end

    %% Operational Flow Edges
    Page --> A
    A --> B
    B --> C
    C --> D

    %% Premium Styling Rules

flowchart TD
    subgraph Ingestion["1. Ingestion & Context Plane"]
        Page["NIST AI Agent Critical Infrastructure Alignment"]
        A["Source Status"]
        B["Control Crosswalk"]
        C["Reference Pack Semantics"]
        D["Operator Notes"]
    end

    %% Operational Flow Edges
    Page --> A
    A --> B
    B --> C
    C --> D

    %% Premium Styling Rules

This page maps current NIST AI-agent and critical-infrastructure work to HELM AI Kernel controls.

Source Status

NIST has not published a finalized "AI Agent - Critical Infrastructure Profile" as of April 29, 2026. The implemented HELM artifact is therefore an early alignment pack grounded in these current NIST sources:

The reference pack is reference_packs/nist_ai_agent_cip.v1.json. It should be treated as a concept-note alignment until NIST publishes a stable control catalog or profile.

Control Crosswalk

Reference Pack Semantics

The nist-ai-agent-cip-v1 pack contains four active programs:

1. prog-agent-identity-authorization - binds every autonomous action to a principal and scoped delegation authority.
2. prog-critical-infrastructure-risk - requires approval or fail-closed denial for high-impact critical-infrastructure effects.
3. prog-secure-interoperable-protocols - denies unmanaged connector and protocol surfaces.
4. prog-supply-chain-assurance - requires provenance and policy-content evidence for critical-infrastructure activation.

The pack deliberately uses HELM's existing reference-pack vocabulary. It does not claim NIST endorsement or final profile conformance.

Operator Notes

For critical-infrastructure deployments, set critical_infrastructure=true in the policy context and bind the nist-ai-agent-cip-v1 reference pack alongside jurisdiction and industry packs. The pack assumes:

• Agent identity is present before any side-effecting action.
• Delegated authority is validated when an agent acts for a user or another agent.
• High-risk CI effects have approval evidence before execution.
• Policy and artifact state is content-addressed.
• Evidence packs are retained long enough for incident reconstruction and audit review.