Event model Clause Samples

The Event Model clause defines the framework for how events are recognized, categorized, and processed within an agreement or system. It typically outlines what constitutes an event, how events are triggered, and the procedures for responding to them, such as notifications, logging, or escalation steps. By establishing clear rules for event handling, this clause ensures consistent responses to specific occurrences, reducing ambiguity and supporting efficient management of contractual or operational processes.
Event model. The “event” entity in 4SECURail will describe a cyber-security incident, threat, vulnerability or risk, and will be used as the information unit to be shared with other organisations for intelligence purposes. This event model will therefore be flexible to admit a large variety of fields for supporting security teams to identify the different events that they might face.
View Source
Event model. This section of the data model describes the modeling of the events inside the HUMAN system. The events stored inside this part of the data model are the low frequency data and commands which are used in the system. Examples of low frequency data are the request for intervention made by the Intervention Manager, the outputs of the Short Term Reasoning Engine and of the Long Term Reasoning Engine when a deviation is detected, updates regarding advancements in the task execution, start / end of a working shift. As a disambiguation note, the modeling of the event is not intended to replicate the Message Schema used to exchange data through the Middleware nor to store all the exchanged data on the middleware. It is important to note that the events that are saved are the low frequency, meaning that data coming from the sensors are not stored in this way.
View Source
Event model. Figure 8 - Events dispatched and consumed by the EventProcessor Interface Note: to ease extensibility, the architecture will manage events in an agnostic way. Specifically, the contents of the events will not be considered as part of the routing task, instead classified will be based purely on TypeId and Version.
View Source
Event model. According to the [MISP data standard], an event is a simple meta structure scheme where attributes and meta-data are embedded to compose a coherent set of indicators. An event can be composed from an incident, a security analysis report or a specific threat actor analysis. The event model is therefore flexible to admit a large variety of fields for supporting security teams to identify the different events that they might face. The meaning of an event only depends of the information embedded in the event. The following sections summarise the data model used in 4SECURAIL. The information about the data model used is detailed at the MISP standard website (▇▇▇▇▇://▇▇▇.▇▇▇▇-▇▇▇▇▇▇▇▇.▇▇▇/). 9.3.1.1 Core of the event
View Source

Related to Event model

  • Additional Features Additional Features are invoiced at the start of the first Contract Year following the Contract Year in which such Additional Features are activated.

  • BUSINESS CONTINUITY/DISASTER RECOVERY In the event of equipment failure, work stoppage, governmental action, communication disruption or other impossibility of performance beyond State Street’s control, State Street shall take reasonable steps to minimize service interruptions. Specifically, State Street shall implement reasonable procedures to prevent the loss of data and to recover from service interruptions caused by equipment failure or other circumstances with resumption of all substantial elements of services in a timeframe sufficient to meet business requirements. State Street shall enter into and shall maintain in effect at all times during the term of this Agreement with appropriate parties one or more agreements making reasonable provision for (i) periodic back-up of the computer files and data with respect to the Trusts; and (ii) emergency use of electronic data processing equipment to provide services under this Agreement. State Street shall test the ability to recover to alternate data processing equipment in accordance with State Street program standards, and provide a high level summary of business continuity test results to the Trusts upon request. State Street will remedy any material deficiencies in accordance with State Street program standards. Upon reasonable advance notice, and at no cost to State Street, the Trusts retain the right to review State Street’s business continuity, crisis management, disaster recovery, and third-party vendor management processes and programs (including discussions with the relevant subject matter experts and an on-site review of the production facilities used) related to delivery of the service no more frequently than an annual basis. Upon reasonable request, the State Street also shall discuss with senior management of the Trusts any business continuity/disaster recovery plan of the State Street and/or provide a high-level presentation summarizing such plan.”

  • Optional Features The Optional Features Prices selected for the Option Aircraft will be adjusted to Boeing's current prices as of the date of execution of the definitive agreement for the Option Aircraft.

  • Alternative Work Schedule An alternate forty (40) hour work schedule (other than five (5) uniform and consecutive eight (8) hour days in a seven (7) day period), or for hospital personnel an eighty (80) hour workweek in a fourteen (14) day period and other mutually agreed upon schedules that comply with applicable federal and state law. Employee work schedules normally include two (2) consecutive days off.

  • Disaster Recovery Plan Contractor agrees that upon request of System Agency, Contractor shall provide copies of its most recent business continuity and disaster recovery plans.