I'm preparing to document a 3 tier PKI (with multiple second level policy CAs) and want to create a document that is useful, technical, and not too overwhelming to the non-PKI expert.
I suppose the audience could be broken up into the following roles
- People who request certificates
- Administrators who approve certificates
- Technical PKI administrators who replace me in the future
There could be more roles, but I don't want to create any unnecessary work for myself. No-one is asking for this information per-se, but I know this body of knowledge I've gathered needs to be stored somewhere.
- What audiences should a PKI administrator generate documentation for?
- What technical facts should be in the respective documentation?
- What should be out of scope (too detailed, or too simple) in each document?
This type of question comes from 1998 thinking as an MCSE where Microsoft had template documentation and checklists for various aspects of Windows. If other vendors (Entrust, etc) have relevant sample documentation that would be useful to structure my thinking.