Common use of System Logging Clause in Contracts

System Logging. The system must maintain an automated audit trail which can identify the 30 user or system process which initiates a request for COUNTY PCI, or which alters COUNTY PCI. The 31 audit trail must be date and time stamped, must log both successful and failed accesses, must be read 33 levels including, but not limited to, systems administrators. If COUNTY PCI is stored in a database, 34 database logging functionality must be enabled. Audit trail data must be archived for at least three (3) 35 years after occurrence.

System Logging. The system must maintain an automated audit trail which can identify the 30 27 user or system process which initiates a request for COUNTY PCI, or which alters COUNTY PCI. The 31 28 audit trail must be date and time stamped, must log both successful and failed accesses, must be read 33 30 levels including, but not limited to, systems administrators. If COUNTY PCI is stored in a database, 34 31 database logging functionality must be enabled. Audit trail data must be archived for at least three (3) 35 32 years after occurrence.

System Logging. The system must maintain an automated audit trail which can identify the 30 user or system process which initiates a request for COUNTY PCI, or which alters COUNTY PCI. The 31 audit trail must be date and time stamped, must log both successful and failed accesses, must be read only, 32 and must be restricted to authorized users. This logging must be included for all user privilege levels 33 levels including, but not limited to, systems administrators. If COUNTY PCI is stored in a database, database 34 database logging functionality must be enabled. Audit trail data must be archived for at least three (3) 35 years after 35 occurrence.

System Logging. The system must maintain an automated audit trail which can identify the 30 32 user or system process which initiates a request for COUNTY PCI, or which alters COUNTY PCI. The 31 33 audit trail must be date and time stamped, must log both successful and failed accesses, must be read 33 35 levels including, but not limited to, systems administrators. If COUNTY PCI is stored in a database, 34 36 database logging functionality must be enabled. Audit trail data must be archived for at least three (3) 35 37 years after occurrence.

System Logging. The system must maintain an automated audit trail which can identify the 30 32 user or system process which initiates a request for COUNTY PCI, or which alters COUNTY PCI. The 31 33 audit trail must be date and time stamped, must log both successful and failed accesses, must be read 33 only, 34 and must be restricted to authorized users. This logging must be included for all user privilege levels 35 including, but not limited to, systems administrators. If COUNTY PCI is stored in a database, 34 database 36 logging functionality must be enabled. Audit trail data must be archived for at least three (3) 35 years after 37 occurrence.