Key Generation and Usage Sample Clauses

Key Generation and Usage. Where Key Pairs are generated by the Subscriber or the Certificate Requester, trustworthy systems must be used to generate Key Pairs, in which case, the following terms also apply: • Key Pairs must be generated using a platform recognized as being fit for such purpose. In the case of AATL Certificates, this must be FIPS 140-2 Level 2 compliant, • A key length and algorithm must be used which is recognized as being fit for the purpose of Digital Signature, • The Subscriber shall ensure that the Public Key submitted to GlobalSign correctly corresponds to the Private Key used. Where Key Pairs are generated in hardware (as required by the CPS): • The Subscriber must maintain processes, including, without limitation, changing of activation data, that assure that each Private Key within a hardware security module (HSM) or token can be used only with the knowledge and explicit action of the “Certificate Custodian”, • The Subscriber must ensure that the Certificate Custodian has received security training appropriate for purposes for which the Certificate is issued, and • Certificate Custodians undertake to take all reasonable measures necessary to maintain sole control of, keep confidential, and properly protect at all times the Private Key that corresponds to the Public Key to be included in the requested Certificate, as well as any associated authentication mechanism to access the key (e.g., password to a token or HSM).
Sample 1Sample 2
AutoNDA by SimpleDocs
Key Generation and Usage. 4.4.1 Where keys are generated by the Subscriber or the Certificate Requester, trustworthy systems must be used in order to generate public-private key pairs, in which case, the following terms also apply: • Keys must be generated using a platform recognized as being fit for purpose. In the case DocumentSign for Adobe PDF Digital Certificate, this must be FIPS 140-2 Level 2 compliant, • A key length and algorithm must be used which is recognized as being fit for purpose for Digital Signature, • The Subscriber shall ensure that the Public Key submitted to the GlobalSign CA correctly corresponds to the Private Key used, • The Subscriber shall exercise appropriate and reasonable care to avoid unauthorized use of its Private Key.
Sample 1
Key Generation and Usage. Where Key Pairs are generated by the Subscriber or the Certificate Requester, trustworthy systems must be used in order to generate Key Pairs, in which case, the following terms also apply: • Key Pairs must be generated using a platform recognized as being fit for such purpose. In the case of PDF Signing for Adobe CDS and EV Code Signing, this must be FIPS 140-2 Level 2 compliant, • A key length and algorithm must be used which is recognized as being fit for the purpose of Digital Signature, and • The Subscriber shall ensure that the Public Key submitted to the GlobalSign correctly corresponds to the Private Key used. Where Key Pairs are generated in hardware (as required by the CPS): • The Subscriber must maintain processes, including, without limitation, changing of activation data, that assure that each Private Key within a hardware security module (HSM) or token can be used only with the knowledge and explicit action of the “Certificate Custodian”, • The Subscriber must ensure that the Certificate Custodian has received security training appropriate for the purposes for which the Certificate is issued, and • Certificate Custodians undertake to take all reasonable measures necessary to maintain sole control of, keep confidential, and properly protect at all times the Private Key that corresponds to the Public Key to be included in the requested Certificate as well as any associated authentication mechanism to access the key - e.g., password to a token or HSM.
Sample 1
Key Generation and Usage. Where Key Pairs are generated by the Subscriber or the Certificate Requester, trustworthy systems must be used to generate Key Pairs, in which case, the following terms also apply:
Sample 1Sample 2
Key Generation and Usage. 4.11.1 Where Key Pairs are generated by the Subscriber or the Certificate Requester, trustworthy systems must be used in order to generate Key Pairs, in which case, the following terms also apply:  Key Pairs must be generated using a platform recognized as being fit for such purpose. In the case of PDF Signing for Adobe CDS and EV Code Signing, this must be FIPS 140-2 Xxxxx 0 xxxxxxxxx,  A key length and algorithm must be used which is recognized as being fit for the purpose of Digital Signature, and  The Subscriber shall ensure that the Public Key submitted to the GlobalSign correctly corresponds to the Private Key used.
Sample 1
Key Generation and Usage. The Subscriber shall be responsible to ensure that trustworthy systems and methods shall be used in order to generate public-private key pairs, moreover key lengths and algorithms must be used which is recognized as being fit for the requested certificate as per the COM-CA CP/CPS,  The Subscriber shall ensure that the Public Key submitted to AECE corresponds to the Private Key used,  The Subscriber shall exercise appropriate and reasonable care to avoid unauthorized use of its Private Key.  The Subscriber maintains reasonable measures to maintain sole control, keep confidential, and properly protect at all times the Private Key that corresponds to the Public Key to be included in the requested certificate.  The Subscriber shall use the certificate(s) issued by the COM-CA solely in compliance with the COM-CA CP/CPS and this subscriber agreement. Under no circumstances shall a certificate be used for criminal activities.
Sample 1
Key Generation and Usage. Trustworthy systems and methods shall be used to generate public-private key pairs. • A key length and algorithm must be used which is recognized as being fit for purpose for the Digital Signature, • The Subscriber shall ensure that the Public Key submitted to Technology Source corresponds to the Private Key used, • The Subscriber shall exercise appropriate and reasonable care to avoid unauthorized use of its Private Key, • The Subscriber maintains reasonable measures to maintain sole control, keep confidential, and properly always protect the Private Key that corresponds to the Public Key to be included in the requested certificate. • The Subscriber shall use the provided certificate(s) solely in compliance with all applicable laws and this Subscriber Agreement. Under no circumstances shall a certificate be used for criminal activities such as phishing attacks, fraud, certifying or signing malware etc. For Code Signing Subscriber confirms that Subscriber it will use one of the following options to generate and protect their Code Signing Certificate Private Keys in a Hardware Crypto Module with a unit design form factor certified as conforming to at least FIPS 140‐2 Level 2 or Common Criteria EAL 4+: • Subscriber uses a Hardware Crypto Module meeting the specified requirement. • Subscriber uses a cloud‐based key generation and protection solution with the following requirements: o Key creation, storage, and usage of Private Key must remain within the security boundaries of the cloud solution’s Hardware Crypto Module that conforms to the specified requirements. o Subscription at the level that manages the Private Key must be configured to log all access, operations, and configuration changes on the resources securing the Private Key. • Subscriber uses a Signing Service which meets the requirements of Section 6.2.7.3 of the “Baseline Requirements for the Issuance and Management of Publicly‐Trusted Code Signing Certificates”. At any time during the application and life cycle of the Certificate, Subscriber must be able to, on request of Technology Source, present proof that Key Pair is generated and protected in accordance with these requirements. Failure to provide such evidence might result in revocation of the Certificate. Subscriber Agreement
Sample 1
AutoNDA by SimpleDocs

Related to Key Generation and Usage

  • Synchronous Generation The Interconnection Customer shall design its Small Generating Facility to maintain a composite power delivery at continuous rated power output at the Point of Interconnection at a power factor within the range of 0.95 leading to 0.95 lagging, unless the NYISO or the Transmission Owner in whose Transmission District the Small Generating Facility interconnects has established different requirements that apply to all similarly situated generators in the New York Control Area or Transmission District (as applicable) on a comparable basis, in accordance with Good Utility Practice.

  • Non-Synchronous Generation The Interconnection Customer shall design its Small Generating Facility to maintain a composite power delivery at continuous rated power output at the high-side of the generator substation at a power factor within the range of 0.95 leading to 0.95 lagging, unless the NYISO or the Transmission Owner in whose Transmission District the Small Generating Facility interconnects has established a different power factor range that applies to all similarly situated non-synchronous generators in the control area or Transmission District (as applicable) on a comparable basis, in accordance with Good Utility Practice. This power factor range standard shall be dynamic and can be met using, for example, power electronics designed to supply this level of reactive capability (taking into account any limitations due to voltage level, real power output, etc.) or fixed and switched capacitors, or a combination of the two. This requirement shall only apply to newly interconnecting non-synchronous generators that have not yet executed a Facilities Study Agreement as of September 21, 2016.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Xxxx Communications has requested an Unbundled Loop and BellSouth uses Integrated Digital Loop Carrier (IDLC) systems to provide the local service to the end user and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Xxxx Communications. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will make alternative arrangements available to Xxxx Communications (e.g. hairpinning).

  • Modification of the Small Generating Facility The Interconnection Customer must receive written authorization from the NYISO and Connecting Transmission Owner before making any change to the Small Generating Facility that may have a material impact on the safety or reliability of the New York State Transmission System or the Distribution System. Such authorization shall not be unreasonably withheld. Modifications shall be done in accordance with Good Utility Practice. If the Interconnection Customer makes such modification without the prior written authorization of the NYISO and Connecting Transmission Owner, the Connecting Transmission Owner shall have the right to temporarily disconnect the Small Generating Facility. If disconnected, the Small Generating Facility will not be reconnected until the unauthorized modifications are authorized or removed.

  • Generating Facility The Interconnection Customer’s device for the production of electricity identified in the Interconnection Request, but shall not include the Interconnection Customer’s Interconnection Facilities.

Time is Money Join Law Insider Premium to draft better contracts faster.