https://github.com/sambacha/boilerplate-certificate-practice-statement
Certificate Practice Statement Boilerplate for providing an official CSP for code signing/pki
https://github.com/sambacha/boilerplate-certificate-practice-statement
certificate-authority certificate-practice-statement certificate-transparency codesigning cps x509
Last synced: 2 months ago
JSON representation
Certificate Practice Statement Boilerplate for providing an official CSP for code signing/pki
- Host: GitHub
- URL: https://github.com/sambacha/boilerplate-certificate-practice-statement
- Owner: sambacha
- Created: 2020-09-25T04:03:44.000Z (about 5 years ago)
- Default Branch: master
- Last Pushed: 2021-01-19T16:14:01.000Z (over 4 years ago)
- Last Synced: 2025-04-15T06:15:00.919Z (6 months ago)
- Topics: certificate-authority, certificate-practice-statement, certificate-transparency, codesigning, cps, x509
- Language: CSS
- Homepage:
- Size: 280 KB
- Stars: 5
- Watchers: 2
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Certificate Practice Statement
> Certificate Practice Statement Boilerplate for providing an official CSP for code signing/pki
### Abstract
A CPS is a statement of the practices that a certification authority (CA) employs in issuing, suspending, revoking,
and renewing certificates and providing access to them, in accordance with specific requirements
(i.e., requirements specified in this Certificate Policy, or requirements specified in a contract for services).
from: [NIST.SP.800-32](https://doi.org/10.6028/NIST.SP.800-32)
A statement of the practices that a CA employs in issuing, suspending, revoking and renewing certificates and providing access to them,
in accordance with specific requirements (i.e., requirements specified in this CP, or requirements specified in a contract for services).
### Conversion
Originally converted from PDF to Microsoft Docx, then into GitHub Flavoured Markdown and HTML
```bash
# where $filename.docx is the converted PDF from GlobalSign
$ pandoc -f docx -t markdown_mmd $filename.docx --output=OUTPUT.md --atx-headers --wrap=none --toc --extract-media=""
```
### Building
Use the files in `dist/` or the compiled outputs offered in the following formats:
1. `.rst`
2. `.md`
3. `.docx`
### Source(s)
[NIST SP 800-32 under Certification Practice Statement (CPS)](https://doi.org/10.6028/NIST.SP.800-32)
[NIST Glossary](https://csrc.nist.gov/glossary/term/certification_practice_statement)
[GlobalSign CPS Template](https://www.globalsign.com/en/repository/TrustedRoot%20Template%20CPS.pdf)
## License
All Rights are owned by their respective holders
No claim asserted over GlobalSign's boilerplate template. Any code is licesned under the ISC licesne
This is not legal advice nor should it be taken as an authoritative guide on issuance of such polices as it relates to CPS guidelines