Incident and Compromise Handling Procedures As part of its incident and compromise handling procedures, each subscriber shall implement a procedure whereby it contacts [FMO Name] promptly upon discovery of any incident in which private key material governed by this CP was, or might have been, compromised. Computing Resources, Software, and/or Data Are Corrupted As part of its incident and compromise handling procedures, each subscriber shall implement a procedure whereby it contacts [FMO Name] promptly upon discovery of any incident in which private key material governed by this CP was, or may have been, compromised. Entity Private Key Compromise Procedures As part of its incident and compromise handling procedures, each subscriber shall implement a procedure whereby it contacts [FMO Name] promptly upon discovery of any incident in which private key material governed by this CP was, or may have been, compromised. Business Continuity Capabilities after a Disaster No stipulation. CA or RA Termination The topics of certificate authority (CA) and registration authority (RA) termination are not applicable to this CP, because the concepts of CA and RA are not applicable to this CP in the context in which they are addressed within this section. Technical Security Controls This section contains rules representing the minimal acceptable level of technical protection that must be applied to sensitive private key material corresponding to certificates covered by this CP and the systems on which the private key material is used. To help ensure the trustworthiness of the [Federation Name] Cryptographic Trust Fabric, all subscribers must obey the rules outlined in this section. In some circumstances, a subscriber may already have policies and procedures in place that preclude their ability to obey these rules. In this circumstance, the subscriber must notify [FMO Name] in writing of its inability to meet these requirements, and must also provide an explanation of why it is unable to meet the requirements.
Incident and Compromise Handling Procedures As part of its incident and compromise handling procedures, each subscriber shall implement a procedure whereby it contacts [FMO Name] promptly upon discovery of any incident in which private key material governed by this CP was, or might have been, compromised. Computing Resources, Software, and/or Data Are Corrupted As part of its incident and compromise handling procedures, each subscriber shall implement a procedure whereby it contacts [FMO Name] promptly upon discovery of any incident in which private key material governed by this CP was, or may have been, compromised. Entity Private Key Compromise Procedures As part of its incident and compromise handling procedures, each subscriber shall implement a procedure whereby it contacts [FMO Name] promptly upon discovery of any incident in which private key material governed by this CP was, or may have been, compromised. Business Continuity Capabilities after a Disaster No stipulation. CA or RA Termination The topics of certificate authority (CA) and registration authority (RA) termination are not applicable to this CP, because the concepts of CA and RA are not applicable to this CP in the context in which they are addressed within this section. Technical Security Controls This section contains rules representing the minimal acceptable level of technical protection that must be applied to sensitive private key material corresponding to certificates covered by this CP and the systems on which the private key material is used. To help ensure the trustworthiness of the [Federation Name] Cryptographic Trust Fabric, all subscribers must obey the rules outlined in this section. In some circumstances, a subscriber may already have policies and procedures in place that preclude their ability to obey these rules. In this circumstance, the subscriber must notify [FMO Name] in writing of its inability to meet these requirements, and must also provide an explanation of why it is unable to meet the requirements.