AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
securitycritical PriorityID: go-fips140-3-crypto-boundary-enforcement

Go 1.24 FIPS 140-3 Cryptographic Core Boundary and Cipher Enforcement

Enforces strict cryptographic boundary compliance utilizing Go 1.24 native FIPS 140-3 module capabilities. Prevents execution of unapproved cryptographic algorithms and guarantees deterministic service panic upon boundary breach in sovereign cloud environments.

Prohibited Anti-Pattern: Bypassing Native FIPS 140-3 Runtime Module Isolation with Unapproved Ciphers or Silent Fallbacks

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: "Go 1.24 FIPS 140-3 Cryptographic Core Boundary and Cipher Enforcement - Enforces strict cryptographic boundary compliance utilizing Go 1.24 native FIPS 140-3 module capabilities. Prevents execution of unapproved cryptographic algorithms and guarantees deterministic service panic upon boundary breach in sovereign cloud environments."
globs: "**/*.go, go.mod, Dockerfile"
alwaysApply: true
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/go-fips140-3-crypto-boundary-enforcement"
---

# Go 1.24 FIPS 140-3 Cryptographic Core Boundary and Cipher Enforcement

> **Severity**: CRITICAL | **Category**: security
> **Anti-Pattern Warning**: Bypassing Native FIPS 140-3 Runtime Module Isolation with Unapproved Ciphers or Silent Fallbacks

## System Constraints
You are a Principal Software Architect enforcing Go 1.24 FIPS 140-3 Cryptographic Core Boundary Enforcement. Sovereign cloud architectures require absolute cryptographic isolation. Mandate Go 1.24 native FIPS compliance, disallow unapproved algorithms, enforce deterministic panic triggers on boundary violation, and eliminate custom or third-party cipher bypasses.

## Strict Guidelines
- Services MUST verify Go 1.24 FIPS 140-3 module activation during package initialization (`init()`) and trigger an immediate, unrecoverable `panic` if the runtime boundary is inactive or non-compliant.
- Engineers MUST NOT catch or `recover()` from FIPS-enforced panics, ensuring deterministic crash-loop backoff alerting when non-compliant primitives are evaluated.
- Code MUST use Go standard library `crypto/*` packages tied to the native FIPS module (`GOFIPS140=v1.0.0` or `latest`) and MUST NEVER import third-party pure-Go primitives or uncertified external crypto engines.
- TLS configurations MUST explicitly mandate `tls.VersionTLS12` or `tls.VersionTLS13` and restrict `CipherSuites` strictly to NIST FIPS-approved algorithms (e.g., `TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256`, `TLS_AES_256_GCM_SHA384`).
- Engineers MUST NOT utilize broken or non-approved digests (e.g., MD5, SHA-1) for digital signatures, HMAC, or integrity verifications under any circumstance.

## Bad vs Good Implementations
### FIPS 140-3 Boundary Check & Secure TLS Configuration

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Fails to enforce Go 1.24 FIPS mode at startup, introduces forbidden MD5 hashing, and permits unapproved legacy TLS 1.0 protocols without cipher suite constraints.
```go
package crypto

import (
	"crypto/md5"
	"crypto/tls"
	"fmt"
)

// Bad: Does not assert FIPS 140-3 compliance at init, uses broken MD5,
// and permits legacy non-FIPS TLS negotiation.
func InitSecurityContext() *tls.Config {
	// Insecure: MD5 used for hash generation
	h := md5.New()
	h.Write([]byte("sovereign-token"))
	fmt.Printf("Token Hash: %x\n", h.Sum(nil))

	return &tls.Config{
		MinVersion: tls.VersionTLS10, // Non-compliant
	}
}
```

#### Production Standard (Correct)
> **Standard**: Asserts GOFIPS140 enforcement on service start with a deterministic panic, replaces non-compliant digests with SHA-256, and restricts TLS configurations strictly to FIPS-approved cipher suites.
```go
package crypto

import (
	"crypto/sha256"
	"crypto/tls"
	"os"
	"strings"
)

// Good: Enforces Go 1.24 FIPS 140-3 boundary activation at initialization
// and triggers a deterministic panic if the environment is non-compliant.
func init() {
	gofips := os.Getenv("GOFIPS140")
	if gofips == "" || gofips == "off" {
		panic("FATAL: FIPS 140-3 boundary violation: GOFIPS140 is not enforced")
	}
}

func InitSecurityContext() (*tls.Config, error) {
	h := sha256.New() // FIPS 140-3 approved
	if _, err := h.Write([]byte("sovereign-token")); err != nil {
		return nil, err
	}

	return &tls.Config{
		MinVersion: tls.VersionTLS12,
		CipherSuites: []uint16{
			tls.TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
			tls.TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
			tls.TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
			tls.TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
		},
	}, nil
}
```
Recommended MCP Servers (mcp-serverlist.com)

Equip agent with system tools to verify code for this stack.

Semgrep Security MCP
Scans Go codebases for unapproved cryptographic imports and non-FIPS primitive usages.
Recommended Agent Skills (askills.dev)

Ready-to-use executable skill functions tailored to this stack.

Go Vulnerability & FIPS Checker
Analyzes Go call graphs for unapproved cryptographic dependencies and security boundary leaks.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Go 1.24 FIPS 140-3 Cryptographic Core Boundary and Cipher Enforcement

Go 1.24 FIPS 140-3 Cryptographic Core Boundary and Cipher Enforcement defines an industrial-grade behavioral standard for security engineering. Enforces strict cryptographic boundary compliance utilizing Go 1.24 native FIPS 140-3 module capabilities. Prevents execution of unapproved cryptographic algorithms and guarantees deterministic service panic upon boundary breach in sovereign cloud environments. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: Bypassing Native FIPS 140-3 Runtime Module Isolation with Unapproved Ciphers or Silent Fallbacks Without an explicit system instruction file, developers spend hours debugging silent failures.
Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure ModeAI Symptom (The Anti-Pattern)SeverityProduction Impact & Remedy
AI Hallucination & Deprecation DriftBypassing Native FIPS 140-3 Runtime Module Isolation with Unapproved Ciphers or Silent FallbacksCritical
Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production.
Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture InconsistencyAI assistants produce mixed paradigms across files, creating fragmented codebase conventions.Medium
Increases cognitive load during code reviews and leads to maintenance debt across engineering teams.
Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.
Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

1

Services MUST verify Go 1.24 FIPS 140-3 module activation during package initialization (`init()`) and trigger an immediate, unrecoverable `panic` if the runtime boundary is inactive or non-compliant.

Services MUST verify Go 1.24 FIPS 140-3 module activation during package initialization (`init()`) and trigger an immediate, unrecoverable `panic` if the runtime boundary is inactive or non-compliant.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
2

Engineers MUST NOT catch or `recover()` from FIPS-enforced panics, ensuring deterministic crash-loop backoff alerting when non-compliant primitives are evaluated.

Engineers MUST NOT catch or `recover()` from FIPS-enforced panics, ensuring deterministic crash-loop backoff alerting when non-compliant primitives are evaluated.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
3

Code MUST use Go standard library `crypto/*` packages tied to the native FIPS module (`GOFIPS140=v1.0.0` or `latest`) and MUST NEVER import third-party pure-Go primitives or uncertified external crypto engines.

Code MUST use Go standard library `crypto/*` packages tied to the native FIPS module (`GOFIPS140=v1.0.0` or `latest`) and MUST NEVER import third-party pure-Go primitives or uncertified external crypto engines.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
4

TLS configurations MUST explicitly mandate `tls.VersionTLS12` or `tls.VersionTLS13` and restrict `CipherSuites` strictly to NIST FIPS-approved algorithms (e.g., `TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256`, `TLS_AES_256_GCM_SHA384`).

TLS configurations MUST explicitly mandate `tls.VersionTLS12` or `tls.VersionTLS13` and restrict `CipherSuites` strictly to NIST FIPS-approved algorithms (e.g., `TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256`, `TLS_AES_256_GCM_SHA384`).

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
5

Engineers MUST NOT utilize broken or non-approved digests (e.g., MD5, SHA-1) for digital signatures, HMAC, or integrity verifications under any circumstance.

Engineers MUST NOT utilize broken or non-approved digests (e.g., MD5, SHA-1) for digital signatures, HMAC, or integrity verifications under any circumstance.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
Technical Questions & Answers

Frequently Asked Technical Questions

Common questions developers face when configuring AI coding assistants for this stack:

Q:Why is Go 1.24 FIPS 140-3 Cryptographic Core Boundary and Cipher Enforcement critical for AI coding assistants?

Enforces strict cryptographic boundary compliance utilizing Go 1.24 native FIPS 140-3 module capabilities. Prevents execution of unapproved cryptographic algorithms and guarantees deterministic service panic upon boundary breach in sovereign cloud environments. Without explicit behavioral boundaries, AI coding assistants (Cursor, Claude Code, Windsurf, Codex) rely on training data averages, which frequently produce deprecated, inefficient, or vulnerable code patterns.

Q:How does adopting this rule prevent AI hallucinations?

This rule explicitly declares what the AI must avoid (Bypassing Native FIPS 140-3 Runtime Module Isolation with Unapproved Ciphers or Silent Fallbacks) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.

Q:Which AI coding environments are supported?

This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).

Q:Can I combine this rule with other technology stacks?

Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.

Open Specification · CC BY 4.0·Free for Personal, Team & Commercial In-Repo Use

Citation & Open Source Attribution Guidelines

This specification is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). You are completely free to adapt and share this rule in your workspace. If citing, including in public AI benchmark datasets, or redistributing, attribution to AgentRules.org is required.

Related SECURITY Rules

View all rules →
security
105

OpenFGA Graph Invariants: Cyclic Relation Prevention & Contextual Tuple Hardening

Enforces strict directed acyclic graph (DAG) topology validation during relationship mutation writes and mandates strict server-side schema verification for ephemeral contextual tuples in OpenFGA evaluations. Prohibits persistent storage of ephemeral request attributes and guards against recursive relation loops causing graph expansion denial-of-service.

security
81

WebAuthn Conditional UI Mediation, Nonce Atomicity, and Assertion Cryptographic Verification

Enforces zero-trust cryptographic validation for FIDO2/WebAuthn Passkey authentication with Conditional UI autofill. Requires atomic single-use challenge consumption to eliminate replay attacks, strict RP ID hash and origin binding, authenticatorData flag verification (User Presence and User Verification), and monotonic signature counter enforcement to detect authenticator cloning.

security
111

Enforce Sigstore Keyless OIDC Attestation and Admission Controller Verification

Enforces immutable supply-chain security using Sigstore Cosign keyless signing via ephemeral OIDC tokens issued by Fulcio and verified against the Rekor transparency log. Container workloads must be signed and attested at build time by digest, and admission controllers (such as Kyverno or Sigstore Policy Controller) must strictly validate the OIDC issuer and subject identity before allowing image execution.

1 Rule in Stack

Go