Restricted Data Security Standards Worksheet

1 BUILD AND MAINTAIN A SECURE NETWORK

1.1 Install and maintain a firewall configuration to protect restricted data	Req 1
Firewalls are computer devices that control computer traffic allowed into and out of a company’s network, as well as traffic into more sensitive areas within a company’s internal network. A firewall examines all network traffic and blocks those transmissions that do not meet the specified security criteria. All systems must be protected from unauthorized access from the Internet, whether entering the system as e-commerce, employees’ Internet-based access through desktop browsers, or employees’ e-mail access. Often, seemingly insignificant paths to and from the Internet can provide unprotected pathways into key systems. Firewalls are a key protection mechanism for any computer network.

1.1.1 Establish firewall configuration standards that include the following:

1.1

SC-1

1.1.1.1 A formal process for approving and testing all external network connections and changes to the firewall configuration

1.1.1

SC-1

1.1.1.2 A current network diagram with all connections to restricted data, including any wireless networks

1.1.2

---

1.1.1.3 Requirements for a firewall at each Internet connection and between any demilitarized zone (DMZ) and the internal network zone

1.1.3

SC-2

1.1.1.4 Description of groups, roles, and responsibilities for logical management of network components

1.1.4

SC-1

1.1.1.5 Documented list of services and ports necessary for business

1.1.5

SC-1

1.1.1.6 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.1.6

SC-1

1.1.1.7 Justification and documentation for any risky protocols allowed (for example, file transfer protocol (FTP), which includes reason for use of protocol and security features implemented

1.1.7

SC-1

1.1.1.8 Quarterly review of firewall and router rule sets

1.1.8

SC-1

1.1.1.9 Configuration standards for routers.

1.1.9

SC-1

1.1.2 Build a firewall configuration that denies all traffic from “untrusted” networks and hosts, except for protocols necessary for the restricted data environment.

1.2

SC-7

1.1.3 Build a firewall configuration that restricts connections between publicly accessible servers and any system component storing restricted data, including any connections from wireless networks. This firewall configuration should include the following:

1.3

SC-7

1.1.3.1 Restricting inbound Internet traffic to Internet protocol (IP) addresses within the DMZ (ingress filters)

1.3.1

1.1.3.2 Not allowing internal addresses to pass from the Internet into the DMZ

1.3.2

1.1.3.3 Implementing stateful inspection, also known as dynamic packet filtering (that is, only ”established” connections are allowed into the network)

1.3.3

1.1.3.4 Placing the database in an internal network zone, segregated from the DMZ

1.3.4

1.1.3.5 Restricting inbound and outbound traffic to that which is necessary for the restricted data environment

1.3.5

1.1.3.6 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 Payment Card Industry (PCI) Data Security Standard

1.3.6

1.1.3.7 Denying all other inbound and outbound traffic not specifically allowed

1.3.7

1.1.3.8 Denial of Service Protection

SC-5

1.1.3.9 Installing perimeter firewalls between any wireless networks and the restricted 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.3.8

1.1.3.10 Installing personal firewall software on any mobile and employee-owned computers with direct connectivity to the Internet (for example, laptops used by employees), which are used to access the organization’s network.

1.3.9

1.1.4 Prohibit direct public access between external networks and any system component that stores restricted data (for example, databases, logs, trace files).

1.4

SC-7

1.1.4.1 Implement a DMZ to filter and screen all traffic and to prohibit direct routes for inbound and outbound Internet traffic

1.4.1

1.1.4.2 Restrict outbound traffic from payment card applications to IP addresses within the DMZ.

1.4.2

1.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.5

SC-20-22

1.2 Do not use vendor-supplied defaults for system passwords and other security parameters	Req 2
Hackers (external and internal to a company) often use vendor default passwords and other vendor default settings to compromise systems. These passwords and settings are well known in hacker communities and easily determined via public information.

1.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).

2.1

CM-2

1.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

2.1.1

1.2.2 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.

2.2

CM-1-8

1.2.2.1 Implement only one primary function per server (for example, web servers, database servers, and DNS should be implemented on separate servers)

2.2.1

CM-6

1.2.2.2 Disable all unnecessary and insecure services and protocols (services and protocols not directly needed to perform the devices’ specified function)

2.2.2

CM-7

1.2.2.3 Configure system security parameters to prevent misuse

2.2.3

CM-5

1.2.2.4 Remove all unnecessary functionality, such as scripts, drivers, features, subsystems, file systems, and unnecessary web servers.

2.2.4

CM-6

1.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.

2.3

IA-7

1.2.4 Hosting providers must protect each entity’s hosted environment and data. These providers must meet specific requirements as detailed in Appendix A: “PCI DSS Applicability for Hosting Providers.”

2.4

SA-9

2 PROTECT RESTRICTED DATA

2.1 Protect stored restricted data	Req 3
Encryption is a critical component of restricted data protection. If an intruder circumvents other network security controls and gains access to encrypted data, without the proper cryptographic keys, the data is unreadable and unusable to that person. Other effective methods of protecting stored data should be considered as potential risk mitigation opportunities. For example, methods for minimizing risk include not storing restricted data unless absolutely necessary, truncating restricted data if full PAN is not needed, and not sending PAN in unencrypted e-mails.

2.1.1 Keep restricted data storage to a minimum. Develop a data retention and disposal policy. Limit storage amount and retention time to that which is required for business, legal, and/or regulatory purposes, as documented in the data retention policy.

3.1

MP-3; MP-6

2.1.2 Do not store sensitive authentication data subsequent to authorization (even if encrypted). Sensitive authentication data includes the data as cited in the following Requirements:

3.2

PCI Specific

2.1.2.1 Do not store the full contents of any track from the magnetic stripe (that is on the back of a card, in a chip or elsewhere). This data is alternatively called full track, track, track 1, track 2, and magnetic stripe data In the normal course of business, the following data elements from the magnetic stripe may need to be retained: the accountholder’s name, primary account number (PAN), expiration date, and service code. To minimize risk, store only those data elements needed for business. NEVER store the card verification code or value or PIN verification value data elements. Note: See “Glossary” for additional information.

3.2.1

PCI Specific

2.1.2.2 Do not store the card-validation code or value (three-digit or four-digit number printed on the front or back of a payment card) used to verify card-not-present transactions Note: See “Glossary” for additional information.

3.2.2

PCI Specific

2.1.2.3 Do not store the personal identification number (PIN) or the encrypted PIN block.

3.2.3

2.1.3 Mask elements of restricted data (EXAMPLES: PAN for PCI ( the first six and last four digits are the maximum number of digits to be displayed); masking SSN (all but the last four digits); masking DOB, mask year)

3.3

MP-2

2.1.4 Render restricted data such as Social Security Numbers (SSN) or Credit Card Numbers, at minimum, unreadable anywhere it is stored (including data on portable digital media, backup media, in logs, and data received from or stored by wireless networks) by using any of the following approaches (Note: If for some reason, a company is unable to encrypt restricted data, refer to Appendix B: “Compensating Controls for Encryption of Stored Data.”):

3.4

MP-4

2.1.4.1 Strong one-way hash functions (hashed indexes)

MP-4 --> FIPS199

2.1.4.2 Truncation

MP-4 --> FIPS199

2.1.4.3 Index tokens and pads (pads must be securely stored)

MP-4 --> FIPS199

2.1.4.4 Strong cryptography with associated key management processes and procedures.

MP-4 --> FIPS199

2.1.4.5 The MINIMUM account information that must be rendered unreadable such as the PAN.

MP-4 --> FIPS199

2.1.4.6 If disk encryption is used (rather than file- or column-level database encryption), logical access must be managed independently of native operating system access control mechanisms (for example, by not using local system or Active Directory accounts). Decryption keys must not be tied to user accounts.

3.4.1

MP-4 --> FIPS199

2.1.5 Protect encryption keys used for encryption of restricted data against both disclosure and misuse.

3.5

SC-12

2.1.5.1 Restrict access to keys to the fewest number of custodians necessary

3.5.1

IA-7 --> FIPS140-x

2.1.5.2 Store keys securely in the fewest possible locations and forms.

3.5.2

IA-7 --> FIPS140-x

2.1.6 Fully document and implement all key management processes and procedures for keys used for encryption of restricted data, including the following:

3.6

SC-13/FIPS140

2.1.6.1 Generation of strong keys

3.6.1

SC-13-->FIPS140

2.1.6.2 Secure key distribution

3.6.2

SC-13-->FIPS140

2.1.6.3 Secure key storage

3.6.3

SC-13-->FIPS140

2.1.6.4 Periodic changing of keys • As deemed necessary and recommended by the associated application (for example, re-keying); preferably automatically At least annually.

3.6.4

SC-13-->FIPS140

2.1.6.5 Destruction of old keys

3.6.5

SC-13-->FIPS140

2.1.6.6 Split knowledge and establishment of dual control of keys (so that it requires two or three people, each knowing only their part of the key, to reconstruct the whole key)

3.6.6

SC-13-->FIPS140

2.1.6.7 Prevention of unauthorized substitution of keys

3.6.7

SC-13-->FIPS140

2.1.6.8 Replacement of known or suspected compromised keys

3.6.8

SC-13-->FIPS140

2.1.6.9 Revocation of old or invalid keys

3.6.9

SC-13-->FIPS140

2.1.6.10 Requirement for key custodians to sign a form stating that they understand and accept their key-custodian responsibilities.

3.6.10

SC-13-->FIPS140

2.2 Encrypt transmission of restricted data across open, public networks	Req 4
Sensitive information must be encrypted during transmission over networks that are easy and common for a hacker to intercept, modify, and divert data while in transit.

2.2.1 Use strong cryptography and security protocols such as secure sockets layer (SSL) / transport layer security (TLS) and Internet protocol security (IPSEC) to safeguard sensitive restricted data during transmission over open, public networks. Examples of open, public networks that are in scope of the PCI DSS are the Internet, WiFi (IEEE 802.11x), global system for mobile communications (GSM), and general packet radio service (GPRS).

4.1

MP-5; SC-8-9

2.2.1.1 For wireless networks transmitting restricted data, encrypt the transmissions by using WiFi protected access (WPA or WPA2) technology, IPSEC VPN, or SSL/TLS. Never rely exclusively on wired equivalent privacy (WEP) to protect confidentiality and access to a wireless LAN. If WEP is used, do the following:

4.1.1

2.2.1.1.1 Use with a minimum 104-bit encryption key and 24 bit-initialization value

2.2.1.1.2 Use ONLY in conjunction with WiFi protected access (WPA or WPA2) technology, VPN, or SSL/TLS

2.2.1.1.3 Rotate shared WEP keys quarterly (or automatically if the technology permits)

2.2.1.1.4 Rotate shared WEP keys whenever there are changes in personnel with access to keys

2.2.1.1.5 Restrict access based on media access code (MAC) address.

2.2.2 Never send unencrypted restricted data, such as credit card PANs or SSNs, by e-mail.

4.2

MP-5

3 MAINTAIN A VULNERABILITY MANAGEMENT PROGRAM

3.1 Use and regularly update anti-virus software or programs	Req 5
Many vulnerabilities and malicious viruses enter the network via employees’ e-mail activities. Anti-virus software must be used on all systems commonly affected by viruses to protect systems from malicious software.

3.1.1 Deploy anti-virus software on all systems commonly affected by viruses (particularly personal computers and servers) Note: Systems commonly affected by viruses typically do not include UNIX-based operating systems or mainframes.

5.1

SI-3 (1)

3.1.1.1 Ensure that anti-virus programs are capable of detecting, removing, and protecting against other forms of malicious software, including spyware and adware.

5.1.1

3.1.2 Ensure that all anti-virus mechanisms are current, actively running, and capable of generating audit logs.

5.2

SI-3 (2)

3.2 Develop and maintain secure systems and applications	Req 6
Unscrupulous individuals use security vulnerabilities to gain privileged access to systems. Many of these vulnerabilities are fixed by vendor-provided security patches. All systems must have the most recently released, appropriate software patches to protect against exploitation by employees, external hackers, and viruses. Note: Appropriate software patches are those patches that have been evaluated and tested sufficiently to determine that the patches do not conflict with existing security configurations. For in-house developed applications, numerous vulnerabilities can be avoided by using standard system development processes and secure coding techniques.

3.2.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.

6.1

MA-1-6

3.2.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.

6.2

SI-2

3.2.3 Develop software applications based on industry best practices and incorporate information security throughout the software development life cycle.

6.3

SA-3; MA-1-6

3.2.3.1 Testing of all security patches and system and software configuration changes before deployment

6.3.1

3.2.3.2 Separate development, test, and production environments

6.3.2

3.2.3.3 Separation of duties between development, test, and production environments

6.3.3

3.2.3.4 Restricted data (ex: PANs, SSN, etc.) are not used for testing or development

6.3.4

3.2.3.5 Removal of test data and accounts before production systems become active

6.3.5

3.2.3.6 Removal of custom application accounts, usernames, and passwords before applications become active or are released to customers

6.3.6

3.2.3.7 Review of custom code prior to release to production or customers in order to identify any potential coding vulnerability.

6.3.7

3.2.4 Follow change control procedures for all system and software configuration changes. The procedures must include the following:

6.4

CM-1-6; SI-2

3.2.4.1 Documentation of impact

6.4.1

3.2.4.2 Management sign-off by appropriate parties

6.4.2

3.2.4.3 Testing of operational functionality

6.4.3

3.2.4.4 Back-out procedures

6.4.4

3.2.5 Develop all web applications based on secure coding guidelines such as the Open Web Application Security Project guidelines. Review custom application code to identify coding vulnerabilities. Cover prevention of common coding vulnerabilities in software development processes, to include the following:

6.5

SA-10-11

3.2.5.1 Unvalidated input

6.5.1

3.2.5.2 Broken access control (for example, malicious use of user IDs)

6.5.2

3.2.5.3 Broken authentication and session management (use of account credentials and session cookies)

6.5.3

3.2.5.4 Cross-site scripting (XSS) attacks

6.5.4

3.2.5.5 Buffer overflows

6.5.5

3.2.5.6 Injection flaws (for example, structured query language (SQL) injection)

6.5.6

3.2.5.7 Improper error handling

6.5.7

3.2.5.8 Insecure storage

6.5.8

3.2.5.9 Denial of service

6.5.9

SC-5

3.2.5.10 Insecure configuration management

6.5.10

3.2.6 Ensure that all web-facing applications are protected against known attacks by applying either of the following methods:

6.6

SA-8

3.2.6.1 Having all custom application code reviewed for common vulnerabilities by an organization that specializes in application security

3.2.6.2 Installing an application layer firewall in front of web-facing applications. (NOTE: This method is considered a best practice until June 30, 2008, after which it becomes a requirement.)

4 IMPLEMENT STRONG ACCESS CONTROL MEASURES

4.1 Restrict access to restricted data by business need-to-know	Req 7
This requirement ensures critical data can only be accessed by authorized personnel.

4.1.1 Limit access to computing resources and restricted information only to those individuals whose job requires such access.

7.1

AC-6

4.1.2 Establish a mechanism for systems with multiple users that restricts access based on a user’s need to know and is set to “deny all” unless specifically allowed.

7.2

AC-6

4.2 Assign a unique ID to each person with computer access	Req 8
Identify all users with a unique user name before allowing them to access system components or restricted data.

4.2.1 Identify all users with a unique user name before allowing them to access system components or restricted data.

8.1

IA-2

4.2.2 In addition to assigning a unique ID, employ at least one of the following methods to authenticate all users: (a) Password; (b) Token devices (e.g., SecureID, certificates, or public key); (c) Biometrics.

8.2

IA-2; AC-14; AC-17

4.2.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.

8.3

IA-2; IA-7

4.2.4 Encrypt all passwords during transmission and storage on all system components.

8.4

IA-7

4.2.5 Ensure proper user authentication and password management for non-consumer users and administrators on all system components as follows:

8.5

IA-5

4.2.5.1 Control addition, deletion, and modification of user IDs, credentials, and other identifier objects

8.5.1

AC-2

4.2.5.2 Verify user identity before performing password resets

8.5.2

IA-4

4.2.5.3 Set first-time passwords to a unique value for each user and change immediately after the first use

8.5.3

AC-1

4.2.5.4 Immediately revoke access for any terminated users

8.5.4

AC-2

4.2.5.5 Remove inactive user accounts at least every 90 days

8.5.5

AC-2

4.2.5.6 Enable accounts used by vendors for remote maintenance only during the time period needed

8.5.6

AC-12; AC-17

4.2.5.7 Communicate password procedures and policies to all users who have access to restricted data

8.5.7

AC-8

4.2.5.8 Do not use group, shared, or generic accounts and passwords

8.5.8

AC-2

4.2.5.9 Change user passwords at least every 90 days

8.5.9

AC-1

4.2.5.10 Passwords chosen must: (a) be a minimum of eight (8) characters in length; (b) be memorized; (c) if a password is written down it must be secure contain at least one (1) character from three (3) of the following categories: Uppercase letter (A-Z), Lowercase letter (a-z), Digit (0-9) and/or contain special characters (~`!@#$%^&*()+=_-{}[]\|:;”’?/<>,.), (d) be private, And passwords chosen must not contain a common proper name, login ID, email address, initials, first, middle or last name.	8.5.10/11	IA-5
This item has been modified to reflect the "Policy and Practices for a Baseline Password Standard for UW-Madison"

4.2.5.11 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

8.5.12

IA-5

4.2.5.12 Limit repeated access attempts by locking out the user ID after not more than six attempts

8.5.13

AC-7

4.2.5.13 Set the lockout duration to thirty minutes or until administrator enables the user ID

8.5.14

AC-7

4.2.5.14 If a session has been idle for more than 15 minutes, require the user to re-enter the password to re-activate the terminal

8.5.15

AC-12

4.2.5.15 Authenticate all access to any database containing restricted data. This includes access by applications, administrators, and all other users

8.5.16

AC-1

4.3 Restrict physical access to restricted data	Req 9
Any physical access to data or systems that house restricted data provides the opportunity for individuals to access devices or data and to remove systems or hardcopies, and should be appropriately restricted.

4.3.1 Use appropriate facility entry controls to limit and monitor physical access to systems that store, process, or transmit restricted data.

9.1

PE-6

4.3.1.1 Use cameras to monitor sensitive areas. Audit collected data and correlate with other entries. Store for at least three months, unless otherwise restricted by law

9.1.1

4.3.1.2 Restrict physical access to publicly accessible network jacks

9.1.2

4.3.1.3 Restrict physical access to wireless access points, gateways, and handheld devices.

9.1.3

4.3.2 Develop procedures to help all personnel easily distinguish between employees and visitors, especially in areas where restricted data is accessible. “Employee” refers to full-time and part-time employees, temporary employees and personnel, and consultants who are “resident” on the entity’s site. A “visitor” is defined as a vendor, guest of an employee, service personnel, or anyone who needs to enter the facility for a short duration, usually not more than one day.

9.2

PE-6

4.3.3 Make sure all visitors are handled as follows:

9.3

PE-7

4.3.3.1 Authorized before entering areas where restricted data is processed or maintained

9.3.1

4.3.3.2 Given a physical token (for example, a badge or access device) that expires and that identifies the visitors as non-employees

9.3.2

4.3.3.3 Asked to surrender the physical token before leaving the facility or at the date of expiration.

9.3.3

4.3.4 Use a visitor log to maintain a physical audit trail of visitor activity. Retain this log for a minimum of three months, unless otherwise restricted by law.

9.4

PE-8

4.3.5 Store media back-ups in a secure location, preferably in an off-site facility, such as an alternate or backup site, or a commercial storage facility.

9.5

CP-9

4.3.6 Physically secure all paper and electronic media (including computers, electronic media, networking and communications hardware, telecommunication lines, paper receipts, paper reports, and faxes) that contain restricted data.

9.6

MP-2

4.3.7 Maintain strict control over the internal or external distribution of any kind of media that contains restricted data including the following:

9.7

MP-1

4.3.7.1 Classify the media so it can be identified as confidential

9.7.1

4.3.7.2 Send the media by secured courier or other delivery method that can be accurately tracked.

9.7.2

4.3.8 Ensure management approves any and all media that is moved from a secured area (especially when media is distributed to individuals).

9.8

MP-1

4.3.9 Maintain strict control over the storage and accessibility of media that contains restricted data.

9.9

MP-1

4.3.9.1 Properly inventory all media and make sure it is securely stored.

9.9.1

4.3.10 Destroy media containing restricted data when it is no longer needed for business or legal reasons as follows:

9.10

MP-6

4.3.10.1 Cross-cut shred, incinerate, or pulp hardcopy materials

9.10.1

4.3.10.2 Purge, degauss, shred, or otherwise destroy electronic media so that restricted data cannot be reconstructed.

9.10.2

5 REGULARLY MONITOR AND TEST NETWORKS

5.1 Track and monitor all access to network resources and restricted data	Req 10
Logging mechanisms and the ability to track user activities are critical. The presence of logs in all environments allows thorough tracking and analysis if something does go wrong. Determining the cause of a compromise is very difficult without system activity logs.

5.1.1 Establish a process for linking all access to system components (especially access done with administrative privileges such as root) to each individual user.

10.1

AC-13

5.1.2 Implement automated audit trails for all system components to reconstruct the following events:

10.2

AU-1-11

5.1.2.1 All individual user accesses to restricted data

10.2.1

5.1.2.2 All actions taken by any individual with root or administrative privileges

10.2.2

5.1.2.3 Access to all audit trails

10.2.3

5.1.2.4 Invalid logical access attempts

10.2.4

5.1.2.5 Use of identification and authentication mechanisms

10.2.5

5.1.2.6 Initialization of the audit logs

10.2.6

5.1.2.7 Creation and deletion of system-level objects.

10.2.7

5.1.3 Record at least the following audit trail entries for all system components for each event:

10.3

AU-1-11

5.1.3.1 User identification

10.3.1

5.1.3.2 Type of event

10.3.2

5.1.3.3 Date and time

10.3.3

5.1.3.4 Success or failure indication

10.3.4

5.1.3.5 Origination of event

10.3.5

5.1.3.6 Identity or name of affected data, system component, or resource.

10.3.6

5.1.4 Synchronize all critical system clocks and times.

10.4

AU-8

5.1.5 Secure audit trails so they cannot be altered.

10.5

AU-9

5.1.5.1 Limit viewing of audit trails to those with a job-related need

10.5.1

5.1.5.2 Protect audit trail files from unauthorized modifications

10.5.2

5.1.5.3 Promptly back-up audit trail files to a centralized log server or media that is difficult to alter

10.5.3

5.1.5.4 Copy logs for wireless networks onto a log server on the internal LAN.

10.5.4

5.1.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).

10.5.5

5.1.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). Note: Log harvesting, parsing, and alerting tools may be used to achieve compliance with Requirement 10.6.

10.6

AU-6

5.1.7 Retain audit trail history for at least one year, with a minimum of three months online availability.

10.7

AU-11

5.2 Regularly test security systems and processes	Req 11
Vulnerabilities are being discovered continually by hackers and researchers, and being introduced by new software. Systems, processes, and custom software should be tested frequently to ensure security is maintained over time and with any changes in software.

5.2.1 Test security controls, limitations, network connections, and restrictions annually to assure the ability to adequately identify and to stop any unauthorized access attempts. Use a wireless analyzer at least quarterly to identify all wireless devices in use.

11.1

SI-6; SA-11

5.2.2 Run internal and external network vulnerability scans at least quarterly and after any significant change in the network (such as new system component installations, changes in network topology, firewall rule modifications, product upgrades). Note: Quarterly external vulnerability scans must be performed by a scan vendor qualified by the payment card industry. Scans conducted after network changes may be performed by the company’s internal staff.