|
About the Regularly Monitor and Test Networks category
|
|
0
|
64
|
January 23, 2023
|
|
[PCI DSS 1.x] 10.2.2 All actions taken by any individual with root or administrative privileges
|
|
6
|
12666
|
March 15, 2012
|
|
[PCI DSS 1.x] 11.5 Deploy file integrity monitoring software to alert personnel to unauthorized modification of cr
|
|
8
|
22885
|
March 8, 2012
|
|
[PCI DSS 1.x] 11.3 Perform penetration testing at least once a year and after any significant infrastructure or ap
|
|
1
|
4955
|
January 25, 2012
|
|
[PCI DSS 1.x] 10.2 5 Use of identification and authentication mechanisms
|
|
8
|
14801
|
May 25, 2011
|
|
[PCI DSS 1.x] 10.3.1 User identification
|
|
1
|
4669
|
April 9, 2011
|
|
[PCI DSS 1.x] 11.2 Run internal and external network vulnerability scans at least quarterly and after any signific
|
|
1
|
8244
|
February 21, 2011
|
|
[PCI DSS 1.x] 10.2.7 Creation and deletion of system-level objects
|
|
1
|
6110
|
October 14, 2010
|
|
[PCI DSS 1.x] 10.5.5 Use file integrity monitoring and change detection software on logs to ensure that existing l
|
|
1
|
5100
|
September 29, 2010
|
|
[PCI DSS 1.x] 10.2.6 Initialization of the audit logs
|
|
2
|
6803
|
June 14, 2010
|
|
[PCI DSS 1.x] 11.1 Test security controls, limitations, network connections, and restrictions annually to assure t
|
|
2
|
5007
|
March 16, 2009
|
|
[PCI DSS 1.x] 10.2.1 All individual accesses to cardholder data
|
|
2
|
5322
|
August 8, 2008
|
|
[PCI DSS 1.x] 11.4 Use network intrusion detection systems, host-based intrusion detection systems, and intrusion
|
|
0
|
6591
|
March 18, 2007
|
|
[PCI DSS 1.x] 11.3.2 Application-layer penetration tests
|
|
0
|
4834
|
March 18, 2007
|
|
[PCI DSS 1.x] 11.3.1 Network-layer penetration tests
|
|
0
|
4460
|
March 18, 2007
|
|
[PCI DSS 1.x] 10.7 Retain audit trail history for at least one year, with a minimum of three months available onli
|
|
0
|
14525
|
March 18, 2007
|
|
[PCI DSS 1.x] 10.6 Review logs for all system components at least daily. Log reviews must include those servers th
|
|
0
|
5576
|
March 18, 2007
|
|
[PCI DSS 1.x] 10.5.4 Copy logs for wireless networks onto a log server on the internal LAN
|
|
0
|
2222
|
March 18, 2007
|
|
[PCI DSS 1.x] 10.5.3 Promptly back up audit trail files to a centralized log server or media that is difficult to
|
|
0
|
3726
|
March 18, 2007
|
|
[PCI DSS 1.x] 10.5.2 Protect audit trail files from unauthorized modifications
|
|
0
|
3933
|
March 18, 2007
|
|
[PCI DSS 1.x] 10.5.1 Limit viewing of audit trails to those with a job-related need
|
|
0
|
3177
|
March 18, 2007
|
|
[PCI DSS 1.x] 10.5 Secure audit trails so they cannot be altered
|
|
0
|
3152
|
March 18, 2007
|
|
[PCI DSS 1.x] 10.4 Synchronize all critical system clocks and times
|
|
0
|
5823
|
March 18, 2007
|
|
[PCI DSS 1.x] 10.3.6 Identity or name of affected data, system component, or resource
|
|
0
|
3171
|
March 18, 2007
|
|
[PCI DSS 1.x] 10.3.5 Origination of event
|
|
0
|
3784
|
March 18, 2007
|
|
[PCI DSS 1.x] 10.3.4 Success or failure indication
|
|
0
|
2890
|
March 18, 2007
|
|
[PCI DSS 1.x] 10.3.3 Date and time
|
|
0
|
2585
|
March 18, 2007
|
|
[PCI DSS 1.x] 10.3.2 Type of event
|
|
0
|
2962
|
March 18, 2007
|
|
[PCI DSS 1.x] 10.3 Record at least the following audit trail entries for all system components for each event: 10.
|
|
0
|
3347
|
March 18, 2007
|
|
[PCI DSS 1.x] 10.2.4 Invalid logical access attempts
|
|
0
|
4520
|
March 18, 2007
|