10 Avoid long-term, side-by-side operation of deployed and PIV technologies. Once PIV
All changes in this version
Title changed
Before · SP 800-116
Avoid long-term, side-by-side operation of deployed and PIV technologies. Once PIV
After · SP 800-116 Rev. 1
Avoid long-term, side-by-side operation of deployed and PIV technologies. Once PIV
Control changed
Before · SP 800-116
Cards have been issued to half the users, cut costs by aggressive completion of the migration.
9.6 PIV Implementation Maturity Model (PIMM) In a document focused on the integration of PIV authentication mechanisms with PACS systems, it is impossible to provide detailed recommendations on project planning for PACS modifications or upgrades. The planning space is simply too large, due to the variations in local requirements, the asset inventory and impact assessment, project size, the installed base of electronic PACS systems, requirements for integration with other facilities’ infrastructure subsystems, etc. Instead, we recommend in this section a PIMM that can be used to measure the progress of a facility or an agency towards a complete PIV implementation. The PIMM should be applied only to facilities that have established a requirement for an electronic PACS. The PIMM is organized around the assumption of three enclosing perimeters: the Controlled area, the Limited area, and the Exclusion area, shown in Figure 7-1. In a general sense, “Controlled, Limited, Exclusion” areas may be considered as the security perimeters consistent with protection of low, moderate, and high impact assets, respectively. The following PIMM maturity levels begin by achieving some capability and experience with PIV-based PACS:
After · SP 800-116 Rev. 1
Cards have been issued to half the users, cut costs by aggressive completion of the migration.
9.6 PIV Implementation Maturity Model (PIMM) In a document focused on the integration of PIV authentication mechanisms with PACS systems, it is impossible to provide detailed recommendations on project planning for PACS modifications or upgrades. The planning space is simply too large, due to the variations in local requirements, the asset inventory and impact assessment, project size, the installed base of electronic PACS systems, requirements for integration with other facilities’ infrastructure subsystems, etc. Instead, we recommend in this section a PIMM that can be used to measure the progress of a facility or an agency towards a complete PIV implementation. The PIMM should be applied only to facilities that have established a requirement for an electronic PACS. The PIMM is organized around the assumption of three enclosing perimeters: the Controlled area, the Limited area, and the Exclusion area, shown in Figure 7-1. In a general sense, “Controlled, Limited, Exclusion” areas may be considered as the security perimeters consistent with protection of low, moderate, and high impact assets, respectively. The following PIMM maturity levels begin by achieving some capability and experience with PIV-based PACS: