Availability and Resilience Measures Sample Clauses

Availability and Resilience Measures. Measures to ensure that personal data are protected against accidental or wilful destruction or loss and can be recovered quickly after an incident. We run daily database backups that are also stored on AWS. Additionally, we also create backups of each application build that we deploy, for both our servers and our clients. This enables us to rapidly rollback a database, server or client application, should an incidence occur. AWS deploys uninterruptible power supplies (see here: xxxxx://x0.xxxxxxxxx.xxx/whitepapers/aws-security-whitepaper.pdf).
AutoNDA by SimpleDocs

Related to Availability and Resilience Measures

  • EPP service availability Refers to the ability of the TLD EPP servers as a group, to respond to commands from the Registry accredited Registrars, who already have credentials to the servers. The response shall include appropriate data from the Registry System. An EPP command with “EPP command RTT” 5 times higher than the corresponding SLR will be considered as unanswered. If 51% or more of the EPP testing probes see the EPP service as unavailable during a given time, the EPP service will be considered unavailable.

  • Interim Measures 6.1 The Parties acknowledge that the British Columbia Claims Task Force made the following recommendation concerning Interim Measures:

  • Service Availability You understand that Service availability is at all times conditioned upon the corresponding operation and availability of the communication systems used in communicating your instructions and requests to the Credit Union. We will not be liable or have any responsibility of any kind for any loss or damage thereby incurred by you in the event of any failure or interruption of such communication systems or services resulting from the act or omission of any third party, or from any other cause not reasonably within the control of the Credit Union.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • Safety Measures Awarded vendor shall take all reasonable precautions for the safety of employees on the worksite, and shall erect and properly maintain all necessary safeguards for protection of workers and the public. Awarded vendor shall post warning signs against all hazards created by the operation and work in progress. Proper precautions shall be taken pursuant to state law and standard practices to protect workers, general public and existing structures from injury or damage.

  • Protective Measures We have implemented and will maintain appropriate technical and organisational measures in relation to the Services taking into account the state of the art, the costs of implementation, and the nature, scope, context and purposes of Processing, as well as the likelihood and severity of risk to the rights and freedoms of data subjects. This includes measures relating to the physical security of Our facilities used to deliver them, measures to control access rights to Our assets and relevant networks, and processes for testing these measures. In accordance with Our obligations under applicable law, We may undertake digital forensic investigations in relation to the use of the Services and Subscriptions. You are responsible for using, and ensuring that your Users use, the controls and advice provided by the Services correctly and consistently.

  • 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.

  • High Availability Registry Operator will conduct its operations using network and geographically diverse, redundant servers (including network-­‐level redundancy, end-­‐node level redundancy and the implementation of a load balancing scheme where applicable) to ensure continued operation in the case of technical failure (widespread or local), or an extraordinary occurrence or circumstance beyond the control of the Registry Operator. Registry Operator’s emergency operations department shall be available at all times to respond to extraordinary occurrences.

  • General Availability The commitment to availability specified in the letter of appointment shall be subject to mutually acceptable revision. Such revision will occur once per year, or, if mutually agreed between the Employer and the employee, on a more frequent basis. The Employer will issue a revised letter of appointment to reflect approved changes to employee’s general availability.

  • DNS service availability Refers to the ability of the group of listed-­‐as-­‐authoritative name servers of a particular domain name (e.g., a TLD), to answer DNS queries from DNS probes. For the service to be considered available at a particular moment, at least, two of the delegated name servers registered in the DNS must have successful results from “DNS tests” to each of their public-­‐DNS registered “IP addresses” to which the name server resolves. If 51% or more of the DNS testing probes see the service as unavailable during a given time, the DNS service will be considered unavailable.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!