We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

System Protection Sample Clauses

System Protection. To prevent compromise of systems which contain DSHS Data or through which that Data passes: a. Systems containing DSHS Data must have all security patches or hotfixes applied within 3 months of being made available. b. The Contractor will have a method of ensuring that the requisite patches and hotfixes have been applied within the required timeframes. c. Systems containing DSHS Data shall have an Anti-Malware application, if available, installed. d. Anti-Malware software shall be kept up to date. The product, its anti-virus engine, and any malware database the system uses, will be no more than one update behind current.
System Protection. Interconnection Customer shall, at its expense, install, operate and maintain such System Protection Facilities as may be required in connection with operation of the Customer Facility and the Customer Interconnection Facilities consistent with Applicable Technical Requirements and Standards. Interconnected Transmission Owner shall install any System Protection Facilities that may be required, as determined by Transmission Provider, on the Transmission Owner Interconnection Facilities or the Transmission System in connection with the operation of the Customer Facility and the Customer Interconnection Facilities. Responsibility for the cost of any System Protection Facilities required on the Transmission Owner Interconnection Facilities or the Transmission System shall be allocated as provided in Section 217 of the Tariff.
System Protection. The Interconnection Customer shall install and maintain protection systems in accordance with applicable provisions of the ISO New England Operating Documents, Applicable Reliability Standards, or successor documents.
System Protection. Project Developer shall, at its expense, install, operate and maintain such System Protection Facilities as may be required in connection with operation of the Generating Facility or Merchant Transmission Facility and the Project Developer Interconnection Facilities consistent with Applicable Technical Requirements and Standards. Transmission Owner shall install any System Protection Facilities that may be required, as determined by Transmission Provider, on the Transmission Owner Interconnection Facilities and Transmission Owner Upgrades or the Transmission System in connection with the operation of the Generating Facility or Merchant Transmission Facility and the Project Developer Interconnection Facilities. Responsibility for the cost of any System Protection Facilities required on the Transmission Owner Interconnection Facilities and Transmission Owner Upgrades or the Transmission System shall be allocated as provided in GIP, section [to be determined].
System Protection. To prevent compromise of systems which contain DCYF Data or through which that Data passes: a. Systems containing Data must have all security patches or hotfixes applied within three (3) months of being made available; b. The Contractor will have a method of ensuring that the requisite patches and hotfixes have been applied within the required timeframes; c. Systems containing Data shall have an Anti-Malware application, if available, installed; and d. Anti-Malware software shall be kept up to date. The product, its anti-virus engine, and any malware database the system uses, will be no more than one update behind current.
System Protection a) Line 10
System Protection. At the DC facilities, system protection is installed in the form of an emergency power function. Activation criteria for emergency power can be locally-measured frequency and voltage or via telecommunications on the basis of a supplied signal. In the event of activation, any ongoing normal regulation will be interrupted. Activation over and above the agreed limits and regulation back to plan may not occur until the counterparty has approved this. (See further in Appendix 5 – System protection).
System Protection. To prevent compromise of systems which contain DOC Data or through which that Data passes: a. Systems containing DOC Data must have all security patches or hotfixes applied within 3 months of being made available. b. The Contractor will have a method of ensuring that the requisite patches and hotfixes have been applied within the required timeframes. c. Systems containing DOC Data shall have an Anti-Malware application, if available, installed. d. Anti-Malware software shall be kept up to date. The product, its anti-virus engine, and any malware database the system uses, will be no more than one update behind current. These anti-malware practices must meet or exceed those described in NIST SP800-40. e. The architecture must provide continuous monitoring of both internal and external activity for anomalies and identify, report, and defend against security intrusions before data is compromised. f. Contractor shall conduct penetration tests at least once every 24 months, system vulnerability assessments at least monthly, and application vulnerability assessments prior to the production release of any changes to source code. g. Contractor has implemented application/system development practices consistent with the current version of NIST SP800-64 for low to moderate impact systems, and warrants the software does not contain any of the Open Web Application Security project (OWASP) top 10 vulnerabilities - xxxxx://xxx.xxxxx.xxx/index.php/Main_Page h. Contractor has a practice of systematic collection, monitoring, alerting, maintenance, retention, and disposal of security event logs and application audit trails. Logs and audit trails are written to an area inaccessible to system users and are protected from editing. At a minimum the logs and audit trails will provide historical details on all transactions within the system that are necessary to reconstruct activities. Including recording; type of event, date, time, account identification and machine identifiers for each logged transaction. Audit and log files can be analyzed by type in order to find emerging issues or trends. Contractor has settings triggering an immediate notification to appropriate system administrators for severe incidents. Logs are secured against unauthorized changes. At a minimum, logs must be retained for a period of 6 months.
System Protection. System protection can be used to increase the transmission capacity and/or system security between and within the subsystems. The settings and operational status of system protection shall be decided upon and monitored by the respective Party. In cases when system protection has a bearing on two or more subsystems, co-ordination and communication of the operating status shall take place between the Parties concerned. The requirements relating to system protection are set out in Appendix 2. The forms of system protection used are set out in Appendix 5.