---
title: Garmo-PUF-Core | Garmo Labs
url: https://garmolabs.com/ip/garmo-puf-core
description: Security — multi-source silicon PUF root-key subsystem
---

[Ip](https://garmolabs.com/marketplace) › IP-2081

Security & trust

# Garmo-PUF-Core

Security — multi-source silicon PUF root-key subsystem

Evaluation package

[Request evaluation](https://garmolabs.com/contact?products=ip-ip-2081)

Gar Security & trust

THE TECHNICAL ROLE

## A clear integration boundary.

Garmo-PUF-Core integration role: Security — multi-source silicon PUF root-key subsystem. Documented composition: SRAM/RO/bistable PUF source abstraction; at least two physically independent sources; Enrollment helper data with BCH/LDPC-style fuzzy extractor boundary; Aging/temperature compensation and confidence scoring.

01

SRAM/RO/bistable PUF source abstraction

02

at least two physically independent sources

03

Enrollment helper data with BCH/LDPC-style fuzzy extractor boundary

04

Aging/temperature compensation and confidence scoring

TECHNICAL OVERVIEW

## The details matter.

[Download the product brief](https://garmolabs.com/static/briefs/ip-ip-2081.pdf)

Canonical identity

IP-2081

Responsibility

Security — multi-source silicon PUF root-key subsystem

Documented interface architecture

PUF hard-macro sample bus, CSR, key-ladder output, lifecycle/zeroize

Documented building blocks

SRAM/RO/bistable PUF source abstraction; at least two physically independent sources; Enrollment helper data with BCH/LDPC-style fuzzy extractor boundary; Aging/temperature compensation and confidence scoring

Delivery boundary

Evaluation / IP scope

Evidence scope

Evaluation package

Architecture targets · not measurements

256-bit derived root key; <1e-6 reconstruction failure target after ECC; zero stored root secret.

### Before integration.

Garmo-PUF-Core integration role: Security — multi-source silicon PUF root-key subsystem. Documented composition: SRAM/RO/bistable PUF source abstraction; at least two physically independent sources; Enrollment helper data with BCH/LDPC-style fuzzy extractor boundary; Aging/temperature compensation and confidence scoring.

- Interface version and parameter set
- Clock/reset domains and integration constraints
- Companion memory, PHY and software requirements
- Verification collateral and acceptance criteria

The selected release must confirm:

- Node/library binding
- Clock/reset limits
- Physical and protocol dependencies
- Artifact hashes
- Acceptance criteria

Unpublished values are not inferred from family names or architecture targets.

[Discuss the integration](https://garmolabs.com/contact?products=ip-ip-2081)

Evaluation package

## Know the release.
Know what it establishes.

Canonical technology and its architecture/integration role are recorded. The offered delivery is confirmed against the exact release before licensing.

This is a controlled-portfolio summary, not a fresh execution of the chip qualification flow.

[Explore the evidence center](https://garmolabs.com/evidence) [Qualification record](https://garmolabs.com/qualification/ip-ip-2081)

### Release-specific qualification

Physical entropy, uniqueness and stability require measured silicon characterization.

Canonical record: P3 / REPRESENTATIVE ARCHITECTURE RTL — concrete integration specification and synthesizable RTL shell/representative datapath only; all frequency, throughput, power, area, jitter and standards-superiority figures remain architecture targets until the required evidence hierarchy closes. Analog/custom production claims require transistor-level/custom-layout, extracted PVT/Monte-Carlo and silicon characterization.

A PATH THAT FITS THE PROJECT

## Build with Garmo-PUF-Core.

Technical scope, rights, support and release configuration are agreed before delivery.

evaluation

### Evaluate an individual IP configuration

Inspect the named release and establish technical fit.

[Discuss this scope](https://garmolabs.com/contact?products=ip-ip-2081&scope=evaluation)

production

### Named-design production license

Agree deployment or design rights, deliverables and support.

[Discuss this scope](https://garmolabs.com/contact?products=ip-ip-2081&scope=production)

custom

### Node binding or derivative integration

Define the customer-specific work and acceptance criteria.

[Discuss this scope](https://garmolabs.com/contact?products=ip-ip-2081&scope=custom)

## Keep exploring.

Security & trust

[## KENBE Authority Guard](https://garmolabs.com/ip/kenbe-authority-guard)

Checks memory request domain/authority permissions.

RTL + models

IP-4017 · Source / reference evidence

Security & trust

[## KENBE Certified-Crypto Boundary](https://garmolabs.com/ip/kenbe-certified-crypto-boundary)

Boundary/control contract to qualified encryption/authentication macros without toy cryptography.

RTL + models

IP-4018 · Source / reference evidence

Security & trust

[## KENBE Epoch / Version Guard](https://garmolabs.com/ip/kenbe-epoch-version-guard)

Rejects stale epoch/version operations under the KENBE transaction contract.

RTL + models

IP-4019 · Source / reference evidence

## Your next big idea.
Let’s build it together.

Start with a chip, a software release or a single IP block.

[Talk to Garmo](https://garmolabs.com/contact) [Start exploring](https://garmolabs.com/developers)

CANONICAL EVIDENCE RECORD · IP-2081

### Source documented

A concrete source or implementation record exists; the selected evidence does not establish complete qualification.

**Record integrity and qualification boundary**Retained exact-release source reference; no new table locator was inferred.

Evidence ranking for evaluation prioritization; not a probability or certification.

[How evidence priority is determined ](https://garmolabs.com/marketplace/evidence)