Randall Easter, NIST, Security Testing Validation and Management Group
Partial Cryptographic AcceleratorsDraft IG 1.9: Hybrid Module is crypto software module that takes advantage of "Security Relevant Components" on a chip.
But, that doesn't cover modern processors like Oracle's SPARC T4 and Intel's AES-NI - so there is a new IG (1.X): Processor Algorithm Accelerators (PAA). If the software module relies on the instructions provided by the PAA (Mathematical construct and not the comlete algorithm as defined in NIST standards), and ccannot act independently - it's still a hybrid. If there are issues with the hardware and the software could work on it's own (or on other platforms), then it is NOT a hybrid. (YAY for clarification!)
Sub-Chip ModulesWhat is this? A complete implementation of a defined cryptograpic module is implemented on part of a chip substrate. This is different than when a partial implemenation of a defined cryptographic module is implemented on part of a chip substrate (see above).
A sub-chip has a logical soft core. The cryptographic module has a contiguous and defined logical boundary with all crypto contained within. Durign physical placement, the crypto gates are scattered. Testing at the logical soft core voundary does not verify correct operation after synthesis and placement.
There are a lot of requirements in play here for these sub-chip modules. There is a physical boundary and a logical boundary. The physical boundary is around a single chip. The logical boundary will represent the collection of physical circuitry that was synthesized from the high level VHDL soft core cryptographic models.
Porting is a bit more difficult here - the soft core cna be re-used, unchanged, and embedded in other single-chip constructs - this requires Operational Regression testing. This can be done at all levels, as long as other requirements are met.
If you have multiple disjoint sub-chip crypto... you can still do this, but it will result in two separate cryptographic modules/boundaries.
What if there are seveal soft cores, and they want to talk to each other? If I have several different disjoint software modules that are both validated and on the same physical device, we allow them to exchange keys in the clear. So, why not? As long as they are being directly transferred, and not outside of the trip through an intermediary.
As chip densities increase, we're going to see more of these cores on one chip.