Contact in Event of Unauthorized Transfer If you believe your Card and/or access code has been lost or stolen or that someone has transferred or may transfer money from your account without your permission, either call us immediately at:
Please see the current Washtenaw Community College catalog for up-to-date program requirements Conditions & Requirements
File Management and Record Retention relating to CRF Eligible Persons or Households Grantee must maintain a separate file for every applicant, Eligible Person, or Household, regardless of whether the request was approved or denied.
a. Contents of File: Each file must contain sufficient and legible documentation. Documents must be secured within the file and must be organized systematically.
Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-‐to-‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.
Incident Event and Communications Management a. Incident Management/Notification of Breach - DST shall develop, implement and maintain an incident response plan that specifies actions to be taken when DST or one of its subcontractors suspects or detects that a party has gained material unauthorized access to Fund Data or systems or applications containing any Fund Data (the “Response Plan”). Such Response Plan shall include the following:
i. Escalation Procedures - An escalation procedure that includes notification to senior managers and appropriate reporting to regulatory and law enforcement agencies. This procedure shall provide for reporting of incidents that compromise the confidentiality of Fund Data (including backed up data) to Fund via telephone or email (and provide a confirmatory notice in writing as soon as practicable); provided that the foregoing notice obligation is excused for such period of time as DST is prohibited by law, rule, regulation or other governmental authority from notifying Fund.
ii. Incident Reporting - DST will use commercially reasonable efforts to promptly furnish to Fund information that DST has regarding the general circumstances and extent of such unauthorized access to the Fund Data.
Xxxxxxxx Tobacco Co [Xxxxx Progeny] Circuit Court, Levy County, (Bronson, FL) $8 million in compensatory damages; 90% of fault assigned to RJR Tobacco, which reduced the award to $7.2 million; $72 million in punitive damages. See “— Xxxxx and Xxxxx Progeny Cases” below.
TECHNOLOGY/KNOWLEDGE TRANSFER ACTIVITIES The goal of this task is to develop a plan to make the knowledge gained, experimental results, and lessons learned available to the public and key decision makers. • Prepare an Initial Fact Sheet at start of the project that describes the project. Use the format provided by the CAM. • Prepare a Final Project Fact Sheet at the project’s conclusion that discusses results. Use the format provided by the CAM. • Prepare a Technology/Knowledge Transfer Plan that includes: o An explanation of how the knowledge gained from the project will be made available to the public, including the targeted market sector and potential outreach to end users, utilities, regulatory agencies, and others.
o A description of the intended use(s) for and users of the project results. o Published documents, including date, title, and periodical name. o Copies of documents, fact sheets, journal articles, press releases, and other documents prepared for public dissemination. These documents must include the Legal Notice required in the terms and conditions. Indicate where and when the documents were disseminated. o A discussion of policy development. State if project has been or will be cited in government policy publications, or used to inform regulatory bodies. o The number of website downloads or public requests for project results. o Additional areas as determined by the CAM. • Conduct technology transfer activities in accordance with the Technology/Knowledge Transfer Plan. These activities will be reported in the Progress Reports. • When directed by the CAM, develop Presentation Materials for an Energy Commission- sponsored conference/workshop(s) on the project. • When directed by the CAM, participate in annual EPIC symposium(s) sponsored by the California Energy Commission. • Provide at least (6) six High Quality Digital Photographs (minimum resolution of 1300x500 pixels in landscape ratio) of pre and post technology installation at the project sites or related project photographs. • Prepare a Technology/Knowledge Transfer Report on technology transfer activities conducted during the project. • Initial Fact Sheet (draft and final) • Final Project Fact Sheet (draft and final) • Presentation Materials (draft and final) • High Quality Digital Photographs • Technology/Knowledge Transfer Plan (draft and final) • Technology/Knowledge Transfer Report (draft and final)
XXXXX-XXXXX AND RELATED ACT PROVISIONS This section is applicable to all Federal-aid construction projects exceeding $2,000 and to all related subcontracts and lower-tier subcontracts (regardless of subcontract size). The requirements apply to all projects located within the right-of- way of a roadway that is functionally classified as Federal-aid highway. This excludes roadways functionally classified as local roads or rural minor collectors, which are exempt. Contracting agencies may elect to apply these requirements to other projects. The following provisions are from the U.S. Department of Labor regulations in 29 CFR 5.5 “Contract provisions and related matters” with minor revisions to conform to the FHWA- 1273 format and FHWA program requirements.
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.
Certain Credit Support Events If (i) the L/C Issuer has honored any full or partial drawing request under any Letter of Credit and such drawing has resulted in an L/C Borrowing, (ii) as of the Letter of Credit Expiration Date, any L/C Obligation for any reason remains outstanding, (iii) the Borrower shall be required to provide Cash Collateral pursuant to Section 2.05 or 8.02(c), or (iv) there shall exist a Defaulting Lender, the Borrower shall immediately (in the case of clause (iii) above) or within one (1) Business Day (in all other cases) following any request by the Administrative Agent or the L/C Issuer, provide Cash Collateral in an amount not less than the applicable Minimum Collateral Amount (determined in the case of Cash Collateral provided pursuant to clause (iv) above, after giving effect to Section 2.15(a)(iv) and any Cash Collateral provided by the Defaulting Lender).
