System Access Agreement Sample Clauses

System Access Agreement. I understand that I am given access to the interoperable system(s) and IPAWS-OPEN to perform my official duties. • I will not attempt to access data, information or applications I am not authorized to access nor bypass access control measures. • I will not provide or knowingly allow other individuals to use my account credentials to access the interoperable system(s) and IPAWS-OPEN. • To prevent and deter others from gaining unauthorized access to sensitive resources, I will log off or lock my computer workstation or will use a password-protected screensaver whenever I step away from my work area, even for a short time and I will log off when I leave for the day. • To prevent others from obtaining my password via “shoulder surfing”, I will shield my keyboard from view as I enter my password. • I will not engage in, encourage, or conceal any hacking or cracking, denial of service, unauthorized tampering, or unauthorized attempted use of (or deliberate disruption of) any data or component within the interoperable system(s) and IPAWS-OPEN. • I agree to inform my Local System Administrator when access to the interoperable system(s) and/or IPAWS- OPEN is no longer required. • I agree that I have completed Computer Security Awareness training prior to my initial access to the interoperable system(s) and IPAWS-OPEN and that as long as I have continued access, I will complete Computer Security Awareness training on an annual basis.
AutoNDA by SimpleDocs
System Access Agreement. I understand that I am given access to the interoperable system(s) and IPAWS-OPEN to perform my official duties. I will not attempt to access data, information or applications I am not authorized to access nor bypass access control measures. I will not provide or knowingly allow other individuals to use my account credentials to access the interoperable system(s) and IPAWS-OPEN. To prevent and deter others from gaining unauthorized access to sensitive resources, I will log off or lock my computer workstation or will use a password-protected screensaver whenever I step away from my work area, even for a short time and I will log off when I leave for the day. as I enter my password. I will not engage in, encourage, or conceal any hacking or cracking, denial of service, unauthorized tampering, or unauthorized attempted use of (or deliberate disruption of) any data or component within the interoperable system(s) and IPAWS-OPEN. IPAWS-OPEN is no longer required. I agree that I have completed Computer Security Awareness training as may be required by my jurisdiction prior to my initial access to the interoperable system(s) and IPAWS-OPEN and that as long as I have continued access, I will complete Computer Security Awareness training on an annual basis. If my jurisdiction does not provide Computer Security Awareness training, I will complete the FEMA self-study course IS-906: Workplace Security Awareness (xxxxx://xxxxxxxx.xxxx.xxx/is/courseoverview.aspx?code=IS- 906) on an annual basis.

Related to System Access Agreement

  • Zone File Access Agreement Registry Operator will enter into an agreement with any Internet user, which will allow such user to access an Internet host server or servers designated by Registry Operator and download zone file data. The agreement will be standardized, facilitated and administered by a Centralized Zone Data Access Provider, which may be ICANN or an ICANN designee (the “CZDA Provider”). Registry Operator (optionally through the CZDA Provider) will provide access to zone file data per Section 2.1.3 of this Specification and do so using the file format described in Section 2.1.4 of this Specification. Notwithstanding the foregoing, (a) the CZDA Provider may reject the request for access of any user that does not satisfy the credentialing requirements in Section 2.1.2 below; (b) Registry Operator may reject the request for access of any user that does not provide correct or legitimate credentials under Section 2.1.2 below or where Registry Operator reasonably believes will violate the terms of Section 2.1.5. below; and, (c) Registry Operator may revoke access of any user if Registry Operator has evidence to support that the user has violated the terms of Section 2.1.5 below.

  • Collateral Access Agreements Such Grantor shall use commercially reasonable efforts to obtain a Collateral Access Agreement, from the lessor of each leased property, mortgagee of owned property or bailee or consignee with respect to the operator of any warehouse, processor or converter facility or other location (each of which is identified on Exhibit B hereto), where Collateral in excess of $1,000,000 is stored or located at any given time (other than (i) company-owned facilities and (ii) retail stores), which agreement or letter shall provide access rights, contain a waiver or subordination of all Liens or claims that the landlord, mortgagee, bailee or consignee may assert against the Collateral at that location, and shall otherwise be reasonably satisfactory in form and substance to the Administrative Agent. With respect to such locations or warehouse space leased as of the Effective Date and thereafter where Collateral in excess of $1,000,000 is stored or located (other than (i) company-owned facilities and (ii) retail stores), if the Administrative Agent has not received a Collateral Access Agreement as of the Effective Date (or, if later as of the date such location is acquired or leased), the Borrower’s Eligible Inventory at that location shall be subject to such Reserves as may be established by the Administrative Agent. After the Effective Date, no real property or warehouse space shall be leased by such Grantor (other than retail stores) and no Inventory shall be shipped to a processor or converter under arrangements established after the Effective Date, unless and until a satisfactory Collateral Access Agreement shall first have been obtained with respect to such location or if it has not been obtained, the Borrower’s Eligible Inventory at that location shall be subject to the establishment of Reserves acceptable to the Administrative Agent. Such Grantor shall timely and fully pay and perform its obligations under all leases and other agreements with respect to each leased location or third party warehouse where any Collateral is or may be located.

  • System Access Control Data processing systems used to provide the Cloud Service must be prevented from being used without authorization.

  • System Access CUSTOMER agrees to provide to PROVIDER, at CUSTOMER’S expense, necessary access to the mainframe computer and related information technology systems (the “System”) on which CUSTOMER data is processed during the times (the “Service Hours”) specified in the PSAs, subject to reasonable downtime for utility outages, maintenance, performance difficulties and the like. In the event of a change in the Service Hours, CUSTOMER will provide PROVIDER with at least fifteen (15) calendar days written notice of such change.

  • Service Level Agreement 6.1 NCR Voyix will use commercially reasonable efforts to make the Service available to you at or above the Availability Rate set forth at xxxxx://xxx.xxx.xxx/support/aloha-sla. If NCR Voyix does not meet the Availability Rate, you are entitled to request a service-level credit subject to the terms of this Agreement. This credit is calculated as a percentage of the monthly recurring bill (or monthly pro rata share of billing, if billing does not occur monthly) for the Service for the month in which the Availability Rate was not met. The Availability Rate is determined by: (a) dividing the total number of valid outage minutes in a calendar month by the total number of minutes in that month; (b) subtracting that quotient from 1.00; (c) multiplying that difference by 100; and (d) rounding that result to two decimal places in accordance with standard rounding conventions. The number of outage minutes per day for a given service is determined by the lesser of the number of outage minutes. 6.2 Unavailability due to other conditions or caused by factors outside of NCR Voyix’s reasonable control will not be included in the calculation of the Availability Rate. Further, the following are expressly excluded from the calculation of the Availability Rate: (a) service unavailability affecting services or application program interfaces that are not used by you; (b) cases where fail-over to another data center is available but not utilized; (c) transient time-outs, required re-tries, or slower-than-normal response caused by factors outside of NCR Voyix’s reasonable control; (d) Scheduled Downtime, including maintenance and upgrades; (e) force majeure; (f) transmission or communications outages outside the NCR Voyix- controlled environment; (g) store-level down-time caused by factors outside of NCR Voyix’s reasonable control; (h) outages attributable to services, hardware, or software not provided by NCR Voyix, including, but not limited to, issues resulting from inadequate bandwidth or related to third-party software or services; (i) use of the Service in a manner inconsistent with the documentation for the application program interface or the NCR Voyix Product; (j) your Point of Sale (“POS”) failure or the failure to properly maintain the POS environment, including updating the POS firmware or version of the software running on the POS as recommended by either NCR Voyix, a third-party POS reseller or servicer; and (k) issues related to third party domain name system (“DNS”) errors or failures. 6.3 To obtain a service-level credit, you must submit a claim by contacting NCR Voyix through the website at xxxxx://xxx.xxx.xxx/support/aloha-sla Your failure to provide the claim and other information will disqualify you from receiving a credit. NCR Voyix must receive claims within 60 days from the last day of the impacted month. After that date, claims are considered waived and will be refused. You must be in compliance with the Agreement in order to be eligible for a service-level credit. You may not unilaterally offset for any performance or availability issues any amount owed to NCR Voyix. If multiple Services experience an outage in a given month, the total credit for that month will be the highest credit allowed for any single Service which failed; there is no stacking of credits. 6.4 The remedies set forth in the Section are your sole and exclusive remedies for performance or availability issues affecting the Services, including any failure by NCR Voyix to achieve the Availability Rate.

  • Network Access Control The VISION Web Site and the Distribution Support Services Web Site (the “DST Web Sites”) are protected through multiple levels of network controls. The first defense is a border router which exists at the boundary between the DST Web Sites and the Internet Service Provider. The border router provides basic protections including anti-spoofing controls. Next is a highly available pair of stateful firewalls that allow only HTTPS traffic destined to the DST Web Sites. The third network control is a highly available pair of load balancers that terminate the HTTPS connections and then forward the traffic on to one of several available web servers. In addition, a second highly available pair of stateful firewalls enforce network controls between the web servers and any back-end application servers. No Internet traffic is allowed directly to the back-end application servers. The DST Web Sites equipment is located and administered at DST’s Winchester data center. Changes to the systems residing on this computer are submitted through the DST change control process. All services and functions within the DST Web Sites are deactivated with the exception of services and functions which support the transfer of files. All ports on the DST Web Sites are disabled, except those ports required to transfer files. All “listeners,” other than listeners required for inbound connections from the load balancers, are deactivated. Directory structures are “hidden” from the user. Services which provide directory information are also deactivated.

  • Service Level Agreements If a Service or a Plan includes a Service Level Agreement (SLA): (a) we are liable for any remedy or rebate specified by the SLA; and (b) subject to clauses 40 to 42, and to the express terms of the SLA, our liability for breach of the SLA is limited to such remedy or rebate.

  • System Upgrade Facilities and System Deliverability Upgrades Connecting Transmission Owner shall design, procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Appendix A hereto. The responsibility of the Developer for costs related to System Upgrade Facilities and System Deliverability Upgrades shall be determined in accordance with the provisions of Attachment S to the NYISO OATT.

  • Data Access Control Persons entitled to use data processing systems gain access only to the Personal Data that they have a right to access, and Personal Data must not be read, copied, modified or removed without authorization in the course of processing, use and storage.

  • Changes to Privacy Policy Agreement Passive Plus, Inc. reserves the right to update and/or change the terms of our privacy policy, and as such we will post those change to our website homepage at xxx.xxxxxxxxxxx.xxx, so that our users and/or visitors are always aware of the type of information we collect, how it will be used, and under what circumstances, if any, we may disclose such information. If at any point in time Passive Plus, Inc. decides to make use of any personally identifiable information on file, in a manner vastly different from that which was stated when this information was initially collected, the user or users shall be promptly notified by email. Users at that time shall have the option as to whether or not to permit the use of their information in this separate manner.

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