Security Requirements 7.1 The Authority will review the Contractor’s Security Plan when submitted by the Contractor in accordance with the Schedule (Security Requirements and Plan) and at least annually thereafter.
Data Security Requirements Without limiting Contractor’s obligation of confidentiality as further described in this Contract, Contractor must establish, maintain, and enforce a data privacy program and an information and cyber security program, including safety, physical, and technical security and resiliency policies and procedures, that comply with the requirements set forth in this Contract and, to the extent such programs are consistent with and not less protective than the requirements set forth in this Contract and are at least equal to applicable best industry practices and standards (NIST 800-53).
Facility Requirements 1. Maintain wheelchair accessibility to program activities according to governing law, including the Americans With Disabilities Act (ADA), as applicable.
2. Provide service site(s) that will promote attainment of Contractor’s program objectives. Arrange the physical environment to support those activities.
3. Decrease program costs when possible by procuring items at no cost from County surplus stores and by accepting delivery of such items by County.
CREDIT AND COLLATERAL REQUIREMENTS The applicable credit and collateral requirements are specified on the Cover Sheet.
CONDITIONS TO LOANS AND LETTERS OF CREDIT The obligations of Lenders to make Loans and the issuance of Letters of Credit hereunder are subject to the satisfaction of the following conditions.
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 Precedent to Loans and Letters of Credit 32 Section 3.1 Conditions To Effectiveness.................................................32 Section 3.2 Each Credit Event...........................................................33 Section 3.3 Delivery of Documents.......................................................34
CONDITIONS OF LENDING AND ISSUANCE OF LETTERS OF CREDIT The obligation of each Lender to make Loans and of the Issuing Lender to issue Letters of Credit hereunder is subject to the performance by each of the Loan Parties of its Obligations to be performed hereunder at or prior to the making of any such Loans or issuance of such Letters of Credit and to the satisfaction of the following further conditions:
Documentation Requirements ODM shall pay the MCP after it receives sufficient documentation, as determined by ODM, detailing the MCP’s Ohio Medicaid-specific liability for the Annual Fee. The MCP shall provide documentation that includes the following:
1. Total premiums reported on IRS Form 8963;
Conditions to Letters of Credit The issuance of any Letter of Credit hereunder (whether or not the applicable Issuing Lender is obligated to issue such Letter of Credit) is subject to the following conditions precedent:
A. On or before the date of issuance of the initial Letter of Credit pursuant to this Agreement, the initial Loans shall have been made.
B. On or before the date of issuance of such Letter of Credit, Administrative Agent shall have received, in accordance with the provisions of subsection 3.1B(i), an originally executed Notice of Issuance of Letter of Credit, in each case signed by the chief executive officer, the chief financial officer or the treasurer of Company or by any executive officer of Company designated by any of the above-described officers on behalf of Company in a writing delivered to Administrative Agent, together with all other information specified in subsection 3.1B(i) and such other documents or information as the applicable Issuing Lender may reasonably require in connection with the issuance of such Letter of Credit.
C. On the date of issuance of such Letter of Credit, all conditions precedent described in subsection 4.2B shall be satisfied to the same extent as if the issuance of such Letter of Credit were the making of a Loan and the date of issuance of such Letter of Credit were a Funding Date.
