Obligations of Verizon and Requirements of the Wireless Network Before Construction Clause Samples
Obligations of Verizon and Requirements of the Wireless Network Before Construction
Personnel Requirements and Documentation Grantee will; 1. maintain current personnel documentation on each employee. All documents must be factual and accurate. Health-related information must be stored separately with restricted access as appropriate under Tex. Gov. Code §552.102. Training records may be stored separately from the main personnel file but must be easily accessible upon request. Required documentation includes the following, as applicable: i. A copy of the current job description signed by the employee; ii. Application or resume with documentation of required qualifications and verification of required credentials; iii. Verification of work experience; iv. Annual performance evaluations; v. Personnel data that includes date hired, rate of pay, and documentation of all pay increases and bonuses; vi. Documentation of appropriate screening and/or background checks, to include probation or parole documentation; vii. Signed documentation of initial and other required training; and viii. Records of any disciplinary actions. 2. document authentication must include signature, credentials when applicable, and date. If the document relates to past activity, the date of the activity must also be recorded. Documentation must be permanent and legible. When it is necessary to correct a required document, the error must be marked through with a single line, dated, and initialed by the writer.
Notifications of Outages and Maintenance In the event that a Registry Operator plans maintenance, it will provide notice to the ICANN emergency operations department, at least, twenty-‐four (24) hours ahead of that maintenance. ICANN’s emergency operations department will note planned maintenance times, and suspend Emergency Escalation services for the monitored services during the expected maintenance outage period. If Registry Operator declares an outage, as per its contractual obligations with ICANN, on services under a service level agreement and performance requirements, it will notify the ICANN emergency operations department. During that declared outage, ICANN’s emergency operations department will note and suspend emergency escalation services for the monitored services involved.
New Hampshire Specific Data Security Requirements The Provider agrees to the following privacy and security standards from “the Minimum Standards for Privacy and Security of Student and Employee Data” from the New Hampshire Department of Education. Specifically, the Provider agrees to: (1) Limit system access to the types of transactions and functions that authorized users, such as students, parents, and LEA are permitted to execute; (2) Limit unsuccessful logon attempts; (3) Employ cryptographic mechanisms to protect the confidentiality of remote access sessions; (4) Authorize wireless access prior to allowing such connections; (5) Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity; (6) Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions; (7) Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles; (8) Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services; (9) Enforce a minimum password complexity and change of characters when new passwords are created; (10) Perform maintenance on organizational systems; (11) Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance; (12) Ensure equipment removed for off-site maintenance is sanitized of any Student Data in accordance with NIST SP 800-88 Revision 1; (13) Protect (i.e., physically control and securely store) system media containing Student Data, both paper and digital; (14) Sanitize or destroy system media containing Student Data in accordance with NIST SP 800-88 Revision 1 before disposal or release for reuse; (15) Control access to media containing Student Data and maintain accountability for media during transport outside of controlled areas; (16) Periodically assess the security controls in organizational systems to determine if the controls are effective in their application and develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems; (17) Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems; (18) Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception); (19) Protect the confidentiality of Student Data at rest; (20) Identify, report, and correct system flaws in a timely manner; (21) Provide protection from malicious code (i.e. Antivirus and Antimalware) at designated locations within organizational systems; (22) Monitor system security alerts and advisories and take action in response; and (23) Update malicious code protection mechanisms when new releases are available.
Conditions of Eft Services (a.) Ownership of Card(s). Any Card we supply to you is our property and must be returned to us, or to any person whom we authorize to act as our agent, or to any person who is authorized to honor the Card, immediately according to instructions. The Card may be reclaimed at any time at our sole discretion without demand or notice. You cannot transfer your Card to another person.
Compliance with Consensus Policies and Temporary Policies Registry Operator shall comply with and implement all Consensus Policies and Temporary Policies found at <▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇/general/consensus-‐policies.htm>, as of the Effective Date and as may in the future be developed and adopted in accordance with the ICANN Bylaws, provided such future Consensus Polices and Temporary Policies are adopted in accordance with the procedure and relate to those topics and subject to those limitations set forth in Specification 1 attached hereto (“Specification 1”).