Vulnerability Scans Sample Clauses

Vulnerability Scans. A vulnerability scan (“Scan”) is necessary for PC, IP enabled terminal, or integrated ECR merchants. Here are the steps to receive your Scan:
AutoNDA by SimpleDocs
Vulnerability Scans. Vendor shall perform internal and external host/network vulnerability scans at least quarterly and after any material change in the host/network configuration, and suspected or substantiated IT security or privacy incidents.
Vulnerability Scans. A vulnerability scan (“Scan”) is necessary for any merchant with Internet accessible I/P addresses connected to or that could allow access to their cardholder data environment. This includes, but is not limited to internet connected terminals, internet connected registers, and ecommerce environments. Here are the steps to receive your Scan:
Vulnerability Scans. The Service Provider shall ensure that the Hosted Infrastructure, Platform Components and Application(s) are subjected to an OWASP-compliant vulnerability scan at least quarterly.
Vulnerability Scans. A vulnerability scan (“Scan”) is necessary for may not waive, forgive, release, assign or in any manner fail to insist on strict performance of Sections 2.B, 2.D, 5.B.iii, 6.A, and 14.X.
Vulnerability Scans. Centercode (either directly or through third parties) shall scan all internet-accessible sites related to Customer’s Services at least annually and at any time a major change is made to a hosted site that could introduce vulnerabilities using industry standard scanning tools such as Nessus.
Vulnerability Scans. Pearson has a single, global vulnerability scanning and management program for its entire server/hosting estate. Coverage includes co-located and cloud-based servers, as well as all of the data centers managed directly by Pearson. Scanning is executed on an ongoing periodic basis for all servers/networks in scope, with critical applications and services are scanned more frequently depending upon the severity and necessity. Vulnerabilities discovered as part of Pearson vulnerability management program are assessed, collated and presented to individual application and system owners for remediation. Pearson then tracks the risk represented by vulnerabilities, and identifies where remediation requires additional attention or escalation through a Risk Exception process. When highly critical vulnerabilities are released, or threats are assessed as being high priority, Pearson executes a global remediation plan independent of vulnerability scanning to ensure the gap between vulnerability and closure is as small as possible. ● Pearson does not authorize customers to perform vulnerability scans or penetration scans against Pearson products which are shared with other customers. ● Pearson may share the results of our security assessments with our customers ● We will provide high level summaries via email under NDA. ● We will share actual vulnerability data on site and in person.
AutoNDA by SimpleDocs

Related to Vulnerability Scans

  • Vulnerability Management BNY Mellon will maintain a documented process to identify and remediate security vulnerabilities affecting its systems used to provide the services. BNY Mellon will classify security vulnerabilities using industry recognized standards and conduct continuous monitoring and testing of its networks, hardware and software including regular penetration testing and ethical hack assessments. BNY Mellon will remediate identified security vulnerabilities in accordance with its process.

  • Searchability Offering searchability capabilities on the Directory Services is optional but if offered by the Registry Operator it shall comply with the specification described in this section.

  • Disturbance Analysis Data Exchange The Parties will cooperate with one another and the NYISO in the analysis of disturbances to either the Large Generating Facility or the New York State Transmission System by gathering and providing access to any information relating to any disturbance, including information from disturbance recording equipment, protective relay targets, breaker operations and sequence of events records, and any disturbance information required by Good Utility Practice.

  • Start-Up and Synchronization Consistent with the mutually acceptable procedures of the Developer and Connecting Transmission Owner, the Developer is responsible for the proper synchronization of the Large Generating Facility to the New York State Transmission System in accordance with NYISO and Connecting Transmission Owner procedures and requirements.

  • Corrective Measures If the Participating Generator fails to meet or maintain the requirements set forth in this Agreement and/or the CAISO Tariff, the CAISO shall be permitted to take any of the measures, contained or referenced in the CAISO Tariff, which the CAISO deems to be necessary to correct the situation.

Time is Money Join Law Insider Premium to draft better contracts faster.