Common use of System Intrusion Clause in Contracts

System Intrusion. In the event of a system intrusion by an unauthorized person or malicious code, affected parties will be notified and a solution will be implemented. Notification of such events to Client by Synacor will occur upon confirmation by Synacor’s security team that there was a bona fide intrusion event, but in no event later than 3 days after the event.

Appears in 2 contracts

Samples: Master Services Agreement, Master Services Agreement (Synacor, Inc.)

AutoNDA by SimpleDocs

System Intrusion. In the event of a system System intrusion by an unauthorized person or malicious code, affected parties will be notified and a solution will be implemented. Notification of such events to Client by Synacor will occur upon confirmation by Synacor’s security team that there was a bona fide intrusion event, but in no event later than 3 days after the event.. [*] = CERTAIN INFORMATION HAS BEEN OMITTED AND FILED SEPARATELY WITH THE COMMISSION. CONFIDENTIAL TREATMENT HAS BEEN REQUESTED WITH RESPECT TO THE OMITTED PORTIONS. CONFIDENTIAL TREATMENT REQUESTED

Appears in 2 contracts

Samples: Master Services Agreement, Master Services Agreement (Synacor, Inc.)

AutoNDA by SimpleDocs

System Intrusion. In the event of a system System intrusion by an unauthorized person or malicious code, affected parties will be notified and a solution will be implemented. Notification of such events to Client by Synacor will occur upon confirmation by Synacor’s security team that there was a bona fide intrusion event, but in no event later than 3 days after the event. [*] CERTAIN INFORMATION HAS BEEN OMITTED AND FILED SEPARATELY WITH THE COMMISSION. CONFIDENTIAL TREATMENT HAS BEEN REQUESTED WITH RESPECT TO THE OMITTED PORTIONS.

Appears in 1 contract

Samples: Master Services Agreement (Synacor, Inc.)

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