Unsuccessful Security Incidents definition

Unsuccessful Security Incidents means, without limitation, pings and other broadcast attacks on firewall, port scans, unsuccessful log-on attempts, denial of service attacks, and any combination of the above, so long as no such incident results in unauthorized access, use or disclosure of PHI.

Unsuccessful Security Incidents shall include, but not be limited to, pings and other broadcast attacks on Contractor's firewall, port scans, unsuccessful log-on attempts, denials of service and any combination of the above, so long as no such incident results in unauthorized access, use or disclosure of Protected Health Information and/or Personally Identifiable Information.

Unsuccessful Security Incidents means, without limitation, pings and other broadcast attacks on Business Associate’s firewall, port scans, unsuccessful log-on attempts, denial of service attacks, and any combination of the above, so long as no such incident results in unauthorized access, use, or disclosure of Covered Entity’s ePHI. In this context, the term “Security Incident” shall have the same meaning as such term is defined at 45 C.F.R. § 164.304.

Examples of Unsuccessful Security Incidents in a sentence

• Business Associate shall provide Covered Entity upon written request a Report that: (a) identifies the categories of Unsuccessful Security Incidents; (b) indicates whether Business Associate believes its current defensive security measures are adequate to address all Unsuccessful Security Incidents, given the scope and nature of such attempts; and (c) if the security measures are not adequate, the measures Business Associate will implement to address the security inadequacies.

• Contractor Business Associate shall provide Covered Entity upon written request a Report that: (a) identifies the categories of Unsuccessful Security Incidents; (b) indicates whether Business Associate believes its current defensive security measures are adequate to address all Unsuccessful Security Incidents, given the scope and nature of such attempts; and (c) if the security measures are not adequate, the measures Business Associate will implement to address the security inadequacies.

• Notwithstanding the foregoing, the parties acknowledge and agree that this Section 11 constitutes notice by Associate to Entity of the ongoing existence and occurrence of attempted but Unsuccessful Security Incidents (as defined below) for which no additional notice to Entity shall be required.

• Notwithstanding the foregoing, the parties acknowledge and agree that this section constitutes notice by Associate to Entity of the ongoing existence and occurrence of attempted but Unsuccessful Security Incidents (as defined below) for which no additional notice to Entity shall be required.

• However, the parties acknowledge and agree that this section constitutes notice by Business Associate to Covered Entity of the ongoing existence and occurrence of attempted but Unsuccessful Security Incidents (as defined below) for which no further notice to Covered Entity shall be required.

More Definitions of Unsuccessful Security Incidents

Unsuccessful Security Incidents mean, without limitation, pings, and other broadcast attacks on iManage’s firewall, port scans, unsuccessful log-on attempts, denial of service attacks, and any combination of the above, as long as no such incident results in unauthorized access, acquisition, Use, or Disclosure of Protected Health Information. iManage’s obligation to report under this paragraph is not and will not be construed as an acknowledgement by iManage of any fault or liability with respect to any Use, Disclosure, Security Incident, or Breach.

Unsuccessful Security Incidents means, without limitation, pings and other broadcast attacks on Business Associate’s firewall, port scans, unsuccessful log-on attempts, denial of service attacks, and any combination of the above, so long as no such incident results in unauthorized access, use, or disclosure of PHI. The contact information for the Business Associate and Covered Entity employees to whom reports of unauthorized use or disclosure of PHI, Breaches of Unsecured PHI and successful Security Incidents under this Section shall be made as provided below (as such information may be updated from time to time between the parties). Notification shall be made using the methods as provided in the relevant Underlying Agreement. Business Associate: Xxxxx Xxxxxxxx, Chief Legal & Compliance Officer DeliverHealth Solutions, LLC 0000 Xxxxxxx Xx., Xxxxx 000 Xxxxxxx, XX 00000 Email: xxxxxxxxxx@xxxxxxxxxxxxx.xxx Covered Entity: [Employee Name and Title] [Company Name] [Street Address] [City, State, Zip] [Phone] [Email]

Unsuccessful Security Incidents shall include, but not be limited to, pings and other broadcast attacks on HeC’s firewall, port scans, unsuccessful log-in attempts, denials of service and any combination of the above, so long as no such incident results in unauthorized access, use or disclosure of PHI.

Unsuccessful Security Incidents means, without limitation, pings and other broadcast attacks on Business Associate’s firewall, port scans, unsuccessful log-on attempts, denial of service attacks, and any combination of the above, so long as no such incident results in unauthorized access to, use, or disclosure of PHI. Business Associate shall make such notification in writing, to the individuals designated as contacts by Covered Entity in pa- ragraph 5.6 below, within ten (10) business days of having been made aware of the se- curity incident.

Unsuccessful Security Incidents means pings and other broadcast attacks on Business Associate’s firewall, port scans, attempts to log onto a system of enter a database with an invalid password or username, and denial-of-service attacks that do not result in the system being taken off-line provided that such attacks do not result in an unauthorized access, use, disclosure, modification or destruction of County PHI.

Unsuccessful Security Incidents means, without limitation, pings and other broadcast attacks on firewall, port scans, unsuccessful log-on attempts, denial of service attacks, and any combination of the above, so long as no such incident results in unauthorized access, Use or Disclosure of PHI. PCQC agrees to report promptly, but in no case later than five (5) business days after discovery (as defined by 45 CFR 164.410(a)), to Participant any Use or Disclosure of PHI which is not authorized by this Agreement of which PCQC becomes aware. PCQC agrees to ensure that any Subcontractor that creates, receives, maintains, or transmits PHI, on behalf of PCQC, will agree in writing to comply with the same restrictions and conditions with respect to such information that apply through this Agreement to PCQC. For the purposes of this Agreement, all PHI provided at PCQC’s direction to a Subcontractor of PCQC will be deemed to have been provided to PCQC. If PHI provided to PCQC, or to which PCQC otherwise has access, constitutes a Designated Record Set, PCQC agrees to provide Participant with timely access to such PHI, upon reasonable advance notice and during regular business hours, or, at Participant’s request, to provide an Individual with access to his or her PHI in order to meet the requirements under 45 CFR 164.524 concerning access of Individuals to PHI. In the event an Individual contacts PCQC or its Subcontractor directly about gaining access to his or her PHI, PCQC will not provide such access but rather will forward such request to Participant within three (3) business days of such contact, unless otherwise required by law. If PHI provide to PCQC, or to which PCQC otherwise has access, constitutes a Designated Record Set, PCQC agrees to make timely amendment(s) to such PHI as Participant may direct or agree to pursuant to 45 CFR 164.526. In the event an Individual contacts PCQC or its Subcontractor directly about making amendments to his or her PHI, PCQC will not make such amendments, but rather will promptly forward such request to Participant, unless otherwise required by law. PCQC agrees to make internal practices, books, and records relating to the Use and Disclosure of PHI available to the Secretary of the United States Department of Health and Human Services, during regular business hours, for purposes of the Secretary’s determining compliance with the HIPAA Regulations. PCQC agrees to document Disclosures of PHI and information related to such Disclosures as would be required for Par...

Unsuccessful Security Incidents shall include, but not be limited to, pings and other broadcast attacks on Business Associate’s firewall, port scans, unsuccessful log-on attempts, denials of service, malware such as worms or viruses and any combination of the above, so long as such incidents do not result in unauthorized access, use or disclosure, modification or destruction of PHI.