Vulnerability Scanning Sample Clauses

Vulnerability Scanning. Coinbase employs security best practices to ensure that the Services are secured, updates to its primary services do not introduce new vulnerabilities, and that new services have been sufficiently analyzed for and defended from potential vulnerabilities. Coinbase supplements its day-to-day security practices, including architecture reviews, with regular vulnerability assessments and audits, including (1) automated scans of all code and applications where possible to identify vulnerabilities before ever being introduced to Coinbase’s environment; (2) once services are deployed, implementing continuous monitoring to promptly assess and react to any potential vulnerabilities; and (3) regular evaluation by independent third parties. Critical software patches are evaluated, tested and applied proactively. Penetration Testing. Coinbase performs penetration tests and engages independent third-party entities to conduct application-level penetration tests on an annual basis at minimum. Results of penetration tests are prioritized, triaged, and remediated promptly by Coinbase’s security team according to established SLAs.

Vulnerability Scanning. Alteryx maintains a vulnerability management program and performs regular vulnerability scanning against services and key infrastructure utilizing industry standard tools or well-known external suppliers.

Vulnerability Scanning. Service vulnerability audits must be conducted with reference to the results of the port/protocol scans and the network design. The audit should detail: ⚫ Low, medium and high risk vulnerabilities so that a risk assessments can be made and fixes implemented where necessary ⚫ List any mitigations to medium and high risk.

Vulnerability Scanning. ‌ • Disseminate intrusion detection alerts to respective BO counterparts for all subnets within the scope of this ISA; • Report to the both the CMS BO and the Non-CMS Organization’s BO any security incident that either organizations subnets within the scope of this ISA; and • Block inbound and outbound access for any CMS or Non-CMS Organization information systems on the subnets within the scope of this ISA that are the source of unauthorized access attempts, or the subject of any security events, until the risk is remediated.

Vulnerability Scanning. Both parties shall:

Vulnerability Scanning. Supplier will provide a platform to allow Customer to run automated Vulnerability Scans of the most common ports with the option to customise to Customer’s requirements, to assess systems or applications for known security flaws and weaknesses. Supplier will provide threats that can be managed, allocated, assigned and risks accepted via ▇▇▇▇▇▇▇.▇▇▇ in addition to actionable remediation advice. The service will allow Customer to identify assets that are prone to attacks. Customer will define the scope of the automated scans and take measures to patch or remediate the threats as provided by Supplier’s automated process.

Vulnerability Scanning. 13. Is vulnerability scanning of your development environments that will interface with Motricity a regular and ongoing process? Briefly describe the process, and provide the names of vulnerability testing tools used. ***. We are using *** as our IDS and IPS. Details about *** as a system is available on the link provided. Please refer to Section 4.10 of Appendix for our IDS/IPS management policy.

Vulnerability Scanning. 1.21.4.1 The EC system shall be scanned for vulnerabilities prior to delivery. The EC system shall be scanned using NESSUS or equivalent. The EC system shall be scanned for vulnerabilities using the most recently released signatures. 1.21.4.2 The signatures used for scanning shall be less than 10 calendar days old at the time of scanning. The date of signatures used for each scan shall be provided along with the scan results. The name or reference number for the signatures used for each scan shall be provided along with the scan results. The vulnerability scan report shall be encrypted and provided to the Government. 1.21.4.3 The EC system shall be remediated for any vulnerabilities discovered during scanning in accordance with National Security Agency Guidance for Addressing Malicious Code Risk dated 10 September 2007. The EC system shall remediated for any vulnerabilities discovered during scanning before delivery. CDRLs: C010, C014

Vulnerability Scanning. Castellan: (i) scans for vulnerabilities in the hosted application at least annually and when new vulnerabilities potentially affecting the system/applications are identified; (ii) employs vulnerability scanning tools and techniques that facilitate interoperability among tools and automate parts of the vulnerability management process by using standards for enumerating platforms, software flaws, and improper configurations, formatting checklists and test procedures, and measuring vulnerability impact ; (iii) analyzes vulnerability scan reports and results from security control assessments; (iv) remediates vulnerabilities in accordance with organizational risk assessment; (v) shares information from the vulnerability scanning and security control assessments with appropriate Personnel to help eliminate similar vulnerabilities in other information systems; and (vi) employs periodic external vulnerability scanning and annual penetration testing to assess the overall strength of the Castellan’s defenses (technology, processes, and employees). Upon Customer’s written request, ▇▇▇▇▇▇▇▇▇ will deliver to Customer a summary of the results of the most recent vulnerability scans and penetration tests.