Sample – PKI Project Requirements
March 6, 2013Conditions / capabilities that must be met for the customer to find the product/service acceptable.
- Migration of existing Certificates for Corp-Signature from the Corporate 2013 CA to the new Corporate 2013 Root CA
- Migration of existing Certificates for Server SSL from the Corporate 2013 CA to the new Corporate 2013 Root CA
- Migration of existing Certificates for Access Control from the Corporate 2013 CA to the new Corporate 2013 Root CA
- Migration of all Certificates Issue out of the IT Security “Standard SSL” to the VeriSign supported Multi-tier Certificate environment.
- Correct the functional problem to enable the Secure Email service out of the MPKI User Service portal.
- Integration of a control and document process for issuing Code Signing Certificates with in the MPKI.
Constraints
- Possible delays on mgration to late 2013 MPKI environment due to configuration require by vendor
- Discovering of application owners who will need to migrate and test their applications in the new environment
- Unable to identify owners of live update supporting the CodeSigning definitions files.
Affected Products, Services, Operations, Organizations
- What other groups will be involved in the implementation?
- What operations could be affected as a result of the implementation?
Affected Services
- Corp-Signature, Access Control, Internal SSL from 2013 CA
- Corp-Signature, Access Control, Internal SSL from 2013 CA
- Secure eMail, and IT Security
Assumptions
- Require Access to the VeriSign Mange PKI admin site will be granted
- Application owner to work with the MPKI admin to test their application with the new environment. Migrate current certificates out of the old environment.
- VeriSign to be able to re-certify the 2013-2014 environment to extended the validity period of the Subordinate CAs.