Security violation report Sample Clauses

Security violation report. The mechanism supports the procedure of reporting a security violation. The primitives covered in this subclause are listed in Table 19. Table 19 — Security violation report primitives Service Primitive Request Indication Response Confirm MLME-SECURITY-VIOLATION 6.2.8.1 Table 20 lists the parameters that appear in the primitives of this subclause. Table 20 — Security violation report primitive parameters Name Type Valid range Description ViolationCode Enumeration INVALID_MODE, INVALID_MIC, INVALID_TKID, REPLAYED_FRAME Indicates the cause of a security violation
AutoNDA by SimpleDocs

Related to Security violation report

  • Condition Report The landlord and tenant are required to inspect the residential unit together at the beginning and end of the tenancy and complete a written condition report. If the landlord allows the tenant to have a pet after the start of the tenancy, an inspection report must be done on the day the tenant starts keeping a pet or on another day mutually agreed to by the landlord and tenant, unless the tenancy started on or after January 1, 2004, and a condition inspection report was completed at that time. A report may describe any damage, how clean each room is, and the general condition of the residential unit including: the floors, carpets, appliances, and paint on the walls. The report must be signed and dated by both the landlord and the tenant who made the inspection, and each should keep a copy. Change of Landlord – A new landlord has the same rights and duties as the previous one and must follow all the terms of this agreement unless the tenant and new landlord agree to other terms.

  • CONTRACT COMPLIANCE REQUIREMENT The HUB requirement on this Contract is 0%. The student engagement requirement of this Contract is 0 hours. The Career Education requirement for this Contract is 0 hours. Failure to achieve these requirements may result in the application of some or all of the sanctions set forth in Administrative Policy 3.10, which is hereby incorporated by reference.

  • Security Violations and Accounts Updates Grantee will adhere to the Confidentiality Article requirements and HHS Data Usage Agreement of this contract and immediately contact System Agency if a security violation is detected, or if Grantee has any reason to suspect that the security or integrity of the CMBHS data has been or may be compromised in any way.

  • Compliance Report The Subservicer agrees that it shall permit, not more than once per year, the Servicer, the Issuer, the Indenture Trustee or the Indenture Administrator, as the Indenture Trustee’s designee, to conduct or have conducted a procedural audit regarding the Subservicer’s compliance with the requirements of the Higher Education Act or the terms of this Agreement. Such audits shall be at the expense of the Servicer.

  • Reporting Violations a) When appropriate, faculty members will submit timely written communication to their immediate supervisor any condition that comes to their attention that may, in their judgment, pose a threat to the health or safety of any person associated with the District.

  • Litigation Reporting If Contractor is served with a pleading or other document in connection with an action before a court or other administrative decision making body, and such pleading or document relates to this Participating Addendum or may affect Contractor’s ability to perform its obligations under this Participating Addendum, Contractor shall, within 10 days after being served, notify the State of such action and deliver copies of such pleading or document to the State’s primary contact identified in §5 of the Participating Addendum .

  • Information Reporting (a) The Fund agrees that, during the Current Special Rate Period and so long as BANA or any Affiliate thereof is the beneficial owner of any Outstanding VRDP Shares, it will deliver, or direct the Tender and Paying Agent to deliver, to BANA and any such Affiliate:

  • Evaluation Report 20.5.4.1 The summary evaluation report shall be prepared by the Faculty Evaluation Committee and administrative evaluator(s) and shall include each evaluator’s individual rating. The summary evaluation report shall take into account the results of each of the evaluation components (Section 20.5.3) in order to arrive at an overall rating. When the committee and the administrative evaluator(s) cannot reach an agreement as to the overall rating, the report must include written explanation.

  • Compliance Reporting a. Provide reports to the Securities and Exchange Commission, the National Association of Securities Dealers and the States in which the Fund is registered.

  • Policy Compliance Violations The Requester and Approved Users acknowledge that the NIH may terminate the DAR, including this Agreement and immediately revoke or suspend access to all controlled-access datasets subject to the NIH GDS Policy at any time if the Requester is found to be no longer in agreement with the principles outlined in the NIH GDS Policy, the terms described in this Agreement, or the Genomic Data User Code of Conduct. The Requester and PI agree to notify the NIH of any violations of the NIH GDS Policy, this Agreement, or the Genomic Data User Code of Conduct data within 24 hours of when the incident is identified. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. The Requester and PI agree to notify the appropriate DAC(s) of any unauthorized data sharing, breaches of data security, or inadvertent data releases that may compromise data confidentiality within 24 hours of when the incident is identified. As permitted by law, notifications should include any known information regarding the incident and a general description of the activities or process in place to define and remediate the situation fully. Within 3 business days of the DAC notification(s), the Requester agrees to submit to the DAC(s) a detailed written report including the date and nature of the event, actions taken or to be taken to remediate the issue(s), and plans or processes developed to prevent further problems, including specific information on timelines anticipated for action. The Requester agrees to provide documentation verifying that the remediation plans have been implemented. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. All notifications and written reports of data management incidents should be sent to the DAC(s) indicated in the Addendum to this Agreement. NIH, or another entity designated by NIH may, as permitted by law, also investigate any data security incident or policy violation. Approved Users and their associates agree to support such investigations and provide information, within the limits of applicable local, state, tribal, and federal laws and regulations. In addition, Requester and Approved Users agree to work with the NIH to assure that plans and procedures that are developed to address identified problems are mutually acceptable and consistent with applicable law.

Time is Money Join Law Insider Premium to draft better contracts faster.