Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Help Implementing FIPS Level 1 Requirements #4 #79

Open
jphung101 opened this issue Jun 26, 2024 · 1 comment
Open

Help Implementing FIPS Level 1 Requirements #4 #79

jphung101 opened this issue Jun 26, 2024 · 1 comment
Labels
question Further information is requested

Comments

@jphung101
Copy link

I was looking at the Level 1 Specific Requirements in README_FIPS.md and was stuck on how #4: Run integrity selftest at power on for SW component would be implemented. I was wondering if there were any good resources on implementing this? (Would it be just as simple as flashing a UEFI on my board, what I/O and components should be checked in the self-test, etc) Thanks a lot!

@jphung101 jphung101 changed the title Help Implementing FIPS Level 1 Requirements (#4) Help Implementing FIPS Level 1 Requirements #4 Jun 26, 2024
@rcao8
Copy link

rcao8 commented Dec 13, 2024

In the Intel Cryptography Library, integrity self-test is an important step to ensure that the cryptographic module has not been tampered with or damaged at startup. This self-test is often used to comply with the requirements of the FIPS (Federal Information Processing Standards) 140 series1.

When implementing this self-test, a specific API function is usually called at system startup to perform the self-test. For example, the Intel® Cryptography Primitives Library provides the fips_selftest_ippcp API to run the self-test1. The user's application should call these self-test functions before using the algorithm for the first time. see Example

@rcao8 rcao8 added the question Further information is requested label Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants