Method and system providing mutli-level security to gate level information flow
A preferred method for providing multi-level security to a gate level information flow receives or specifies a security lattice having more than two security levels. The security lattice defines how security levels relate to each other. A hardware design implementing information flows including flows having security levels specified by the security lattice is received. Logic is created for testing the hardware design in view of the security lattice. A logic function is created based upon the hardware design and the logic for testing to implement the security lattice. Another method receives a hardware design in a hardware description language. At least a portion of the hardware design is synthesized to gate level primitives. Functional component tracking logic supporting more than two-security levels is built from the gate level primitives. Functional components in the hardware design are simulated with the functional component tracking logic.
1. A method for providing multi-level security to a gate level information flow, the method comprising:
receiving or specifying a security lattice having more than two security levels, wherein the security lattice defines how security levels relate to each other by defining permitted communication channels between security levels and permitted information flow directions between the security levels;
receiving a hardware design implementing information flows including flows having security levels specified by the security lattice;
creating logic for testing the hardware design in view of the security lattice, wherein at least a portion of the hardware design is synthesized into primitive gate level hardware components and the logic adds more than two security level tracking logic to the gate level hardware components to test for violations of the permitted communication channels and the permitted information flow directions; and
outputting a logic function based upon the hardware design and the logic for testing to implement the security lattice.
2. The method of claim 1 , further comprising converting the logic function to a hardware design specification.
3. The method of claim 1 , wherein the hardware design is in a hardware description language.
4. The method of claim 1 , wherein said creating comprises building functional components of the hardware design from gate-level GLIFT (gate level information flow tracking) components to create complex GLIFT functional components and said outputting replaces portions of the hardware design with the complex GLIFT functional components.
5. The method of claim 1 , wherein said receiving or specifying a security lattice comprises converting a two-level GLIFT label propagation logic to a more than two level security label propagation logic.
6. The method of claim 1 , wherein
said receiving receives the hardware design in a hardware description language;
said creating logic comprises building functional component tracking logic;
and further comprising simulating functional components in the hardware design with the functional component tracking logic.
7. The method of claim 6 , further comprising testing an information flow labeled with one of the security levels for leaking to a lower classified security level area of the hardware design.
8. The method of claim 7 , wherein said testing accounts for values that can be taken by the information flow in addition to the security level of the information flow.
9. The method of claim 7 , wherein said simulating comprises gate level information flow tracking and an output of the flow tracking is bounded to the most restrictive security class whose data has an effect on the output.