Shared Keys Clause Samples

The Shared Keys clause establishes the rules and responsibilities regarding the use and management of cryptographic keys that are accessible to multiple parties. Typically, this clause outlines how such keys are generated, distributed, stored, and protected, and may specify who is authorized to use them and under what circumstances. For example, in a data-sharing agreement, both parties might use a shared encryption key to access sensitive information. The core practical function of this clause is to ensure security and accountability when multiple parties require access to the same cryptographic resources, thereby reducing the risk of unauthorized access or data breaches.
Shared Keys. For Licensed Products containing Shared Device Key Sets, Adopter shall order and use only Device Key Sets designated by AACS as “Shared Device Keys”. Adopter shall implement Proactive Renewal for all Licensed Products containing Shared Device Key Sets. A Licensed Product may implement Proactive Renewal only if the Licensed Product is capable of receiving Periodic Updates, including after a Shared Device Key Set has been Expired in accordance with Section
View SourceView Similar (4)
Shared Keys. For Licensed Products containing shared Device Key Sets, Adopter shall order and use only Device Key Sets designated by AACS as “Type C”.
View SourceView Similar (3)
Shared Keys. 6.2. Real life parameters and security. ▇▇▇▇▇▇▇▇▇▇▇ [8] suggests that the success rate of a brute force attack decreases exponentially as the matrix order increases. In our context, this is irrelevant since the (X, Y) matrices are public and the security relies upon lambda and omega secret integers. Therefore, much attention must be paid to the pseudo-random number generator, since the security of the protocol depends sensibly on it, given the linear relationship between the public parameters (X, Y) and the private values (A, B). Since an attacker does not know (lambda, omega, A, B), a natural attack would be the systematic exploration of the space of the random constants (lambda, omega) which depend directly on the cardinal of the set ℤ𝑝 and in consequence the security against this attack is proportional to 𝑝2. We recommend using p ~ 264 as a minimum value. Thus, two random integers in ℤ𝑝 represent a 128-bit brute-force search. Consequently, overall security relies on the NP-hard nonlinear MPF [2] if the linear step becomes practically invulnerable.
View Source

Related to Shared Keys

  • Shared roles The Parties will meet the requirements of Schedule E, Clause 26 of the IGA FFR, by ensuring that prior agreement is reached on the nature and content of any events, announcements, promotional material or publicity relating to activities under this Agreement, and that the roles of both Parties will be acknowledged and recognised appropriately.

  • Shared Services CUPE agrees to adopt a shared services model that will allow other Trusts to join the shared services model. The shared services office of the Trust is responsible for the services to support the administration of benefits for the members, and to assist in the delivery of benefits on a sustainable, efficient and cost effective basis recognizing the value of benefits to the members.

  • Shared Personal Data This clause sets out the framework for the sharing of personal data between the parties as data controllers. Each party acknowledges that one party (the Data Discloser) will regularly disclose to the other party (the Data Recipient) Shared Personal Data collected by the Data Discloser for the Agreed Purposes.

  • Shared Costs (i) If the Parties elect to establish two-way Local Interconnection Trunks for reciprocal exchange of traffic, the cost of the two-way Local Interconnection Entrance Facility and DTT shall be shared among the Parties. CenturyLink will ▇▇▇▇ ▇▇▇▇ for the entire DTT and Local Interconnection Entrance Facility provided by CenturyLink at the rates in Table 1. CLEC will bill CenturyLink for CenturyLink’s portion of the same DTT and Local Interconnection Entrance Facility at the same recurring rates in Table 1 charged by CenturyLink based on the portion defined in (ii) below. (ii) CenturyLink’s portion of the DTT and Local Interconnection Entrance Facility will be based on the factor determined by CenturyLink using the following to assign the minutes for which CenturyLink is responsible: • All Local Traffic MOU that CenturyLink originates and sends to CLEC. • All CenturyLink originated IntraLATA LEC Toll MOU that CenturyLink sends to CLEC. • All other minutes are CLEC’s responsibility for purposes of allocating the shared costs.

  • Shared Transport The Shared Transport Network Element (“Shared Transport”) provides the collective interoffice transmission facilities shared by various Carriers (including Qwest) between end-office switches and between end-office switches and local tandem switches within the Local Calling Area. Shared Transport uses the existing routing tables resident in Qwest switches to carry the End User Customer’s originating and terminating local/extended area service interoffice Local traffic on the Qwest interoffice message trunk network. CLEC traffic will be carried on the same transmission facilities between end- office switches, between end-office switches and tandem switches and between tandem switches on the same network facilities that Qwest uses for its own traffic. Shared Transport does not include use of tandem switches or transport between tandem switches and end-office switches for Local Calls that originate from end users served by non- Qwest Telecommunications Carriers (“Carrier(s)”) which terminate to QLSP End Users.