Enumeration of threats Sample Clauses

Enumeration of threats. To use this approach, one must find a way to enumerate potential threats representing the possible causes of adverse user experiences. Some of these threats are evident in the analysis of selected use cases described in Section 5.2, but this will only find some of the possible threats even when extended to cover all the use cases from Deliverable D2.1. It is therefore important to understand how such a threat catalogue could be created. It turns out that different sources of information are available for each of the broad classes of threats identified above, and the largest number of threats arise from malicious attacks, where fortunately there is a large corpus available for analysis. Malicious stakeholder threats: in 5G networks are likely to be covered quite well by the analysis of use cases from D2.1, plus additional scenarios that may be identified during the project. To become a stakeholder in a socio-technical system, one must adopt a legitimate role with respect to that system, so malicious stakeholder threats normally arise where there is a potential conflict of interests, e.g. between the Subscriber’s desire to use a service and the Service Provider’s requirement that they be paid for the service. A typical threat may involve a Subscriber seeking to defraud the Service Provider to get some services without paying. These types of threats will provide a basis for modelling U2U trust (between stakeholders), and help 5G stakeholders determine what issues should be addressed through service level or subscriber agreements. Internal failures and non-malicious actions: these types of threats represent error conditions. They arise because they were not foreseen during the development of a system, in the sense that errors that are foreseen are usually eliminated during the system implementation phase. Because the specific bugs or user errors are unforeseen, the most important issue for a threat modeller is to capture their consequences and potential measures to mitigate these consequences. It is relatively easy to classify such threats in those terms, e.g. by considering whether the error leads to a compromise in confidentiality, integrity or availability in the affected system or component. External disasters: are also relatively easy to classify in terms of their effect on the integrity or availability of the affected system(s) or component(s). From a trust perspective, the most relevant threats are localised threats affecting particular parts of the net...
AutoNDA by SimpleDocs

Related to Enumeration of threats

  • Reservation of Managerial Rights The foregoing enumeration of School Board rights and duties shall not be deemed to exclude other inherent management rights and management functions not expressly reserved herein, and all management rights and management functions not expressly delegated in this Agreement are reserved to the School Board.

  • ENUMERATION OF CONTRACT DOCUMENTS § 9.1 The Contract Documents, except for Modifications issued after execution of this Agreement, are enumerated in the sections below.

  • Inherent Managerial Rights The exclusive representative recognizes that the School District is not required to meet and negotiate on matters of inherent managerial policy, which include, but are not limited to, such areas of discretion or policy as the functions and programs of the employer, its overall budget, utilization of technology, the organizational structure and selection and direction and number of personnel.

  • Variation of the contract The parties undertake not to vary or modify the Clauses. This does not preclude the parties from adding clauses on business related issues where required as long as they do not contradict the Clause. Clause 11

  • Description of the service 9.1.1 Internet banking service implies an ability for the client to manage and receive remotely the following services from the bank by means of using the special Internet-site of the bank xxxxx://xxx.xxxxxxxxxxxxxxx.xx:

  • City’s Right to Terminate for Convenience City may, at its sole option and for its convenience, terminate all or any portion of this Contract by giving thirty (30) days’ written notice of such termination to Contractor. The termination of the Contract shall be effective upon receipt of the notice by Contractor. After termination of all or any portion of the Contract, Contractor shall: (1) immediately discontinue all affected performance (unless the notice directs otherwise); and (2) complete any and all additional work necessary for the orderly filing of documents and closing of Contractor's affected performance under the Contract. After filing of documents and completion of performance, Contractor shall deliver to City all data, drawings, specifications, reports, estimates, summaries, and such other information and materials created or received by Contractor in performing this Contract, whether completed or in process. By accepting payment for completion, filing, and delivering documents as called for in this section, Contractor discharges City of all of City’s payment obligations and liabilities under this Contract with regard to the affected performance.

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