Verification Code Injection at Build Time

2. The non-transitory computer-readable medium of claim 1, wherein generating the verification code includes determining an integrity value for at least one of the executable modules.

4. The non-transitory computer-readable medium of claim 2, wherein the integrity value is determined based on a digital signature.

6. The non-transitory computer-readable medium of claim 1, wherein the ephemeral key pair is unique to the plurality of sequentially ordered executable modules.

7. The non-transitory computer-readable medium of claim 1, wherein the operations further comprise discarding the private component.

8. The non-transitory computer-readable medium of claim 1, wherein the verification code verifies a subset of the executable modules.

9. The non-transitory computer-readable medium of claim 1, wherein the source contains an integrity violation response code configured to perform a security action based on the verification code.

10. The non-transitory computer-readable medium of claim 1, wherein the sequence is determined by an order of operations for building the executable modules.

11. The non-transitory computer readable medium of claim 1, wherein the verification code is configured to verify the integrity of a predetermined quantity of the executable modules.

14. The computer-implemented method of claim 13, wherein the source contains integrity violation response code configured to perform a security action based on the verification code.

16. The computer-implemented method of claim 13, wherein generating verification code includes generating a new executable module configured to verify the integrity of at least one of the plurality of neighboring executable modules.

17. The computer-implemented method of claim 13, wherein the integrity value of the at least one executable module includes a cryptographic hash value for one of the preceding executable modules in the sequence.

18. The computer-implemented method of claim 12, wherein generating verification code is repeated for each of the sequentially ordered executable modules.

20. The computer-implemented method of claim 12, wherein inserting the public component into one or more of the source code files occurs as the source code is compiled into an executable module.