[READ-ONLY] Archives

Topic	Views	Activity
[PCI DSS 3.0] 6.1 Establish a process to identify security vulnerabilities, using reputable outside sources for se Maintain a Vulnerability Management Program (Requi requirement-6:-devel	2549	September 22, 2014
[PCI DSS 3.0] 5.4 Ensure that security policies and operational procedures for protecting systems against malware Maintain a Vulnerability Management Program (Requi requirement-5:-prote	1835	September 22, 2014
[PCI DSS 3.0] 5.3 Ensure that anti-virus mechanisms are actively running and cannot be disabled or altered by user Maintain a Vulnerability Management Program (Requi requirement-5:-prote	1661	September 22, 2014
[PCI DSS 3.0] 5.2 Ensure that all anti-virus mechanisms are maintained as follows: Maintain a Vulnerability Management Program (Requi requirement-5:-prote	2257	September 22, 2014
[PCI DSS 3.0] 5.1.2 For systems considered to be not commonly affected by malicious software, perform periodic eva Maintain a Vulnerability Management Program (Requi requirement-5:-prote	2797	September 22, 2014
[PCI DSS 3.0] 5.1.1 Ensure that anti-virus programs are capable of detecting, removing, and protecting against all Maintain a Vulnerability Management Program (Requi requirement-5:-prote	1643	September 22, 2014
[PCI DSS 3.0] 5.1 Deploy anti-virus software on all systems commonly affected by malicious software (particularly Maintain a Vulnerability Management Program (Requi requirement-5:-prote	1432	September 22, 2014
[PCI DSS 3.0] 4.3 Ensure that security policies and operational procedures for encrypting transmissions of cardhol Protect Cardholder Data (Requirements 3-4) requirement-4:-encry	3261	September 22, 2014
[PCI DSS 3.0] 4.2 Never send unprotected PANs by end-user messaging technologies (for example, e-mail, instant mes Protect Cardholder Data (Requirements 3-4) requirement-4:-encry	3752	September 22, 2014
[PCI DSS 3.0] 4.1.1 Ensure wireless networks transmitting cardholder data or connected to the cardholder data envi Protect Cardholder Data (Requirements 3-4) requirement-4:-encry	1619	September 22, 2014
[PCI DSS 3.0] 4.1 Use strong cryptography and security protocols (for example, SSL/TLS, IPSEC, SSH, etc.) to safeg Protect Cardholder Data (Requirements 3-4) requirement-4:-encry	3821	September 22, 2014
[PCI DSS 3.0] 3.7 Ensure that security policies and operational procedures for protecting stored cardholder data a Protect Cardholder Data (Requirements 3-4) requirement-3:-prote	1822	September 22, 2014
[PCI DSS 3.0] 3.6.8 Requirement for cryptographic key custodians to formally acknowledge that they understand and Protect Cardholder Data (Requirements 3-4) requirement-3:-prote	1782	September 22, 2014
[PCI DSS 3.0] 3.6.7 Prevention of unauthorized substitution of cryptographic keys. Protect Cardholder Data (Requirements 3-4) requirement-3:-prote	1956	September 22, 2014
[PCI DSS 3.0] 3.6.6 If manual clear-text cryptographic key-management operations are used, these operations must b Protect Cardholder Data (Requirements 3-4) requirement-3:-prote	3228	September 22, 2014
[PCI DSS 3.0] 3.6.5 Retirement or replacement (for example, archiving, destruction, and/or revocation) of keys as Protect Cardholder Data (Requirements 3-4) requirement-3:-prote	1506	September 22, 2014
[PCI DSS 3.0] 3.6.4 Cryptographic key changes for keys that have reached the end of their cryptoperiod Protect Cardholder Data (Requirements 3-4) requirement-3:-prote	2264	September 22, 2014
[PCI DSS 3.0] 3.6.3 Secure cryptographic key storage Protect Cardholder Data (Requirements 3-4) requirement-3:-prote	1414	September 22, 2014
[PCI DSS 3.0] 3.6.2 Secure cryptographic key distribution Protect Cardholder Data (Requirements 3-4) requirement-3:-prote	1584	September 22, 2014
[PCI DSS 3.0] 3.6.1 Generation of strong cryptographic keys Protect Cardholder Data (Requirements 3-4) requirement-3:-prote	1709	September 22, 2014
[PCI DSS 3.0] 3.6 Fully document and implement all key-management processes and procedures for cryptographic keys Protect Cardholder Data (Requirements 3-4) requirement-3:-prote	1799	September 22, 2014
[PCI DSS 3.0] 3.5.3 Store cryptographic keys in the fewest possible locations. Protect Cardholder Data (Requirements 3-4) requirement-3:-prote	1498	September 22, 2014
[PCI DSS 3.0] 3.5.2 Store secret and private keys used to encrypt/decrypt cardholder data in one (or more) of the Protect Cardholder Data (Requirements 3-4) requirement-3:-prote	3667	September 22, 2014
[PCI DSS 3.0] 3.5.1 Restrict access to cryptographic keys to the fewest number of custodians necessary. Protect Cardholder Data (Requirements 3-4) requirement-3:-prote	1349	September 22, 2014
[PCI DSS 3.0] 3.5 Document and implement procedures to protect keys used to secure stored cardholder data against Protect Cardholder Data (Requirements 3-4) requirement-3:-prote	1374	September 22, 2014
[PCI DSS 3.0] 3.4 Render PAN unreadable anywhere it is stored Protect Cardholder Data (Requirements 3-4) requirement-3:-prote	2737	September 22, 2014
[PCI DSS 3.0] 3.3 Mask PAN when displayed (the first six and last four digits are the maximum number of digits to Protect Cardholder Data (Requirements 3-4) requirement-3:-prote	3032	September 22, 2014
[PCI DSS 3.0] 3.2.3 Do not store the personal identification number (PIN) or the encrypted PIN block. Protect Cardholder Data (Requirements 3-4) requirement-3:-prote	1339	September 22, 2014
[PCI DSS 3.0] 3.2.2 Do not store the card verification code or value Protect Cardholder Data (Requirements 3-4) requirement-3:-prote	1238	September 22, 2014
[PCI DSS 3.0] 3.2.1 Do not store the full contents of any track Protect Cardholder Data (Requirements 3-4) requirement-3:-prote	1367	September 22, 2014