Vertical Reporting of TEFCA Security Incident(s) Sample Clauses

Vertical Reporting of TEFCA Security Incident(s). Signatory shall report a TEFCA Security Incident to its Participants and Subparticipants as required by an applicable SOP.
AutoNDA by SimpleDocs
Vertical Reporting of TEFCA Security Incident(s). Signatory shall require that each Participant with which it has entered into a Participant-QHIN Agreement: (i) Notify Signatory and Participant’s Subparticipants of any TEFCA Security Incident the Participant experiences in accordance with the timing and content requirements stated in Section 12.3; (ii) Require that each Subparticipant with which the Participant enters into a Participant-Subparticipant Agreement report any TEFCA Security Incident experienced by or reported to the Subparticipant to the Participant and to the Subparticipant’s Downstream Subparticipants in accordance with the timing and content requirements stated in Section 12.3; (iii) Require that each Subparticipant with which the Participant enters into a Participant-Subparticipant Agreement require that its Downstream Subparticipants report any TEFCA Security Incident experienced by or reported to the Downstream Subparticipant to the Upstream Subparticipant and to its own Downstream Subparticipants, in accordance with the timing and content requirements stated in Section 12.3. (iv) Notify Signatory of any TEFCA Security Incident reported to the Participant by one of its Subparticipants.

Related to Vertical Reporting of TEFCA Security Incident(s)

  • Procurement from UN Agencies Goods estimated to cost less than $100,000 equivalent per contract may be procured directly from Inter-Agency Procurement Services Office (IAPSO) in accordance with the provisions of paragraphs 3.1 and 3.9 of the Procurement Guidelines.

  • Electronic and Information Resources Accessibility and Security Standards a. Applicability: The following Electronic and Information Resources (“EIR”) requirements apply to the Contract because the Grantee performs services that include EIR that the System Agency's employees are required or permitted to access or members of the public are required or permitted to access. This Section does not apply to incidental uses of EIR in the performance of the Agreement, unless the Parties agree that the EIR will become property of the State of Texas or will be used by HHSC’s clients or recipients after completion of the Agreement. Nothing in this section is intended to prescribe the use of particular designs or technologies or to prevent the use of alternative technologies, provided they result in substantially equivalent or greater access to and use of a Product.

  • Security Controls for State Agency Data In accordance with Senate Bill 475, Acts 2021, 87th Leg., R.S., pursuant to Texas Government Code, Section 2054.138, Contractor understands, acknowledges, and agrees that if, pursuant to this Contract, Contractor is or will be authorized to access, transmit, use, or store data for System Agency, Contractor is required to meet the security controls the System Agency determines are proportionate with System Agency’s risk under the Contract based on the sensitivity of System Agency’s data and that Contractor must periodically provide to System Agency evidence that Contractor meets the security controls required under the Contract.

  • Security Incident Reporting A security incident occurs when CDA information assets are or reasonably believed to have been accessed, modified, destroyed, or disclosed without proper authorization, or are lost, or stolen. Subrecipient must comply with CDA’s security incident reporting procedures located at xxxxx://xxx.xxxxx.xx.xxx/ProgramsProviders/#Resources.

  • Project Monitoring Reporting and Evaluation The Recipient shall furnish to the Association each Project Report not later than forty-five (45) days after the end of each calendar semester, covering the calendar semester.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!