Compliance SonicWALL PCI 1.1 Implementation Guide A PCI Implementation Guide for SonicWALL SonicOS Standard In conjunction with ControlCase, LLC (PCI Council Approved Auditor)
SonicWall SonicOS Standard PCI Data Security Standard 1.1 Compliance: The following are the PCI Data Security Standard 1.1 controls which are applicable to SonicWall SonicOS Standard Edition. PCI DSS Requirement 1.1.1 Establish firewall configuration standards that include: A formal process for approving and testing all external network connections and changes to the firewall configuration. N/A SonicWALL Administrator Guide should include this as a Best Practice. PCI DSS Requirement 1.1.3 Establish firewall configuration standards that include: Requirements for a firewall at each Internet connection and between any demilitarized zone (DMZ) and the internal network zone. N/A Verify that there is a firewall installed between the DMZ and internal network in all cases. PCI DSS Requirement 1.1.4 Establish firewall configuration standards that include: Description of groups, roles, and responsibilities for logical management of network components. 1. Login to Sonicwall firewall. 2. Verify and ensure that the source and destination IP s reflect to the degree possible logical combinations of groups. For example, in the screenshot below OPT, LAN and WAN are examples of logical IP groups. 1
Verify grouping of IP addresses whenever possible. 2
PCI DSS Requirement 1.1.6 Establish firewall configuration standards that include: Justification and documentation for any available protocols besides hypertext transfer protocol (HTTP), and secure sockets layer (SSL), secure shell (SSH), and virtual private network (VPN). 1. Login to the SonicWALL firewall. 2. Select the Firewall menu, and select the Access Rules item. 3> Documentation for justification must exist for any services that are allowed to the internal network besides HTTP, SSH, SSL and VPN. 3
PCI DSS Requirement 1.2 Build a firewall configuration that denies all traffic from untrusted networks and hosts, except for protocols necessary for the cardholder data environment. 1. Login to the SonicWALL firewall. 2. Select the Firewall menu, and select the Access Rules item. 3. To edit an existing rule, click on the Configure icon next to that rule or click the Add button to add a new rule. The following window will appear: 4
4. Establish rules which deny all traffic from untrusted networks and hosts. For example, to block all traffic from the Internet, check Deny and select Any from the Service drop down menu. Select Source and Destination from the drop down menus as shown below and click the OK button. 5
5. The new rule will appear in the Access Rules list as seen below. 6
SonicWALL's default policy on its security devices is to have a "denial-all" policy to everything internal to the network. 7
PCI DSS Requirement 1.3.1 Build a firewall configuration that restricts connections between publicly accessible servers and any system component storing cardholder data, including any connections from wireless networks. This firewall configuration should include the following: Restricting inbound Internet traffic to Internet protocol (IP) addresses within the DMZ (ingress filters). N/A Ensure that any of the IP s mentioned above (i.e. wireless and cardholder systems) are adequately protected within the network behind firewall rule-sets. PCI DSS Requirement 1.3.2 Build a firewall configuration that restricts connections between publicly accessible servers and any system component storing cardholder data, including any connections from wireless networks. This firewall configuration should include the following: Not allowing internal addresses to pass from the Internet into the DMZ. N/A Ensure that any of the IP s mentioned above (i.e. wireless and cardholder systems) are adequately protected within the network behind firewall rule-sets. PCI DSS Requirement 1.3.3 Build a firewall configuration that restricts connections between publicly accessible servers and any system component storing cardholder data, including any connections from wireless networks. This firewall configuration should include the following: Implementing stateful inspection, also known as dynamic packet filtering (that is, only established connections are allowed into the network). N/A Ensure that any of the IP s mentioned above (i.e. wireless and cardholder systems) are adequately protected within the network behind firewall rule-sets. 8
PCI DSS Requirement 1.3.4 Build a firewall configuration that restricts connections between publicly accessible servers and any system component storing cardholder data, including any connections from wireless networks. This firewall configuration should include the following: Placing the database in an internal network zone, segregated from the DMZ. N/A Ensure that any of the IP s mentioned above for the database are adequately protected within the network behind firewall rule-sets. PCI DSS Requirement 1.3.5 Build a firewall configuration that restricts connections between publicly accessible servers and any system component storing cardholder data, including any connections from wireless networks. This firewall configuration should include the following: Restricting inbound and outbound traffic to that which is necessary for the cardholder data environment. N/A Ensure that any of the IP s mentioned above (i.e. wireless and cardholder systems) are adequately protected within the network behind firewall rule-sets. PCI DSS Requirement 1.3.6 Build a firewall configuration that restricts connections between publicly accessible servers and any system component storing cardholder data, including any connections from wireless networks. This firewall configuration should include the following: Securing and synchronizing router configuration files. For example, running configuration files (for normal functioning of the routers), and start-up configuration files (when machines are re-booted) should have the same secure configuration. N/A SonicWALL units only keep a single previous configuration file on the native device. Authenticated access is required for viewing, manipulation or exportation. 9
PCI DSS Requirement 1.3.7 Build a firewall configuration that restricts connections between publicly accessible servers and any system component storing cardholder data, including any connections from wireless networks. This firewall configuration should include the following: Denying all other inbound and outbound traffic not specifically allowed. 1. Login to the SonicWALL firewall. 2. Select the Firewall menu, and select the Access Rules item. 3. To edit an existing rule, click on the Configure icon next to that rule or click the Add button to add a new rule. The following window will appear: 10
4. As shown above, select the Deny any rule and click OK. 11
PCI DSS Requirement 1.3.8 Build a firewall configuration that restricts connections between publicly accessible servers and any system component storing cardholder data, including any connections from wireless networks. This firewall configuration should include the following: Installing perimeter firewalls between any wireless networks and the cardholder data environment, and configuring these firewalls to deny any traffic from the wireless environment or from controlling any traffic (if such traffic is necessary for business purposes). 1. Login to the SonicWALL firewall. This firewall should be placed between the cardholder network and other networks. 2. Select the Firewall menu, and select the Access Rules item. 3. To edit an existing rule, click on the Configure icon next to that rule or click the Add button to add a new rule. The following window will appear: 12
4. Establish rules which deny any traffic from the wireless environment or rules which will control wireless traffic (if such traffic is necessary for business purposes). For example, to allow certain traffic from the cardholder data environment to the wireless networks, check Allow and specify allowable services from the Services drop down menu. Also select the Source and Destination from the drop down menus as shown below and click the OK button. SonicWALL Administrator Guide should include this as a Best Practice. 13
PCI DSS Requirement 1.4 Prohibit direct public access between external networks and any system component that stores cardholder data (for example, databases, logs, trace files). N/A SonicWALL firewalls, properly configured, can prohibit direct public access between external networks and any system component that stores cardholder data (for example, databases, logs, trace files). Verify that there is a firewall between network that hosts cardholder data and all other networks. PCI DSS Requirement 1.4.1 Implement a DMZ to filter and screen all traffic and to prohibit direct routes for inbound and outbound Internet traffic. N/A The SonicOS Standard default configuration has a "denial-all" rule from the WAN interface to everything internal to the network. 14
PCI DSS Requirement 1.4.2 Restrict outbound traffic from payment card applications to IP addresses within the DMZ. 1. Login to the SonicWALL firewall. 2. Select the Firewall menu, and select the Access Rules item. 3. To edit an existing rule, click on the Configure icon next to that rule or click the Add button to add a new rule. The following window will appear: 15
4. Establish rules which restrict outbound traffic from payment card applications to IP addresses within the DMZ. For example, to allow outbound traffic to addresses within the DMZ, check Allow and specify allowable services from the Services drop down menu. Also select the Source and Destination from the drop down menus as shown below and click the OK button. 16
PCI DSS Requirement 1.5 Implement IP masquerading to prevent internal addresses from being translated and revealed on the Internet. Use technologies that implement RFC 1918 address space, such as port address translation (PAT) or network address translation (NAT). 1. Login to the SonicWALL firewall. 2. Select the Network menu, and select the Settings item. 3. Select NAT Mode from the drop-down menu. 4. Click the WAN Configure icon. One of the following windows will appear depending upon which NAT mode was selected: NAT Enabled 17
NAT with DHCP Client 18
NAT with PPPoE Client 19
NAT with L2TP Client 20
NAT with PPTP Client 21
5. Configure WAN settings and click the OK button. 6. Once back at the Network>Settings screen, click the Apply button. 22
PCI DSS Requirement 2.1 Always change vendor-supplied defaults before installing a system on the network (for example, include passwords, simple network management protocol (SNMP) community strings, and elimination of unnecessary accounts). 1. Login to the SonicWALL firewall. 2. Select the System menu, and select the Administration item. 3. In the Administrator Name & Password section, assign a password different from the initial supplied default. 4. Scroll to the bottom of the screen and click Enable SNMP. 23
5. Click the Configure button. The following window will appear: 6. Enter SNMP settings and click the OK button. Note that the Community Name should not be defaults like Public or Private. 7. Once back at the System > Administration screen, click the Apply button. 24
PCI DSS Requirement 2.1.1 For wireless environments, change wireless vendor defaults, including but not limited to, wired equivalent privacy (WEP) keys, default service set identifier (SSID), passwords, and SNMP community strings. Disable SSID broadcasts. Enable WiFi protected access (WPA and WPA2) technology for encryption and authentication when WPA-capable. N/A SonicWALL Administrator Guide should include this as a Best Practice. PCI DSS Requirement 2.2 Develop configuration standards for all system components. Assure that these standards address all known security vulnerabilities and are consistent with industry-accepted system hardening standards as defined, for example, by SysAdmin Audit Network Security Network (SANS), National Institute of Standards Technology (NIST), and Center for Internet Security (CIS). N/A SonicWALL Administrator Guide should include this as a Best Practice. PCI DSS Requirement 2.2.3 Configure system security parameters to prevent misuse N/A Enhanced version of SonicWALL OS is recommended for stronger security parameters. 25
PCI DSS Requirement 2.3 Encrypt all non-console administrative access. Use technologies such as SSH, VPN, or SSL/TLS (transport layer security) for web-based management and other non-console administrative access. 1. Login to the SonicWALL firewall. 2. Select the System menu, and select the Administration item. 3. Scroll to the Web Management Settings section. 4. Check HTTPS and disable HTTP. 5. Click Apply. 26
PCI DSS Requirement 5.1 Deploy anti-virus software on all systems commonly affected by viruses (particularly personal computers and servers). 1. To purchase the SonicWALL Client Anti-Virus Upgrade, select the Security Services menu, and select the Client AV Enforcement item. 2. Select the Security Services menu, and select the Gateway Anti-Virus item. 3. Check Enable Gateway Anti-Virus. 27
4. Check Enable Inbound Inspection for HTTP, FTP, IMAP, SMTP and POP3. 5. Click the Settings button to configure Protocol Settings. The following window will appear: 6. Configure protocol settings and click the OK button. 7. Once back at the Security Services>Gateway Anti-Virus screen, click the Configure Gateway AV Settings button. The following window will appear: 28
8. Configure Gateway AV Settings and click the OK button. 9. Once back at the Security Services>Gateway Anti-Virus screen, click the Apply button. Enforce a policy of updating anti-virus signatures regularly. 29
PCI DSS Requirement 5.1.1 Ensure that anti-virus programs are capable of detecting, removing, and protecting against other forms of malicious software, including spyware and adware. SonicWALL Administrator Guide should include this as a Best Practice. PCI DSS Requirement 5.2 Ensure that all anti-virus mechanisms are current, actively running, and capable of generating audit logs. SonicWALL Administrator Guide should include this as a Best Practice. PCI DSS Requirement 6.1 Ensure that all system components and software have the latest vendor-supplied security patches installed. Install relevant security patches within one month of release. Periodically check Mysonicwall.com for security advisories and new firmware availability. SonicWALL Administrator Guide should include this as a Best Practice. 30
PCI DSS Requirement 6.2 Establish a process to identify newly discovered security vulnerabilities (for example, subscribe to alert services freely available on the Internet). Update standards to address new vulnerability issues. Provided via SonicAlert. SonicWALL security services automatically pushes down updates to security devices. SonicWALL Administrator Guide should include this as a Best Practice. PCI DSS Requirement 6.4.4 Follow change control procedures for all system and software configuration changes. The procedures must include the following: Back-out procedures. Provided via SonicAlert. SonicWALL security services automatically pushes down updates to security devices. SonicWALL systems provide at least one back-up configuration. SonicOS Standard provides config backup and restore capabilities. SonicWALL Administrator Guide should include this as a Best Practice. PCI DSS Requirement 8.1 Identify all users with a unique user name before allowing them to access system components or cardholder data. 1. Login to the SonicWALL firewall. 2. Select the User menu, and select the Local Users item. 31
3. Click the Add User button. The following window will appear: 4. Assign a username and password for the new user and check boxes for appropriate access rights. 5. Click the OK button. 6. Please note that no generic id s or shared id s should be used. Please ensure that no generic id s or shared id s should be used. 32
PCI DSS Requirement 8.2 In addition to assigning a unique ID, employ at least one of the following methods to authenticate all users: Password Token devices (e.g., SecureID, certificates, or public key) Biometrics. 1. Login to the SonicWALL firewall. 2. Select the User menu, and select the Local Users item. 3. Click the Add User button. The following window will appear: 33
4. Assign a username and password for the new user and check boxes for appropriate access rights. 5. Click the OK button. 34
PCI DSS Requirement 8.3 Implement two-factor authentication for remote access to the network by employees, administrators, and third parties. Use technologies such as remote authentication and dial-in service (RADIUS) or terminal access controller access control system (TACACS) with tokens; or VPN (based on SSL/TLS or IPSEC) with individual certificates. 1. Login to the SonicWALL firewall. 2. Select the User menu, and select the Local Users item. 3. Check Enable VPN. 4. Click the Add button to add new VPN policies or click the Configure icon to edit an existing policy. The following window will appear: 35
5. Configure the VPN policy and click the OK button. 6. Once back at the VPN>Settings screen, click the Apply button. User-level authentication for remote access through the SonicWALL is supported with local RADIUS LDAP and AD authentication as our 2-factor authentication methods and CA based authentication. SSL-VPN allows for granular access control policies. 36
PCI DSS Requirement 8.4 Encrypt all passwords during transmission and storage on all system components. N/A All passwords will need to be encrypted by SSL/TLS (for management access as already addressed above), the configuration is stored and encoded on the device and requires administrative authentication for view and export. PCI DSS Requirement 8.5.3 Set first-time passwords to a unique value per user and change immediately after first use. N/A SonicWALL products do not enforce a user to specify a unique password after the first login. Beginning with GMS 4.1 and SonicOS 4.0 Enhanced, this feature will be supported. PCI DSS Requirement 8.5.4 Immediately revoke accesses of terminated users N/A SonicWALL Administrator Guide should include this as a Best Practice. 37
PCI DSS Requirement 8.5.5 Remove inactive user accounts at least every 90 days. N/A SonicWALL Administrator Guide should include this as a Best Practice. PCI DSS Requirement 8.5.6 Enable accounts used by vendors for remote maintenance only during the time needed N/A Although this is a best practice, SonicWALL products do not support this feature. If products are used with GMS 4.1 management only, other SonicWALL products under management would not need to have this support. PCI DSS Requirement 8.5.8 Do not use group, shared, or generic accounts and passwords. N/A Although this is a best practice, SonicWALL products do not support this feature. If products are used with GMS 4.1 management only, other SonicWALL products under management would not need to have this support. PCI DSS Requirement 8.5.9 Change user passwords at least every 90 days. N/A 38
Although this is a best practice, SonicWALL products do not support this feature. If products are used with GMS 4.1 management only, other SonicWALL products under management would not need to have this support. PCI DSS Requirement 8.5.10 Require a minimum password length of at least seven characters. N/A Although this is a best practice, SonicWALL products do not support this feature. If products are used with GMS 4.1 management only, other SonicWALL products under management would not need to have this support. PCI DSS Requirement 8.5.11 Use passwords containing both numeric and alphabetic characters. N/A Although this is a best practice, SonicWALL products do not support this feature. If products are used with GMS 4.1 management only, other SonicWALL products under management would not need to have this support. PCI DSS Requirement 8.5.12 Do not allow an individual to submit a new password that is the same as any of the last four passwords he or she has used. N/A Although this is a best practice, SonicWALL products do not support this feature. If products are used with GMS 4.1 management only, other SonicWALL products under management would not need to have this support. 39
PCI DSS Requirement 8.5.13 Limit repeated access attempts by locking out the user ID after not more than six attempts. 1. Login to the SonicWALL firewall. 2. Select the System menu, and select the Administration item. 3. Check Enable Administrator/User Lockout. 4. Enter a value of 6 or less for Failed login attempts per minute before lockout. 5. Enter a value of 30 or more for Lockout Period (minutes). 6. Click the Apply button. 40
PCI DSS Requirement 8.5.14 Set the lockout duration to thirty minutes or until administrator enables the user ID. 1. Login to the SonicWALL firewall. 2. Select the System menu, and select the Administration item. 3. Check Enable Administrator/User Lockout. 4. Enter a value of 6 or less for Failed login attempts per minute before lockout. 5. Enter a value of 30 or more for Lockout Period (minutes). 6. Click the Apply button. PCI DSS Requirement 8.5.15 If a session has been idle for more than 15 minutes, require the user to re-enter the password to re-activate the terminal. 1. Login to the SonicWALL firewall. 2. Select the System menu, and select the Administration item. 41
3. Enter a value of 15 or less for Log out Administrator after inactivity of (minutes). 4. Click the Apply button. 5. Select the Users menu, and select the Settings item. 6. Enter a value of 15 or less for Inactivity timeout (minutes). 7. Click the Apply button. 42
PCI DSS Requirement 10.1 Establish a process for linking all access to system components (especially access done with administrative privileges such as root) to each individual user. 1. Login to the SonicWALL firewall. 2. Select the User menu, and select the Local Users item. 3. Click the Add User button. The following window will appear: 43
4. Assign a username and password for the new user and check boxes for appropriate access rights. 5. Click the OK button. 6. Ensure that id s are not generic or shared. Ensure that id s are not generic or shared. 44
PCI DSS Requirement 10.2.1 Implement automated audit trails for all system components to reconstruct the following events: All individual user accesses to cardholder data. 1. Login to the SonicWALL firewall. 2. Select the Log menu, and select the Categories item. 3. Check System Maintenance and User Activity. 4. Click the Apply button. 45
PCI DSS Requirement 10.2.2 Implement automated audit trails for all system components to reconstruct the following events: All actions taken by any individual with root or administrative privileges. 1. Login to the SonicWALL firewall. 2. Select the Log menu, and select the Categories item. 3. Check System Maintenance and User Activity. 4. Click the Apply button. 46
PCI DSS Requirement 10.2.3 Implement automated audit trails for all system components to reconstruct the following events: Access to all audit trails. 1. Login to the SonicWALL firewall. 2. Select the Log menu, and select the Categories item. 3. Check User Activity. 4. Click the Apply button. 47
PCI DSS Requirement 10.2.4 Implement automated audit trails for all system components to reconstruct the following events: Invalid logical access attempts. 1. Login to the SonicWALL firewall. 2. Select the Log menu, and select the Categories item. 3. Check User Activity. 4. Click the Apply button. 48
PCI DSS Requirement 10.2.5 Implement automated audit trails for all system components to reconstruct the following events: Use of identification and authentication mechanisms 1. Login to the SonicWALL firewall. 2. Select the Log menu, and select the Categories item. 3. Check User Activity and Attacks. 4. Click the Apply button. 49
PCI DSS Requirement 10.2.6 Implement automated audit trails for all system components to reconstruct the following events: Initialization of the audit logs. 1. Login to the SonicWALL firewall. 2. Select the Log menu, and select the Categories item. 3. Check System Maintenance and User Activity. 4. Click the Apply button. 50
PCI DSS Requirement 10.2.7 Implement automated audit trails for all system components to reconstruct the following events: Creation and deletion of system-level objects. 1. Login to the SonicWALL firewall. 2. Select the Log menu, and select the Categories item. 3. Check User Activity. 4. Click the Apply button. 51
PCI DSS Requirement 10.3.1 Record at least the following audit trail entries for each event for all system components: User identification. 1. Login to the SonicWALL firewall. 2. Select the Log menu, and select the Automation item. 3. Scroll down to the Syslog Servers section. 4. Set the Syslog Format to Default using the drop-down menu. 5. In the Server Name section, click the Add button. The following window will appear: 6. Enter the Name or IP Address and Port for the syslog server and click the OK button. 7. Once back at the Log>Automation screen, click the Apply button. Event logging to a centralized syslog console. 52
PCI DSS Requirement 10.3.2 Record at least the following audit trail entries for each event for all system components: Type of event. 1. Login to the SonicWALL firewall. 2. Select the Log menu, and select the Automation item. 3. Scroll down to the Syslog Servers section. 4. Set the Syslog Format to Default using the drop-down menu. 5. In the Server Name section, click the Add button. The following window will appear: 6. Enter the Name or IP Address and Port for the syslog server and click the OK button. 7. Once back at the Log>Automation screen, click the Apply button. Event logging to a centralized syslog console. 53
PCI DSS Requirement 10.3.3 Record at least the following audit trail entries for each event for all system components: Date and time. 1. Login to the SonicWALL firewall. 2. Select the Log menu, and select the Automation item. 3. Scroll down to the Syslog Servers section. 4. Set the Syslog Format to Default using the drop-down menu. 5. In the Server Name section, click the Add button. The following window will appear: 6. Enter the Name or IP Address and Port for the syslog server and click the OK button. 7. Once back at the Log>Automation screen, click the Apply button. Event logging to a centralized syslog console. 54
PCI DSS Requirement 10.3.4 Record at least the following audit trail entries for each event for all system components: Success or failure indication. 1. Login to the SonicWALL firewall. 2. Select the Log menu, and select the Automation item. 3. Scroll down to the Syslog Servers section. 4. Set the Syslog Format to Default using the drop-down menu. 5. In the Server Name section, click the Add button. The following window will appear: 6. Enter the Name or IP Address and Port for the syslog server and click the OK button. 7. Once back at the Log>Automation screen, click the Apply button. Event logging to a centralized syslog console. 55
PCI DSS Requirement 10.3.5 Record at least the following audit trail entries for each event for all system components: Origination of event. 1. Login to the SonicWALL firewall. 2. Select the Log menu, and select the Automation item. 3. Scroll down to the Syslog Servers section. 4. Set the Syslog Format to Default using the drop-down menu. 5. In the Server Name section, click the Add button. The following window will appear: 6. Enter the Name or IP Address and Port for the syslog server and click the OK button. 7. Once back at the Log>Automation screen, click the Apply button. Event logging to a centralized syslog console. 56
PCI DSS Requirement 10.3.6 Record at least the following audit trail entries for each event for all system components: Identity or name of affected data, system component, or resource. 1. Login to the SonicWALL firewall. 2. Select the Log menu, and select the Automation item. 3. Scroll down to the Syslog Servers section. 4. Set the Syslog Format to Default using the drop-down menu. 5. In the Server Name section, click the Add button. The following window will appear: 6. Enter the Name or IP Address and Port for the syslog server and click the OK button. 7. Once back at the Log>Automation screen, click the Apply button. Event logging to a centralized syslog console. 57
PCI DSS Requirement 10.4 Synchronize all critical system clocks and times. 1. Login to the SonicWALL firewall. 2. Select the System menu, and select the Time item. 3. Check Set Time Automatically using NTP. 4. Click the Add button in the NTP Server section at the bottom of the page. The following window will appear: 5. Enter the NTP Server IP address and click OK. 6. Click the Apply button. 58
PCI DSS Requirement 10.5.1 Secure audit trails so they cannot be altered, including the following: Limit viewing of audit trails to those with a job-related need. SonicWALL Administrator Guide should include this as a Best Practice. PCI DSS Requirement 10.5.2 Secure audit trails so they cannot be altered, including the following: Protect audit trail files from unauthorized modifications. : Secure audit trails by limiting access to the firewall. 59
PCI DSS Requirement 10.5.3 Secure audit trails so they cannot be altered, including the following: Promptly back-up audit trail files to a centralized log server or media that is difficult to alter. 1. Login to the SonicWALL firewall. 2. Select the Log menu, and select the Automation item. 3. Scroll down to the Syslog Servers section and make sure you set the send log functionality as frequent as possible. 4. Set the Syslog Format to Default using the drop-down menu. 5. In the Server Name section, click the Add button. The following window will appear: 6. Enter the Name or IP Address and Port for the syslog server and click the OK button. 7. Once back at the Log>Automation screen, click the Apply button. Verify that access to the target syslog server where all events are getting recorded is adequate. 60
PCI DSS Requirement 10.5.4 Copy logs for wireless networks onto a log server on the internal LAN. N/A SonicWALL Administrator Guide should include this as a Best Practice. PCI DSS Requirement 10.5.5 Use file integrity monitoring and change detection software on logs to ensure that existing log data cannot be changed without generating alerts (although new data being added should not cause an alert). N/A SonicWALL Administrator Guide should include this as a Best Practice. PCI DSS Requirement 10.6 Review logs for all system components at least daily. Log reviews must include those servers that perform security functions like intrusion detection system (IDS) and authentication, authorization, and accounting protocol (AAA) servers (for example, RADIUS). N/A SonicWALL Administrator Guide should include this as a Best Practice. 61
PCI DSS Requirement 10.7 Retain audit trail history for at least one year, with a minimum of three months online availability. 1. Login to the SonicWALL firewall. 2. Select the Log menu, and select the Automation item. 3. Scroll down to the Syslog Servers section. 4. Set the Syslog Format to Default using the drop-down menu. 5. In the Server Name section, click the Add button. The following window will appear: 6. Enter the Name or IP Address and Port for the syslog server and click the OK button. 7. Once back at the Log>Automation screen, click the Apply button. SonicWALL firewalls support transferring of all log files to a configured syslog server. Ensure that the syslog server has enough hard disk size to store GMS server logs for at least three months online. 62
PCI DSS Requirement 11.4 Use network intrusion detection systems, host-based intrusion detection systems, and intrusion prevention systems to monitor all network traffic and alert personnel to suspected compromises. Keep all intrusion detection and prevention engines up-to-date. 1. Login to the SonicWALL firewall. 2. Select the Security Services menu, and select the Intrusion Prevention item. 3. Check Enable IPS and check the interface for which you are enabling IPS (WAN, LAN, and/or OPT). 4. Check Prevent All for High Priority Attacks, Medium Priority Attacks & Low Priority Attacks. 5. Click the Apply button. 6. To exclude specific IP addresses, click the Configure IPS Settings button. The following window will appear: 63
7. Check Enable IPS Exclusion List. 8. Click the Add button. The following window will appear: 9. Complete the IP Address From and IP Address To fields and click the OK button. Enforce a policy of keeping all intrusion detection and prevention engines up-to-date. 64
PCI DSS Requirement 11.5 Deploy file integrity monitoring software to alert personnel to unauthorized modification of critical system or content files; and configure the software to perform critical file comparisons at least weekly. N/A SonicWALL Administrator Guide should include this as a Best Practice. 65
PCI DSS Requirement 12.5.2 Monitor and analyze security alerts and information, and distribute to appropriate personnel. 1. Login to the SonicWALL firewall. 2. Select the Log menu, and select the Automation item. 3. Enter the email address that will be receiving alerts in the Send Alerts to E-mail Address field. Also enter the IP address and email address of the mail server in the Mail Server Settings section. 4. Click the Apply button. 66
PCI DSS Requirement 12.5.5 Monitor and control all access to data. 1. Login to the SonicWALL firewall. 2. Select the Log menu, and select the Categories item. 3. Check System Maintenance and User Activity. 4. Click the Apply button. Also ensure, that access to the management console is limited to specific named users. 67