Security goals Sample Clauses

The 'Security goals' clause defines the specific objectives and standards that parties must achieve to ensure the protection of information, systems, or assets. It typically outlines the required levels of confidentiality, integrity, and availability, and may specify compliance with certain security frameworks or regulations. By clearly stating these goals, the clause provides a benchmark for evaluating security measures and helps prevent misunderstandings about the expected level of protection, thereby reducing the risk of security breaches and disputes.
Security goals. Towards a SMI network an adequate se- curity suite essentially satisfies the following goals: 1) Mutual authentication and key establishment: In a SMI network, it is paramount security requirement that a NAN gateway must authenticate to a smart meter, since consumption data collected from smart meters will be utilized for many purposes e.g., billing, load balancing, etc. Similarly, a smart meter should authenticate the NAN gateway in order to protect from fake messages (e.g., control commands, etc.) from an attacker. Thus mutual authentication is highly required [32]. As soon as mutual authentication verified, a fresh session key agreement should be generated for the legal parties, so that subsequent communication could take place securely.
View SourceView Similar (4)
Security goals. The objective of the proposed scheme is the establishment of the session keys and the authentication of the users. The formalized goals of the scheme are as follows: G1: Sk possess at [1] H(XOR(H(Nz,Ny), H(Ui,Ny)),NtH(H(H(Ui,Ny),Nz),XOR(H(Nz,Ny), H(Uj,Ny))));
View SourceView Similar (2)
Security goals. The scheme is supposed to satisfy the following security goals.
View Source
Security goals. The following security goals can be identified for any GKA protocol. 1) Key Secrecy: The key can be computed only by the GKA participants. 2) Key Independence: Knowledge of any set of group keys does not lead to the knowledge of any other group key not in this set (see [9]).
View Source
Security goals. The stakeholder interests are related to a particular (business) goal or function which will be elaborated upon in each of the specific SEGRID use cases. Security goals are related to specific architectural assets (information, function, system and/or network) that are critical to achieve these goals or functions. By determining what security properties of these assets need to be preserved in order to ensure the stakeholders interests, the security goals can be defined. The property types are typically derived from the information security domain. A well-known and renowned set of standards for Information Security Management is the ISO/IEC 27000 series. The first standard ISO/IEC 27000:2014 [4] provides the set of definitions and terms. Information security is defined as: Information security – preservation of confidentiality, integrity and availability of information. Note: In addition, other properties, such as authenticity, accountability, non- repudiation, and reliability can also be involved. Here confidentiality, integrity and availability are defined as follows: The property availability is applicable to information as well as to a (information processing) function, process or system. In the context of smart grids, availability is often regarded as the most important property [5]. Ensuring availability of the power supply is indeed very important. The availability of information or of an information processing function is not necessarily more important than the integrity of the information to ensure the availability of power supply. A common debate on data integrity is whether it also means that the data is correct. Therefore, correctness integrity is sometimes included as an additional property. Moreover, the authenticity of the origin of information is also not included in the definition above. Data origin integrity or authenticity is commonly addressed as a separate property. For the definition of security goals of the SEGRID use cases we will use both data integrity & authenticity as aspects of integrity. The security goal shall make clear which of the two, or if both are meant. In the definition of information security above, accountability is mentioned as an additional property that is sometimes relevant. Within the context of smart grids we expect that accountability is relevant. ISO/IEC 27000:2014 does not contain a definition of this property. ISO 7498-2:1989 provides the following definition of accountability: A specific type of accountabi...
View Source

Related to Security goals

  • Performance Goals A. The Trust and State Street have developed mutually acceptable performance goals dated March 1, 2011 , and as may be amended from time to time, regarding the manner in which they expect to deliver and receive the services under this Agreement (hereinafter referred to as “Service Level Agreement”). The parties agree that such Service Level Agreement reflects performance goals and any failure to perform in accordance with the provisions thereof shall not be considered a breach of contract that gives rise to contractual or other remedies. It is the intention of the parties that the sole remedy for failure to perform in accordance with the provisions of the Service Level Agreement, or any dispute relating to performance goals set forth in the Service Level Agreement, will be a meeting of the parties to resolve the failure pursuant to the consultation procedure described in Sections V. B. and V.C. below. Notwithstanding the foregoing, the parties hereby acknowledge that any party’s failure (or lack thereof) to meet the provisions of the Service Level Agreement, while not in and of itself a breach of contract giving rise to contractual or other remedies, may factor into the Trust’s reasonably determined belief regarding the standard of care exercised by State Street hereunder.

  • Contract Goals A. For purposes of this procurement, OGS conducted a comprehensive search and determined that the Contract does not offer sufficient opportunities to set goals for participation by MWBEs as subcontractors, service providers, or suppliers to Contractor. Contractor is, however, encouraged to make every good faith effort to promote and assist the participation of MWBEs on this Contract for the provision of services and materials. The directory of New York State Certified MWBEs can be viewed at: ▇▇▇▇▇://▇▇.▇▇▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇/FrontEnd/VendorSearchPublic.asp?TN=ny&XID=2528. Additionally, following Contract execution, Contractor is encouraged to contact the Division of Minority and Women’s Business Development ((▇▇▇) ▇▇▇-▇▇▇▇; (▇▇▇) ▇▇▇-▇▇▇▇; or (▇▇▇) ▇▇▇-▇▇▇▇) to discuss additional methods of maximizing participation by MWBEs on the Contract. B. Good Faith Efforts Pursuant to 5 NYCRR § 142.8, evidence of good faith efforts shall include, but not be limited to, the following: 1. A list of the general circulation, trade, and MWBE-oriented publications and dates of publications in which the Contractor solicited the participation of certified MWBEs as subcontractors/suppliers, copies of such solicitations, and any responses thereto. 2. A list of the certified MWBEs appearing in the Empire State Development (“ESD”) MWBE directory that were solicited for this Contract. Provide proof of dates or copies of the solicitations and copies of the responses made by the certified MWBEs. Describe specific reasons that responding certified MWBEs were not selected. 3. Descriptions of the Contract documents/plans/specifications made available to certified MWBEs by the Contractor when soliciting their participation and steps taken to structure the scope of work for the purpose of subcontracting with, or obtaining supplies from, certified MWBEs. 4. A description of the negotiations between the Contractor and certified MWBEs for the purposes of complying with the MWBE goals of this Contract. 5. Dates of any pre-bid, pre-award, or other meetings attended by Contractor, if any, scheduled by OGS with certified MWBEs whom OGS determined were capable of fulfilling the MWBE goals set in the Contract. 6. Other information deemed relevant to the request.

  • Project Goals The schedule, budget, physical, technical and other objectives for the Project shall be defined.

  • Objectives The Parties conclude this Agreement, among others, for purposes of: (a) Encouraging expansion and diversification of trade between the Parties; (b) Eliminating the barriers to trade in, and facilitate the cross-border movement of goods and services between the Parties; (c) Promoting fair competition in the Parties' markets; (d) Creating new employment opportunities; (e) Creating framework for furthering bilateral, regional and multilateral cooperation to expand and enhance the benefits of this Agreement; and (f) Providing forum and approach for resolution of disputes amiably.

  • Goals Goals define availability, performance and other objectives of Service provisioning and delivery. Goals do not include remedies and failure to meet any Service Goal does not entitle Customer to a Service credit.