-
Notifications
You must be signed in to change notification settings - Fork 33
Agency Best Practices for Device Certificates #4
Comments
I can't find the material in the linked PDF in this repository. Where are you drawing it from? |
Also, some of it looks quite dated:
|
it's not in the repo - @ajones13 wants to add it to the repo somewhere...specific to fpki so we can remove the PDF documents entirely It's definitely dated which is why we're trying to "clean house"! 👍 |
Ah okay, I misread the intent -- I thought @ajones13 was saying they'd made a PDF version of this repository. Apologies for the distraction. |
#19 duplicate |
syncing private repo with updates to GSA FPKI main
Should this issue be closed? If USG is establishing a public NPE root, best practices would be for internally operated CAs. Is there a playbook that can be published? |
I wouldn't say that, since I don't expect the USG root to be mandated or used universally. And even for those who do use a new NPE root, how they choose to obtain those certificates (automated vs manual) is of some relevance. I've tried to include some guidance here: https://https.cio.gov/certificates/ Though it touches on some topics beyond best practices for device certificates. |
There are two different use cases:
So you're right eric - we should link to the https.cio.gov site for the web pki best practices as this also includes configuration best practices. For internal only locally trusted CAs, the only playbook we've put together is reusing one from DHS (that I send out / not posted) and a very short writeup for setting up a CA for domain controller certs (network auth). |
Do we need an NPE guide? PIV Guide Scope - Everything needed to setup and use PIV logically. FPKI Guide Scope - Everything that happens above PIV and software certs(?) New Device Guide Scope(?) - Everything devices(?). This might just be a pointer to the M-15-13 guidance, NIST 800-52, and maybe NCCOE TLS project. |
I'll transfer comments to #19 and close this issue. |
I am converting this document into a play.
https://www.idmanagement.gov/IDM/servlet/fileField?entityId=ka0t0000000TNOEAA4&field=File__Body__s
The text was updated successfully, but these errors were encountered: