No Reliance on Administrative Agent’s Customer Identification Program Each Lender acknowledges and agrees that neither such Lender, nor any of its Affiliates, participants or assignees, may rely on the Administrative Agent to carry out such Lender’s, Affiliate’s, participant’s or assignee’s customer identification program, or other obligations required or imposed under or pursuant to the USA Patriot Act or the regulations thereunder, including the regulations contained in 31 CFR 103.121 (as hereafter amended or replaced, the “CIP Regulations”), or any other Anti-Terrorism Law, including any programs involving any of the following items relating to or in connection with any of the Loan Parties, their Affiliates or their agents, the Loan Documents or the transactions hereunder or contemplated hereby: (i) any identity verification procedures, (ii) any recordkeeping, (iii) comparisons with government lists, (iv) customer notices or (v) other procedures required under the CIP Regulations or such other Laws.
Know Your Customer Requirements (a) The Owner must promptly on the request of any Finance Party supply to that Finance Party any documentation or other evidence which is reasonably requested by that Finance Party (whether for itself, on behalf of any Finance Party or any prospective new Lender) to enable a Finance Party or prospective new Lender to carry out and be satisfied with the results of all applicable know your customer requirements.
(b) Each Lender must promptly on the request of the Facility Agent supply to the Facility Agent any documentation or other evidence which is reasonably required by the Facility Agent to carry out and be satisfied with the results of all know your customer requirements.
No Reliance on Agent’s Customer Identification Program Each Lender acknowledges and agrees that neither such Lender, nor any of its Affiliates, participants or assignees, may rely on the Agent to carry out such Lender’s, Affiliate’s, participant’s or assignee’s customer identification program, or other obligations required or imposed under or pursuant to the USA PATRIOT Act or the regulations thereunder, including the regulations contained in 31 CFR 103.121 (as hereafter amended or replaced, the “CIP Regulations”), or any other Anti-Terrorism Law, including any programs involving any of the following items relating to or in connection with any Borrower, its Affiliates or its agents, this Agreement, the Other Documents or the transactions hereunder or contemplated hereby: (1) any identity verification procedures, (2) any record-keeping, (3) comparisons with government lists, (4) customer notices or (5) other procedures required under the CIP Regulations or such other laws.
Subsidy Requests and Reporting Requirements 1. The Grantee or Management Company shall complete a CRF Subsidy Request Report - Recap of Tenant Income Certification, which provides a unit-by-unit listing of all units in the Development for whom assistance is being requested and gives detailed information including the occupants’ eligibility, set-aside requirements, amount of household rent paid, utility allowance and amount of CRF Rental Subsidy requested.
2. The CRF Subsidy Request Report - Recap of Tenant Income Certification shall be prepared as of the last day of each calendar month during the period of performance and shall be submitted to XXXXxxxxxxxx@XxxxxxxXxxxxxx.xxx and Florida Housing’s monitoring agent no later than the 15th day of the following month. The December 2020 request will be due on or before December 15th. The Grantee will submit executed Coronavirus Relief Fund Rental Assistance Applications and supporting documentation to Florida Housing’s monitoring agent within 5 days upon the monitoring agent’s request.
Federal Medicaid System Security Requirements Compliance Party shall provide a security plan, risk assessment, and security controls review document within three months of the start date of this Agreement (and update it annually thereafter) in order to support audit compliance with 45 CFR 95.621 subpart F, ADP System Security Requirements and Review Process.
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.
FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-‐xxxxxx-‐icann-‐registry-‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).
Reporting Requirements of the Commission The Trustee and the Master Servicer shall reasonably cooperate with the Depositor and its counsel to enter into such amendments or modifications to this Agreement as may be necessary to comply with the Rules and any interpretations thereof by the staff of the Commission, subject to the provisions of Section 11.03 hereof.
Requirements of Insurance All such insurance shall (i) provide that no cancellation, material reduction in amount or material change in coverage thereof shall be effective until at least 10 days (or, to the extent reasonably available, 30 days) after receipt by the Collateral Agent of written notice thereof (the Borrower shall deliver a copy of the policy (and to the extent any such policy is cancelled or renewed, a renewal or replacement policy) or other evidence thereof to the Administrative Agent and the Collateral Agent, or insurance certificate with respect thereto) and (ii) name the Collateral Agent as loss payee (in the case of property insurance) or additional insured on behalf of the Secured Parties (in the case of liability insurance) (it being understood that, absent an Event of Default, any proceeds of any such property insurance shall be delivered by the insurer(s) to the Borrower or one of its Subsidiaries and applied in accordance with this Agreement), as applicable.
Know Your Customer Information The Administrative Agent shall have received at least three Business Days prior to the Closing Date all documentation and other information about the Borrower as has been reasonably requested by the Administrative Agent at least 10 Business Days prior to the Closing Date that is required by regulatory authorities under applicable “know your customer” and anti-money laundering rules and regulations, including without limitation the USA PATRIOT Act.
