Improper Identifier for IP Block used in System-On-Chip (SOC)

Draft Base
Structure: Simple
Description

This weakness occurs when a System-on-Chip (SoC) lacks a secure, unique, and permanent identifier for its internal hardware components (IP blocks). Without this, the system cannot reliably distinguish between different parts of the chip, leading to security and reliability failures.

Extended Description

A System-on-Chip integrates multiple hardware components, or IP blocks, each with different security needs. A unique and immutable identifier for each block is essential for secure operations like routing transactions, managing resets, or controlling access to sensitive data. When this identifier is missing or flawed, the SoC cannot properly authenticate which component is making a request, opening the door to spoofing, unauthorized actions, and system malfunctions. This vulnerability typically manifests in four ways: a completely missing identifier mechanism, an insufficient identifier that doesn't block all relevant attacks, a misconfigured mechanism that isn't implemented correctly, or an ignored identifier where the SoC doesn't enforce security policies based on it. Each scenario prevents the system from establishing the trusted identity required for secure communication and access control between chip components.

Common Consequences 1
Scope: Access Control

Impact: Bypass Protection Mechanism

Potential Mitigations 1
Phase: Architecture and Design

Strategy: Separation of Privilege

Every identity generated in the SoC should be unique and immutable in hardware. The actions that an IP is trusted or not trusted should be clearly defined, implemented, configured, and tested. If the definition is implemented via a policy, then the policy should be immutable or protected with clear authentication and authorization.
Applicable Platforms
Languages:
Not Language-Specific : Undetermined
Technologies:
System on Chip : Undetermined
Modes of Introduction
Architecture and Design
Implementation
Operation