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

Keys used to sign OCSP responses must be protected in HSMs #22

Open
BenWilson-Mozilla opened this issue Jul 6, 2022 · 2 comments
Open
Assignees

Comments

@BenWilson-Mozilla
Copy link
Contributor

The NCSSRs should state that the private signing keys for all OCSP responders must be protected in an HSM, as opposed to, for example, storage of OCSP private signing keys in software, which would be more susceptible to misuse and comprise. This issue came up during a threat-modeling discussion today in the weekly subgroup meeting. Protection of OCSP signing keys in HSMs should not just be an underlying assumption, but should be expressly required in the NCSSRs.

@bcmorton
Copy link

I think this should be a BR requirement and not a NCSSR requirement. Note the NCSSR does not have any key protection levels for any other private keys.

@clintwilson
Copy link
Member

The NCSSRs should perhaps describe the security requirements for the HSMs themselves, but perhaps not the contents of those HSMs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants