Estimating consequence parameters Sample Clauses

Estimating consequence parameters. To exemplify the proposed procedure, we consider 10 types of cyber attacks identified in Deliverable D3.1. Table 13 lists the loss types involved in each attack. For example, a Denial of Service attack is assumed to involve the following loss types: Business interruption, Contractual penalties, Reputational damage, Crisis handling, Third party damages and Legal costs. Section 11.1.1 indicates the procedure to quantify each type of loss, by interviews with the company’s management and internal experts. Assuming that the cost for each loss type have been quantified, for each attack type we proceed as follows:  the worst case impact is obtained as the sum of the impacts quantified for the loss types involved in the attack as per Table 13;  the typical case impact is obtained either by historical loss data recorded by the Company, or by publicly available datasets and surveys. Loss type Denial of Service Invalidated redirects and forwards Bypass login by brute force or DNS Compromise security via Trojan- malware Client-server protocol manipulation Session hijacking Cross site request forgery SQL injection Buffer overflow Relative path traversal Loss revenues X X X X X X X Costs for notification to authority X X X X X X X X X Legal costs X X X X X X X X X X Third Party damages X X X X X X X X X Digital assets disruption X Data recovery costs X X X X X X X X Infrastructure recovery costs X X X X X Costs for informatics experts X X X X X X X X X Losses from multimedia activities X Contractual penalties X X X X X X X X X X PCI-DSS costs X X X X X X X X X Fines from regulatory authority X X X X X X X X X Reputational damage X X X X X X Crisis handling costs X X X X X Extortion X Fines for privacy breach X X X X X X X X X Table 13. Main types of cyber attacks (column labels) and corresponding loss types triggered by each attack (row labels).
AutoNDA by SimpleDocs

Related to Estimating consequence parameters

  • CONTRACT CONSEQUENCES In the case of a state contractor, contributions made or solicited in violation of the above prohibitions may result in the contract being voided. In the case of a prospective state contractor, contributions made or solicited in violation of the above prohibitions shall result in the contract described in the state contract solicitation not being awarded to the prospective state contractor, unless the State Elections Enforcement Commission determines that mitigating circumstances exist concerning such violation. The State shall not award any other state contract to anyone found in violation of the above prohibitions for a period of one year after the election for which such contribution is made or solicited, unless the State Elections Enforcement Commission determines that mitigating circumstances exist concerning such violation. Additional information may be found on the website of the State Elections Enforcement Commission, xxx.xx.xxx/xxxx. Click on the link to “Lobbyist/Contractor Limitations.”

  • Financial Consequences The Department reserves the right to impose financial consequences when the Contractor fails to comply with the requirements of the Contract. The following financial consequences will apply for the Contractor’s non-performance under the Contract. The Customer and the Contractor may agree to add additional Financial Consequences on an as-needed basis beyond those stated herein to apply to that Customer’s resultant contract or purchase order. The State of Florida reserves the right to withhold payment or implement other appropriate remedies, such as Contract termination or nonrenewal, when the Contractor has failed to comply with the provisions of the Contract. The Contractor and the Department agree that financial consequences for non-performance are an estimate of damages which are difficult to ascertain and are not penalties. The financial consequences below will be paid and received by the Department of Management Services within 30 calendar days from the due date specified by the Department. These financial consequences below are individually assessed for failures over each target period beginning with the first full month or quarter of the Contract performance and every month or quarter, respectively, thereafter. Deliverable Performance Metric Performance Due Date Financial Consequence for Non-Performance Contractor will timely submit completed Quarterly Sales Reports All Quarterly Sales Reports will be submitted timely with the required information Reports are due on or before the 30th calendar day after the close of each State fiscal quarter $250 per Calendar Day late/not received by the Contract Manager Contractor will timely submit completed MFMP Transaction Fee Reports All MFMP Transaction Fee Reports will be submitted timely with the required information Reports are due on or before the 15th calendar day after the close of each month $100 per Calendar Day late/not received by the Contract Manager Failure to timely provide Quarterly Sales Reports, transaction fee reports, or other reports as required will result in the imposition of financial consequences and repeated failures or non- payment of financial consequences owed under this Contract may result in the Contractor being found in default and the termination of the Contract. No favorable action will be considered when Contractor has outstanding Contract Quarterly Sales Reports, MFMP Transaction Fee Reports, or any other documentation owed to the Department or Customer, to include fees / monies, that is required under this Contract.

  • Acceptable Estimating System The Contractor shall maintain the acceptable status of their Estimating System and submit updates to the current status, if applicable

  • Opinion of Probable Cost Any opinions of probable Project cost or probable construction cost provided by Engineer are made on the basis of information available to Engineer and on the basis of Engineer’s experience and qualifications and represents its judgment as an experienced and qualified professional engineer. However, since Engineer has no control over the cost of labor, materials, equipment or services furnished by others, or over the contractor(s’) methods of determining prices, or over competitive bidding or market conditions, Engineer does not guarantee that proposals, bids or actual Project or construction cost will not vary from opinions of probable cost Engineer prepares.

  • Initial Forecasts/Trunking Requirements Because Verizon’s trunking requirements will, at least during an initial period, be dependent on the Customer segments and service segments within Customer segments to whom CSTC decides to market its services, Verizon will be largely dependent on CSTC to provide accurate trunk forecasts for both inbound (from Verizon) and outbound (to Verizon) traffic. Verizon will, as an initial matter, provide the same number of trunks to terminate Reciprocal Compensation Traffic to CSTC as CSTC provides to terminate Reciprocal Compensation Traffic to Verizon. At Verizon’s discretion, when CSTC expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, Verizon will provide the number of trunks CSTC suggests; provided, however, that in all cases Verizon’s provision of the forecasted number of trunks to CSTC is conditioned on the following: that such forecast is based on reasonable engineering criteria, there are no capacity constraints, and CSTC’s previous forecasts have proven to be reliable and accurate.

  • ADDITIONAL SPECIAL CONTRACT CONDITIONS A. Special Contract Conditions revisions: the corresponding subsections of the Special Contract Conditions referenced below are replaced in their entirety with the following:

  • Estimating (2) Marketing and sales:

  • Measuring EPP parameters Every 5 minutes, EPP probes will select one “IP address” of the EPP servers of the TLD being monitored and make an “EPP test”; every time they should alternate between the 3 different types of commands and between the commands inside each category. If an “EPP test” result is undefined/unanswered, the EPP service will be considered as unavailable from that probe until it is time to make a new test.

  • Trunk Forecasting Requirements 14.2.1 Initial trunk forecast requirements. At least ninety (90) days before initiating interconnection in a LATA, Alltel shall provide Verizon a two (2)-year traffic forecast that complies with the Verizon Interconnection Trunking Forecast Guide, as revised from time to time. This initial traffic forecast will provide the amount of traffic to be delivered to and from Verizon over each of the Interconnection Trunk groups in the LATA over the next eight (8) quarters.

  • Agreement Exceptions/Deviations Explanation If the proposing Vendor desires to deviate form the Vendor Agreement language, all such deviations must be listed on this attribute, with complete and detailed conditions and information included. TIPS will consider any deviations in its proposal award decisions, and TIPS reserves the right to accept or reject any proposal based upon any deviations indicated below. In the absence of any deviation entry on this attribute, the proposer assures TIPS of their full compliance with the Vendor Agreement. No response

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