System Agency Data A. As between the Parties, all data and information acquired, accessed, or made available to Grantee by, through, or on behalf of System Agency or System Agency contractors, including all electronic data generated, processed, transmitted, or stored by Grantee in the course of providing data processing services in connection with Xxxxxxx’s performance hereunder (the “System Agency Data”), is owned solely by System Agency.
B. Grantee has no right or license to use, analyze, aggregate, transmit, create derivatives of, copy, disclose, or process the System Agency Data except as required for Grantee to fulfill its obligations under the Grant Agreement or as authorized in advance in writing by System Agency.
C. For the avoidance of doubt, Grantee is expressly prohibited from using, and from permitting any third party to use, System Agency Data for marketing, research, or other non-governmental or commercial purposes, without the prior written consent of System Agency.
D. Grantee shall make System Agency Data available to System Agency, including to System Agency’s designated vendors, as directed in writing by System Agency. The foregoing shall be at no cost to System Agency.
E. Furthermore, the proprietary nature of Xxxxxxx’s systems that process, store, collect, and/or transmit the System Agency Data shall not excuse Xxxxxxx’s performance of its obligations hereunder.
Agency Shop It is mutually agreed by the parties that this Unit is an agency shop Unit. It is the intent of the parties that the agency shop provisions in the Memorandum of Understanding comply with applicable state law (Government Code Section 3502.5).
Receivable Files Complete There exists a Receivable File pertaining to each Receivable. Related documentation concerning the Receivable, including any documentation regarding modifications of the Contract, will be maintained electronically by the Servicer in accordance with customary policies and procedures. With respect to any Receivables that are tangible chattel paper, the complete Receivable File for each Receivable currently is in the possession of the Custodian.
Communications Relating to Portfolio Securities Subject to the provisions of Section 2.3, the Custodian shall transmit promptly to the Fund for each Portfolio all written information (including, without limitation, pendency of calls and maturities of domestic securities and expirations of rights in connection therewith and notices of exercise of call and put options written by the Fund on behalf of the Portfolio and the maturity of futures contracts purchased or sold by the Portfolio) received by the Custodian from issuers of the securities being held for the Portfolio. With respect to tender or exchange offers, the Custodian shall transmit promptly to the Portfolio all written information received by the Custodian from issuers of the securities whose tender or exchange is sought and from the party (or his agents) making the tender or exchange offer. If the Portfolio desires to take action with respect to any tender offer, exchange offer or any other similar transaction, the Portfolio shall notify the Custodian at least three business days prior to the date on which the Custodian is to take such action.
Emergency School Closing 24.1 If as determined by the Superintendent, circumstances of weather, energy crisis, power failure, lack of water or heat, work stoppage, epidemic or other civil or natural emergencies, including threats or acts of violence, make it impossible or unsafe to open the schools or to keep open a school or schools, then the Superintendent shall act in such emergency situations to preserve and protect the lives and property of pupils and staff personnel. Such absence(s) shall not result in loss of pay or accumulated leave days to the teacher.
24.2 When an emergency confronts the schools of Polk County, notification of the closing of the schools shall be released for broadcast over appropriate public media as soon as possible.
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.
Monthly Data Download Not later than fifteen (15) days after the end of each month, beginning with the month in which the Commencement Date occurs and ending with the Final Shared-Loss Recovery Month, Assuming Bank shall provide Receiver:
Agency Disclosure Xxxxxxxx Realty Inc. is functioning the Seller’s Agent. Buyer acknowledges receipt of the “Real Estate Brokerage Relationship” brochure. Buyer agrees to hold Seller harmless from the claim of any person or entity claiming a sales commission or similar right to payment by or through Buyer.
Processing of Deposit files The use of compression is recommended in order to reduce electronic data transfer times, and storage capacity requirements. Data encryption will be used to ensure the privacy of registry escrow data. Files processed for compression and encryption will be in the binary OpenPGP format as per OpenPGP Message Format -‐ RFC 4880, see Part A, Section 9, reference 3 of this Specification. Acceptable algorithms for Public-‐key cryptography, Symmetric-‐key cryptography, Hash and Compression are those enumerated in XXX 0000, not marked as deprecated in OpenPGP IANA Registry, see Part A, Section 9, reference 4 of this Specification, that are also royalty-‐free. The process to follow for the data file in original text format is:
(1) The XML file of the deposit as described in Part A, Section 9, reference 1 of this Specification must be named as the containing file as specified in Section 5 but with the extension xml.
(2) The data file(s) are aggregated in a tarball file named the same as (1) but with extension tar.
(3) A compressed and encrypted OpenPGP Message is created using the tarball file as sole input. The suggested algorithm for compression is ZIP as per XXX 0000. The compressed data will be encrypted using the escrow agent’s public key. The suggested algorithms for Public-‐key encryption are Elgamal and RSA as per XXX 0000. The suggested algorithms for Symmetric-‐key encryption are TripleDES, AES128 and CAST5 as per XXX 0000.
(4) The file may be split as necessary if, once compressed and encrypted, it is larger than the file size limit agreed with the escrow agent. Every part of a split file, or the whole file if not split, will be called a processed file in this section.
(5) A digital signature file will be generated for every processed file using the Registry Operator’s private key. The digital signature file will be in binary OpenPGP format as per RFC 4880 Section 9, reference 3, and will not be compressed or encrypted. The suggested algorithms for Digital signatures are DSA and RSA as per XXX 0000. The suggested algorithm for Hashes in Digital signatures is SHA256.
(6) The processed files and digital signature files will then be transferred to the Escrow Agent through secure electronic mechanisms, such as, SFTP, SCP, HTTPS file upload, etc. as agreed between the Escrow Agent and the Registry Operator. Non-‐electronic delivery through a physical medium such as CD-‐ROMs, DVD-‐ROMs, or USB storage devices may be used if authorized by ICANN.
(7) The Escrow Agent will then validate every (processed) transferred data file using the procedure described in Part A, Section 8 of this Specification.
Signaling Link Transport 9.2.1 Signaling Link Transport is a set of two or four dedicated 56 kbps transmission paths between Global Connection-designated Signaling Points of Interconnection that provide appropriate physical diversity.
