Payment Card Industry (PCI) Executive Report 08/04/2014



Similar documents
Payment Card Industry (PCI) Executive Report 10/27/2015

Payment Card Industry (PCI) Executive Report. Pukka Software

ASV Scan Report Attestation of Scan Compliance

Payment Card Industry (PCI) Data Security Standard

Payment Card Industry (PCI) Data Security Standard

Scan Report Executive Summary. Part 2. Component Compliance Summary IP Address :

GETTING STARTED WITH THE PCI COMPLIANCE SERVICE VERSION 2.3. May 1, 2008

Overview of Network Security The need for network security Desirable security properties Common vulnerabilities Security policy designs

PCI Security Scan Procedures. Version 1.0 December 2004

Firewall Firewall August, 2003

Vulnerability Scans. Bomgar 14.2

1 hours, 30 minutes, 38 seconds Heavy scan. All scanned network resources. Copyright 2001, FTP access obtained

Vulnerability Scans Remote Support 15.1

Automated Vulnerability Scan Results

ANNEXURE-1 TO THE TENDER ENQUIRY NO.: DPS/AMPU/MIC/1896. Network Security Software Nessus- Technical Details

Client logo placeholder XXX REPORT. Page 1 of 37

Vulnerability Scans. Security

Cyber Security Scan Report

Vulnerability Scan. January 6, 2015

CS5008: Internet Computing

Penetration Testing. NTS330 Unit 1 Penetration V1.0. February 20, Juan Ortega. Juan Ortega, juaorteg@uat.edu. 1 Juan Ortega, juaorteg@uat.

Nessus Perimeter Service User Guide (HTML5 Interface) March 18, 2014 (Revision 9)

IBM. Vulnerability scanning and best practices

Nessus Report. Report 21/Mar/2012:16:43:56 GMT

Cyber Essentials. Test Specification

Global Partner Management Notice

1 Scope of Assessment

How To Pass An Asv Scan

Port Scanning and Vulnerability Assessment. ECE4893 Internetwork Security Georgia Institute of Technology

My FreeScan Vulnerabilities Report

Payment Card Industry (PCI) Approved Scanning Vendors. Program Guide Reference 1.0 PCI DSS Version 1.2

INFORMATION SUPPLEMENT. Migrating from SSL and Early TLS. Version 1.0 Date: April 2015 Author: PCI Security Standards Council

Web App Security Audit Services

PCI Vulnerability Validation Report

Redhawk Network Security, LLC Layton Ave., Suite One, Bend, OR

TRIPWIRE PURECLOUD. TRIPWIRE PureCloud USER GUIDE

Introduction of Intrusion Detection Systems

Firewalls. Firewalls. Idea: separate local network from the Internet 2/24/15. Intranet DMZ. Trusted hosts and networks. Firewall.

Apache Partial HTTP Request Denial of Service Vulnerability - Zero Day. SSL Certificate - Subject Common Name Does Not Match Server FQDN

REDSEAL NETWORKS SOLUTION BRIEF. Proactive Network Intelligence Solutions For PCI DSS Compliance

Payment Card Industry (PCI) Data Security Standard Approved Scanning Vendors

IBM Security QRadar SIEM Version MR1. Vulnerability Assessment Configuration Guide

Nessus Enterprise Cloud User Guide. October 2, 2014 (Revision 9)

Overview. Summary of Key Findings. Tech Note PCI Wireless Guideline

PCI COMPLIANCE REQUIREMENTS COMPLIANCE CALENDAR

Linux Network Security

How To Understand A Network Attack

1. Introduction. 2. DoS/DDoS. MilsVPN DoS/DDoS and ISP. 2.1 What is DoS/DDoS? 2.2 What is SYN Flooding?

April 11, (Revision 2)

Web Application Vulnerability Testing with Nessus

Firewall Testing Methodology W H I T E P A P E R

FIREWALLS & NETWORK SECURITY with Intrusion Detection and VPNs, 2 nd ed. Chapter 4 Finding Network Vulnerabilities

PROFESSIONAL SECURITY SYSTEMS

74% 96 Action Items. Compliance

Attack Vector Detail Report Atlassian

White Paper. Managing Risk to Sensitive Data with SecureSphere

Network Security. Marcus Bendtsen Institutionen för Datavetenskap (IDA) Avdelningen för Databas- och Informationsteknik (ADIT)

Nessus. A short review of the Nessus computer network vulnerability analysing tool. Authors: Henrik Andersson Johannes Gumbel Martin Andersson

FortiWeb 5.0, Web Application Firewall Course #251

8. Firewall Design & Implementation

REPORT ON AUDIT OF LOCAL AREA NETWORK OF C-STAR LAB

Locking down a Hitachi ID Suite server


Payment Card Industry (PCI) Data Security Standard

Chapter 4 Firewall Protection and Content Filtering

GFI White Paper PCI-DSS compliance and GFI Software products

Protecting Critical Infrastructure

PCI Compliance. Network Scanning. Getting Started Guide

SECURITY ADVISORY FROM PATTON ELECTRONICS

Cyber Essentials PLUS. Common Test Specification

1. Introduction. 2. Web Application. 3. Components. 4. Common Vulnerabilities. 5. Improving security in Web applications

ASV Scan Report Vulnerability Details PRESTO BIZ

- Basic Router Security -

Client Server Registration Protocol

!!!!!!!!!!!!!!!!!!!!!!

PCI DSS Policies Outline. PCI DSS Policies. All Rights Reserved. ecfirst Page 1 of 7

Demystifying Penetration Testing for the Enterprise. Presented by Pravesh Gaonjur

Network Security Fundamentals

Port Scanning. Objectives. Introduction: Port Scanning. 1. Introduce the techniques of port scanning. 2. Use port scanning audit tools such as Nmap.

Firewalls, Tunnels, and Network Intrusion Detection. Firewalls

noway.toonux.com 09 January 2014

Web Application Firewall

Firewalls. Chapter 3

SECURITY PATCH MANAGEMENT INSTALLATION POLICY AND PROCEDURES

Intrusion Detection System Based Network Using SNORT Signatures And WINPCAP

APNIC elearning: Network Security Fundamentals. 20 March :30 pm Brisbane Time (GMT+10)

Did you know your security solution can help with PCI compliance too?

Chapter 4 Firewall Protection and Content Filtering

Firewalls, Tunnels, and Network Intrusion Detection

locuz.com Professional Services Security Audit Services

Where every interaction matters.

Installing and Configuring Nessus by Nitesh Dhanjani

Acquia Cloud Edge Protect Powered by CloudFlare

Network Security. Chapter 9. Attack prevention, detection and response. Attack Prevention. Part I: Attack Prevention

McAfee Vulnerability Manager 7.0.2

An Introduction to Network Vulnerability Testing

Solution of Exercise Sheet 5

Transcription:

Payment Card Industry (PCI) Executive Report 08/04/2014 ASV Scan Report Attestation of Scan Compliance Scan Customer Information Approved Scanning Vendor Information Company: A.B. Yazamut Company: Qualys Contact: Alex Betis Title: Contact: Telephone: Business Address: Zeev Wainhoiz 3, Email: alex.betis@gmail. com Qualys PCI ASV Support Title: Telephone: 1-866-801-6161 Email: Business Address: 1600 Bridge Parkway, Qualys PCI ASV Support Support@Qualys. com City: Yehud State/Province: City: Redwood Shores State/Province: California ZIP: 56290 URL: ZIP: 94065 URL: http://www. qualys.com/ Scan Status * Compliance Status : * Number of unique components scanned: 1 * Number of identified failing vulnerabilities: 0 * Number of components found by ASV but not scanned because scan customer confirmed components were out of scope: 29 * Date scan completed: 08/03/2014 * Scan expiration date (90 days from date scan completed): 11/01/2014 Scan Customer Attestation A.B. Yazamut attests on 08/04/2014 at 13:56:24 GMT that this scan includes all components* which should be in scope for PCI DSS, any component considered out-of-scope for this scan is properly segmented from my cardholder data environment, and any evidence submitted to the ASV to resolve scan exceptions is accurate and complete.a.b. Yazamut also acknowledges the following: 1) proper scoping of this external scan is my responsibility, and 2) this scan result only indicated whether or not my scanned systems are compliant with the external vulnerability scan requirement of PCI DSS; this scan result does not represent my overall compliance status with PCI DSS or provide any indication of compliance with other PCI DSS requirements. ASV Attestation This scan and report was prepared and conducted by Qualys under certificate number 3728-01-09, according to internal processes that meet PCI DSS requirement 11.2 and the PCI DSS ASV Program Guide. Qualys attests that the PCI DSS scan process was followed, including a manual or automated Quality Assurance process with customer boarding and scoping practices, review of results for anomalies, and review and correction of 1) disputed or incomplete results, 2) false positives, and 3) active scan interference. This report and any exceptions were reviewed by Qualys PCI ASV Support Payment Card Industry (PCI) Executive Report page 1

ASV Scan Report Executive Summary Part 1. Scan Information Scan Customer Company: A.B. Yazamut ASV Company: Qualys Date scan was completed: 08/03/2014 Scan expiration date: 11/01/2014 Part 2. Component Compliance Summary IP Address: Part 2. Component Compliance Summary - (Hosts Not Current) Part 3a. Vulnerabilities Noted for each IP Address IP Address port 25/tcp port 587/tcp port 443/tcp-SSL port 443/tcp-SSL port 80/tcp (www.4project.co. il) port 80/tcp Vulnerabilities Noted per IP address 86847 - Apache Partial HTTP Request Denial of Service Vulnerability - Zero Day CVE-2007-6750 74095 - Postfix SMTP Log Denial of Service Vulnerability CVE-2001-0894 74095 - Postfix SMTP Log Denial of Service Vulnerability CVE-2001-0894 42366 - SSLv3.0/TLSv1.0 Protocol Weak CBC Mode Vulnerability CVE-2011-3389 Severity Level 38601 - SSL/TLS use of weak RC4 cipher CVE-2013-2566 2.6 150122 - Cookie Does Not Contain The "secure" Attribute 0 150122 - Cookie Does Not Contain The "secure" Attribute 0 CVSS Score 5 5 5 4.3 Compliance Status Exceptions, False Positives, or Compensating Controls Noted by the ASV for this Vulnerability The vulnerability is purely a denial-of-service (DoS) vulnerability. The vulnerability is purely a denial-of-service (DoS) vulnerability. The vulnerability is purely a denial-of-service (DoS) vulnerability. ASV Score = 2.6. Access complexity in the CVSS base metric should be High. The vulnerability is not included in the NVD. ASV Score = 0 The vulnerability is not included in the NVD. ASV Score = 0 Part 3b. Special Notes by IP Address IP Address Note Due to increased risk to the cardholder data environment when remote access software is present, please 1) justify the business need for this software to the ASV and 2) confirm it is either implemented securely or disabled/removed. Item Noted (remote access software, POS software, etc.) 42017 - Remote Access or Management Service Detected (SSH:port 22/TCP) Scan customer's declaration that software is implemented securely (see next column if not implemented securely) Yes Scan customer's description of actions taken to either: 1) remove the software or 2) implement security controls to secure the software The remote access is required for server management. Payment Card Industry (PCI) Executive Report page 2

Report Summary Company: A.B. Yazamut Hosts in Account: 1 Hosts Scanned: 1 Hosts Active: 1 Scan Date: 08/03/2014 at 08:46:30 GMT Report Date: 08/04/2014 at 13:56:32 GMT Report Title: PCI scan result Template Title: Payment Card Industry (PCI) Executive Report Summary of Vulnerabilities Vulnerabilities Total 89 Average Security Risk 3.0 by Severity Severity Confirmed Potential Information Gathered Total 5 0 0 0 0 4 0 0 0 0 3 1 1 2 4 2 2 0 8 10 1 1 2 72 75 Total 4 3 82 89 by PCI Severity PCI Severity Confirmed Potential Total High 0 0 0 Medium 1 3 4 Low 3 0 3 Total 4 3 7 Payment Card Industry (PCI) Executive Report page 3

Vulnerabilities by PCI Severity Potential Vulnerabilities by PCI Severity Payment Card Industry (PCI) Executive Report page 4

Vulnerabilities by Severity Potential Vulnerabilities by Severity Payment Card Industry (PCI) Executive Report page 5

Appendices Hosts Scanned Option Profile Scan Scanned TCP Ports: Full Scanned UDP Ports: Standard Scan Scan Dead Hosts: Off Load Balancer Detection: Off Password Brute Forcing: Standard Vulnerability Detection: Complete Windows Authentication: Disabled SSH Authentication: Disabled Oracle Authentication: Disabled SNMP Authentication: Disabled Perform 3-way Handshake: Off Advanced Hosts Discovery: TCP Standard Scan, UDP Standard Scan, ICMP On Ignore RST packets: Off Ignore firewall-generated SYN-ACK packets: Off Do not send ACK or SYN-ACK packets during host discovery: Off Payment Card Industry (PCI) Executive Report page 6

Report Legend Payment Card Industry (PCI) Status An overall PCI compliance status of PASSED indicates that all hosts in the report passed the PCI compliance standards. A PCI compliance status of PASSED for a single host/ip indicates that no vulnerabilities or potential vulnerabilities, as defined by the PCI DSS compliance standards set by the PCI Council, were detected on the host. An overall PCI compliance status of FAILED indicates that at least one host in the report failed to meet the PCI compliance standards. A PCI compliance status of FAILED for a single host/ip indicates that at least one vulnerability or potential vulnerability, as defined by the PCI DSS compliance standards set by the PCI Council, was detected on the host. Vulnerability Levels A Vulnerability is a design flaw or mis-configuration which makes your network (or a host on your network) susceptible to malicious attacks from local or remote users. Vulnerabilities can exist in several areas of your network, such as in your firewalls, FTP servers, Web servers, operating systems or CGI bins. Depending on the level of the security risk, the successful exploitation of a vulnerability can vary from the disclosure of information about the host to a complete compromise of the host. 1 Minimal Intruders can collect information about the host (open ports, services, etc.) and may be able to use this information to find other vulnerabilities. 2 Medium Intruders may be able to collect sensitive information from the host, such as the precise version of software installed. With this information, intruders can easily exploit known vulnerabilities specific to software versions. 3 Serious Intruders may be able to gain access to specific information stored on the host, including security settings. This could result in potential misuse of the host by intruders. For example, vulnerabilities at this level may include partial disclosure of file contents, access to certain files on the host, directory browsing, disclosure of filtering rules and security mechanisms, denial of service attacks, and unauthorized use of services, such as mail-relaying. 4 Critical Intruders can possibly gain control of the host, or there may be potential leakage of highly sensitive information. For example, vulnerabilities at this level may include full read access to files, potential backdoors, or a listing of all the users on the host. 5 Urgent Intruders can easily gain control of the host, which can lead to the compromise of your entire network security. For example, vulnerabilities at this level may include full read and write access to files, remote execution of commands, and the presence of backdoors. Low Medium High A vulnerability with a CVSS base score of 0.0 through 3.9. These vulnerabilities are not required to be fixed to pass PCI compliance. A vulnerability with a CVSS base score of 4.0 through 6.9. These vulnerabilities must be fixed to pass PCI compliance. A vulnerability with a CVSS base score of 7.0 through 10.0. These vulnerabilities must be fixed to pass PCI compliance. Potential Vulnerability Levels A potential vulnerability is one which we cannot confirm exists. The only way to verify the existence of such vulnerabilities on your network would be to perform an intrusive scan, which could result in a denial of service. This is strictly against our policy. Instead, we urge you to investigate these potential vulnerabilities further. 1 Minimal If this vulnerability exists on your system, intruders can collect information about the host (open ports, services, etc.) and may be able to use this information to find other vulnerabilities. 2 Medium If this vulnerability exists on your system, intruders may be able to collect sensitive information from the host, such as the precise version of software installed. With this information, intruders can easily exploit known vulnerabilities specific to software versions. 3 Serious If this vulnerability exists on your system, intruders may be able to gain access to specific information stored on the host, including security settings. This could result in potential misuse of the host by intruders. For example, vulnerabilities at this level may include partial disclosure of file contents, access to certain files on the host, directory browsing, disclosure of filtering rules and security mechanisms, denial of service attacks, and unauthorized use of services, such as mail-relaying. Payment Card Industry (PCI) Executive Report page 7

4 Critical If this vulnerability exists on your system, intruders can possibly gain control of the host, or there may be potential leakage of highly sensitive information. For example, vulnerabilities at this level may include full read access to files, potential backdoors, or a listing of all the users on the host. 5 Urgent If this vulnerability exists on your system, intruders can easily gain control of the host, which can lead to the compromise of your entire network security. For example, vulnerabilit es at this level may include full read and write access to files, remote execution of comma ds, and the presence of backdoors. Low Medium High A potential vulnerability with a CVSS base score of 0.0 through 3.9. These vulnerabilities are not required to be fixed to pass PCI compliance. A potential vulnerability with a CVSS base score of 4.0 through 6.9. These vulnerabilities must be fixed to pass PCI compliance. A potential vulnerability with a CVSS base score of 7.0 through 10.0. These vulnerabilities must be fixed to pass PCI compliance. Information Gathered Information Gathered includes visible information about the network related to the host, such as traceroute information, Internet Service Provider (ISP), or a list of reachable hosts. Information Gathered severity levels also include Network Mapping data, such as detected firewalls, SMTP banners, or a list of open TCP services. 1 Minimal Intruders may be able to retrieve sensitive information related to the host, such as open UDP and TCP services lists, and detection of firewalls. 2 Medium Intruders may be able to determine the operating system running on the host, and view banner versions. 3 Serious Intruders may be able to detect highly sensitive data, such as global system user lists. Payment Card Industry (PCI) Executive Report page 8

Payment Card Industry (PCI) Executive Report page 9