Data Models Related to Monitoring Sample Clauses

Data Models Related to Monitoring. Monitoring events, alarms, and vulnerability scan reports are saved in the document-based database of the Data Warehouse. These documents are constructed by the WISER Agent from the logs originating at the sensors and follow a common format based on the OSSIM11 data format. In the case of vulnerability scan reports, the format is extended to include a specially formed report (described in section 3.1.4) and operation logs of the vulnerability scanners. Information about the status of deployed sensors is stored in the “Sensors” table of the Data Warehouse relational database. Each entry represents a single sensor instance, holding its ID number, type of the sensor, IP address of the sensor’s machine, ID of the organization, times of first and the most recent heartbeat message reception and additional sensor-specific data intended for troubleshooting the sensor’s operation. Heartbeat messages are described in section 5.1.4 debajo de. Data Warehouse matches the heartbeat message to an existing sensor based on its type, organization name, and IP address. If a sensor with the same values is already in the database, its values are updated, otherwise a new sensor object is created. 11 xxxxx://xx.xxxxxxxxx.xxx/wiki/OSSIM 5 Monitoring Communication Protocols The definition of communication protocols is crucial for the information interchange between all the components in the WISER Framework. The communication considered here covers the flow of Events, Vulnerability scan reports, and Heartbeat messages from the Resource Layer towards the Provider Layer. Besides this, Alerts generated by the Monitoring Engine as a result of pre-existing Events are sent from the Monitoring Engine to the Risk Assessment Engine and the Data Warehouse. This section explains the purpose, the flow. and the data format for each of these message types. For an easier understanding of the data streams, Figure 12 can be used as reference.
Sample 1
AutoNDA by SimpleDocs

Related to Data Models Related to Monitoring

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

  • Program Monitoring The Contractor will make all records and documents required under this Agreement as outlined here, in OEC Policies and NHECC Policies available to the SRO or its designee, the SR Fiscal Officer or their designee and the OEC. Scheduled monitoring visits will take place twice a year. The SRO and OEC reserve the right to make unannounced visits.

  • System Monitoring to ensure safe and continuous operation, the Customer must monitor key services and resource use as recommended by Deswik, and provide Deswik with details of monitoring and any relevant alerts as needed. Services to be monitors include, without limitation, disk space, CPU usage, memory usage, database connectivity, and network utilization.

  • EVALUATION AND MONITORING The ORGANIZATION agrees to maintain books, records and other documents and evidence, and to use accounting procedures and practices that sufficiently and properly support the complete performance of and the full compliance with this Agreement. The ORGANIZATION will retain these supporting books, records, documents and other materials for at least three (3) calendar years following the year in which the Agreement expires. The COUNTY and/or the State Auditor and any of their representatives shall have full and complete access to these books, records and other documents and evidence retained by the ORGANIZATION respecting all matters covered in and under this Agreement, and shall have the right to examine such during normal business hours as often as the COUNTY and/or the State Auditor may deem necessary. Such representatives shall be permitted to audit, examine and make excerpts or transcripts from such records, and to make audits of all contracts, invoices, materials, and records of matters covered by this Agreement. These access and examination rights shall last for three calendar years following the year in which the Agreement expires. The COUNTY intends without guarantee for its agents to use reasonable security procedures and protections to assure that related records and documents provided by the ORGANIZATION are not erroneously disclosed to third parties. The COUNTY will, however, disclose or make this material available to those authorized by/in the above paragraph or permitted under the provisions of Chapter 42.56 RCW without notice to the ORGANIZATION. The ORGANIZATION shall cooperate with and freely participate in any other monitoring or evaluation activities pertinent to this Agreement that the COUNTY finds needing to be conducted.

  • Service Monitoring Customer gives express consent for Vodafone to monitor Customer’s use of the Service (and disclose and otherwise use the information obtained) only to: (a) the extent allowed by Applicable Law; (b) comply with Applicable Law; (c) protect the Network from misuse; (d) protect the integrity of the public internet and/or Vodafone’s systems and Networks; (e) the extent necessary to determine if Customer has breached any conditions or restrictions on use of the Service; (f) provide the Service; and/or (g) take other actions agreed or requested by Customer.

  • Access to Network Interface Device (NID 2.4.3.1. Due to the wide variety of NIDs utilized by BellSouth (based on subscriber size and environmental considerations), Mpower may access the on-premises wiring by any of the following means: BellSouth shall allow Mpower to connect its loops directly to BellSouth’s multi-line residential NID enclosures that have additional space and are not used by BellSouth or any other telecommunications carriers to provide service to the premise. Mpower agrees to install compatible protectors and test jacks and to maintain the protection system and equipment and to indemnify BellSouth pursuant to Section 8 of the General Terms and Conditions of this Agreement.

  • Evaluation, Testing, and Monitoring 1. The System Agency may review, test, evaluate and monitor Grantee’s Products and services, as well as associated documentation and technical support for compliance with the Accessibility Standards. Review, testing, evaluation and monitoring may be conducted before and after the award of a contract. Testing and monitoring may include user acceptance testing. Neither the review, testing (including acceptance testing), evaluation or monitoring of any Product or service, nor the absence of review, testing, evaluation or monitoring, will result in a waiver of the State’s right to contest the Grantee’s assertion of compliance with the Accessibility Standards.

  • Program Monitoring and Evaluation (c) The Recipient shall prepare, or cause to be prepared, and furnish to the Association not later than six months after the Closing Date, a report of such scope and in such detail as the Association shall reasonably request, on the execution of the Program, the performance by the Recipient and the Association of their respective obligations under the Legal Agreements and the accomplishment of the purposes of the Financing.”

  • Account Monitoring Merchant acknowledges that Servicer will monitor Merchant’s daily deposit activity. Servicer may upon reasonable grounds suspend disbursement of Merchant's funds for any reasonable period of time required to investigate suspicious or unusual deposit activity. Servicer will make good faith efforts to notify Merchant promptly following suspension. Servicer is not liable to Merchant for any loss, either direct or indirect, which Merchant may attribute to any suspension of funds disbursement.

  • Project Monitoring The Developer shall provide regular status reports to the NYISO in accordance with the monitoring requirements set forth in the Development Schedule, the Public Policy Transmission Planning Process Manual and Attachment Y of the OATT.

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