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

  • System Access Control Data processing systems used to provide the Cloud Service must be prevented from being used without authorization. Measures: • Multiple authorization levels are used when granting access to sensitive systems, including those storing and processing Personal Data. Authorizations are managed via defined processes according to the SAP Security Policy • All personnel access SAP’s systems with a unique identifier (user ID). • SAP has procedures in place so that requested authorization changes are implemented only in accordance with the SAP Security Policy (for example, no rights are granted without authorization). In case personnel leaves the company, their access rights are revoked. • SAP has established a password policy that prohibits the sharing of passwords, governs responses to password disclosure, and requires passwords to be changed on a regular basis and default passwords to be altered. Personalized user IDs are assigned for authentication. All passwords must fulfill defined minimum requirements and are stored in encrypted form. In the case of domain passwords, the system forces a password change every six months in compliance with the requirements for complex passwords. Each computer has a password-protected screensaver. • The company network is protected from the public network by firewalls. • SAP uses up–to-date antivirus software at access points to the company network (for e-mail accounts), as well as on all file servers and all workstations. • Security patch management is implemented to provide regular and periodic deployment of relevant security updates. Full remote access to SAP’s corporate network and critical infrastructure is protected by strong authentication.

  • Service Level Agreement Subject to the terms and conditions of this Agreement, Bank agrees to perform the custody services provided for under this Agreement in a manner that meets or exceeds any service levels as may be agreed upon by the parties from time to time in a written document that is executed by both parties on or after the date of this Agreement, unless that written document specifically states that it is not contractually binding. For the avoidance of doubt, Bank’s Service Directory shall not be deemed to be such a written document.

  • Acceptable Use Policy Agreement I understand that I must use school IT systems in a responsible way, to ensure that there is no risk to my safety or to the safety and security of the IT systems and other users. For my own personal safety: • I understand that the school will monitor my use of the IT systems, email and other digital communications. • I will treat my username and password like my toothbrush – I will not share it, nor will I try to use any other person’s username and password. • I will be aware of “stranger danger”, when I am communicating on-line. • I will not disclose or share personal information about myself or others when on-line. • If I arrange to meet people off-line that I have communicated with on-line, I will do so in a public place and take an adult with me. • I will immediately report any unpleasant or inappropriate material or messages or anything that makes me feel uncomfortable when I see it on-line. I understand that everyone has equal rights to use technology as a resource and: • I understand that the school IT systems are primarily intended for educational use and that I will not use the systems for personal or recreational use unless I have permission to do so. • I will not try (unless I have permission) to make large downloads or uploads that might take up internet capacity and prevent other users from being able to carry out their work. • I will not use the school IT systems for on-line gaming, on-line gambling, internet shopping, file sharing, or video broadcasting (e.g. YouTube), unless I have permission of a member of staff to do so. I will act as I expect others to act toward me: • I will respect others’ work and property and will not access, copy, remove or otherwise alter any other user’s files, without the owner’s knowledge and permission. • I will be polite and responsible when I communicate with others, I will not use strong, aggressive or inappropriate language and I appreciate that others may have different opinions. • I will not take or distribute images of anyone without their permission. I recognise that the school has a responsibility to maintain the security and integrity of the technology it offers me and to ensure the smooth running of the school: • I will only use my personal hand held / external devices (mobile phones / USB devices etc) in school if I have permission. I understand that, if I do use my own devices in school, I will follow the rules set out in this agreement, in the same way as if I was using school equipment. • I understand the risks and will not try to upload, download or access any materials which are illegal or inappropriate or may cause harm or distress to others, nor will I try to use any programmes or software that might allow me to bypass the filtering / security systems in place to prevent access to such materials.

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

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