Missing Support for Security Features in On-chip Fabrics or Buses

Many on-chip communication systems, especially simpler or low-power designs, are built solely for moving data and lack interfaces to carry critical security attributes like privilege levels or device identity from a master component (like a CPU) to a slave (like a peripheral). Without these dedicated signals, the fabric cannot enforce security policies, making it unsafe for transporting any sensitive security metadata. Even when a bus specification includes optional security signaling, these features are often left unconnected or disabled when the hardware design is generated. Consequently, any peripheral that handles security-sensitive assets should not be connected directly to such a bus unless robust access control is implemented at an earlier point, such as a bridge or intermediary module, before transactions enter the insecure fabric.