BaselineWatch
Desk
Your fleet and your work Fleetyour releases and the hardware they run onTriagewhat needs a decisionWatchlistthe products and platforms you runSaved searchesthe lists you come back to
This instance Sourceswhat is read, how often, under what termsDigestthe daily or weekly summary, and alerts
How it is drawn Appearancethe look and the colour schemeBrandingthe mark this instance wears
Owner sign-in

3.2 Implementing Issuer Controls (was: Implementing PCI Controls)

NIST PIV and digital identity SP 800-79-2 against SP 800-79-1
All changes in this version
modified 3 T AXONOMY OF I SSUER C ONTROLS part of 3

Title changed

Before · SP 800-79-1

Implementing PCI Controls

After · SP 800-79-2

Implementing PCIIssuer Controls

Control changed

Before · SP 800-79-1

Each PCI control must be properly implemented, managed, and monitored in order for the PCI to be accredited. Depending on how an organization decides to implement their HSPD-12 program, the authority to implement some of the controls may not directly come under the PCI Management (due to outsourcing of certain PCI processes or using the PCI facilities of other organizations). However, it is still the responsibility of the PCI management to ensure that these PCI controls are being deployed, enforced, and maintained by its service provider.

After · SP 800-79-2

Each PCIissuer control must be properly implemented, managed, and monitored in order for the PCIissuer to be accreditedauthorized. Depending on how an organization decides to implement their HSPD-12[HSPD- 12] program, the authority to implement some of the controls may not directly come under the PCImanagement Managementof the issuer organization (due to outsourcing of certain PCIPIV processes or using the PCIissuing facilities of other organizations). However, it is still the responsibility of the PCI management of the issuer organization to ensure that these PCIissuer controls are being deployed, enforced, and maintained by its service provider.