Security Reporting Sample Clauses
The Security Reporting clause requires parties to promptly notify each other of any actual or suspected security incidents that could impact the confidentiality, integrity, or availability of data or systems. Typically, this clause outlines the types of incidents that must be reported, the timeframe for notification, and the method of communication, such as reporting data breaches or unauthorized access to sensitive information within a specified period. Its core function is to ensure transparency and enable timely responses to security threats, thereby minimizing potential harm and facilitating compliance with legal or contractual obligations.
Security Reporting. If you’ve discovered a vulnerability in the Chargifi application, please report it to us at the email address noted below. ▇▇▇▇▇▇▇▇ strives to stay on top of the latest security developments both internally and by working with third parties. We appreciate the community’s efforts in creating a more secure web. If you believe your account has been compromised or you are seeing suspicious activity on your account please report it immediately to ▇▇▇▇-▇▇▇▇▇▇▇▇@▇▇▇▇▇▇▇▇.▇▇▇.
Security Reporting. Commencing no less than thirty (30) Days prior to the System Integration Date, and thereafter annually during the Term of this Agreement, Supplier shall deliver to Company evidence of Supplier’s information security safeguards, including but not limited to current ISO27001 reports, SSAE 16 SOC2 Type 2 reports and annual third-party penetration tests, within thirty (30) days of each such report’s completion, and any and all such other similar reports, as completed. Supplier shall, at no cost to Company, mitigate all critical and high-risk findings within ten (10) Days of receiving such findings and provide Company with evidence of such mitigation to the reasonable satisfaction of Company. Malware. Supplier will (consistent with the following sentence) ensure that no Malware or malicious software, or similar items are coded or introduced into any aspect of the Grid Services, the GSDS, the DERMS, and the Supplier information systems and operating environments and processes used or relied upon by Supplier to provide the Grid Services, including the information, data and other materials delivered by or on behalf of Supplier to Company, the customers of Company, Participants and/or third party providers (collectively, Environment). Supplier will continue to implement improvements to and upgrades of its Malware prevention and correction programs and processes consistent with the then‑current NIST technology industry’s standards and, in any case, no less robust than the programs and processes implemented by Supplier with respect to its own information systems and, on a regular basis as requested by Company, Supplier shall provide Company with sufficient evidence of the same. Supplier shall furthermore ensure that all Supplier Agents comply with the obligations of Supplier as set forth in this Section 27.1 (c) (Malware). If Malware is found to have been introduced into the Environment, Supplier will promptly notify Company, and Supplier shall take immediate action to eliminate and remediate the effects of the Malware at Supplier’s expense. Supplier shall not modify or otherwise take corrective action with respect to the Company Systems except at Company’s request. Supplier will promptly report to Company the nature and status of all security incidents, Malware detection, elimination and remediation efforts. On a regular basis as requested by the Company, Supplier shall provide Company with sufficient evidence of its efforts at continuous monitoring to evaluate the ...
Security Reporting. Contractor must provide security reports, including, but not limited to:
i. Security assessments: results of assessments conducted to identify and mitigate vulnerabilities and risks in the Application Software.
Security Reporting. In the event where the Client suspects any irregular activities or security activities, such reports should be emailed to ▇▇▇▇▇▇▇▇▇▇@▇▇▇▇▇▇.▇▇▇ along with any supporting logs, screenshots, or proof of incident.
Security Reporting. The contractor shall perform data analysis by functional area of the security program metrics to assess the health of security posture and provide a get well plan, to the Government Security Manager and/or Information Assurance Manager (IAM), as applicable, as well as the COR that clearly define roles, expectations, and measure of success. The contractor shall submit to the COR, within 24 hours, a copy of all security reports submitted to any Cognizant Security Activity (CSA), Cognizant Security Office (CSO), base Security Office, or other Federal authority under DoDM 5220.22 National Industrial Security Program Operating Manual (NISPOM) Chapter 1, Section 3. The contractor shall report security incidents IAW CDRL A011 Incident Report (DI-MGMT-82071).
Security Reporting. The Contractor must maintain and submit to the COTR or designee, as requested, reports that detail the following: • Incident Reports • Key Control Manifest • Custody and Destruction of Damaged Key Logs • Visitor Logs
Security Reporting. Design-Builder shall report all Security Incidents, emergencies, crimes in progress and Potential Incidents to the City and the applicable Emergency Services:
(a) in real time, or as soon as practicable after Design-Builder or a Design-Builder Person becomes aware of the Security Incident, emergency, crime in progress or Potential Incident; and
(b) in accordance with the Security Program. All security reports shall be prepared and maintained in a format consistent with the City’s then current security incident reporting systems.
Security Reporting. COUNTY’s system administrator shall be able to report on user activity by logon ID. These reports shall contain details on user, date, time and type of access.
Security Reporting. 8.1.1 The Supplier shall:
(A) Update the Security Management Plan for approval by the Buyer
(B) Monitor the delivery of assurance activities
(C) Manage and maintain the accuracy of a Security Risk Register for the
(D) Agree a document which presents the residual security risks to inform the Buyer’s decision to give approval to the Supplier to process, store and transit the Buyer’s data.
(E) Monitor security risk impacting upon the operation of the
(F) Agree a Security Incident Management and Reporting process with the Buyer within 30 days of the commencement of the contract
(G) Report security incidents in accordance with the agreed Security Incident Management and Reporting process
(H) Agree with the Buyer a mechanism for security reporting within 30 days of the commencement of the contract.
Security Reporting. Project Co shall report all Security Incidents, emergencies, crimes in progress and Potential Incidents to the City and the applicable Emergency Services:
(a) in real time, or as soon as practicable after Project Co or a Project Co Person becomes aware of the Security Incident, emergency, crime in progress or Potential Incident; and
(b) in accordance with the Security Program. All security reports shall be prepared and maintained in a format consistent with the City’s then current security incident reporting systems.