System Logging. The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.
System Logging. The system must maintain an automated audit trail which can identify the user or system process which initiates a request for County PHI or PI, or which alters County PHI or PI. The audit trail must be date and time stamped, must log both successful and failed accesses, must be read only, and must be restricted to authorized users. If County PHI or PI is stored in a database, database logging functionality must be enabled. Audit trail data must be archived for at least three (3) years after occurrence.
System Logging. The system must maintain an automated audit trail which can identify the user or system process which initiates a request for DHCS PHI or PI, or which alters DHCS PHI or PI. The audit trail must be date and time stamped, must log both successful and failed accesses, must be read only, and must be restricted to authorized users. If DHCS PHI or PI is stored in a database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 years after occurrence.
System Logging. The system must maintain an automated audit trail which can identify
System Logging i. The systems which provide access to PII must maintain an automated audit trail that can identify the user or system process which initiates a request for PII or alters PII.
ii. The audit trail shall:
A. Be date and time stamped;
B. Log both successful and failed accesses;
C. Be read-access only; and
D. Be restricted to authorized users.
iii. If PII is stored in a database, database logging functionality shall be enabled.
iv. Audit trail data shall be archived for at least three (3) years from the occurrence.
System Logging. The system must maintain an automated audit trail which can identify the user or system process which initiates a request for CDPH PCI, or which alters CDPH PCI. The audit trail must be date and time stamped, must log both successful and failed accesses, must be read only, and must be restricted to authorized users This logging must be included for all user privilege levels including, but not limited to, systems administrators. If CDPH PCI is stored in a database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 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 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 user or system process which initiates a request for CDPH PHI or PI, or which alters CDPH PHI or PI. The audit trail must be date and time stamped, must log both successful and failed accesses, must be read only, and must be restricted to authorized users. If CDPH PHI or PI is stored in a database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 years after occurrence.
System Logging. The system must maintain an automated audit trail which can identify the user or system process which initiates a request for DBH PHI or PI, or which alters DBH PHI or PI. The audit trail must be date and time stamped, must log both successful and failed accesses, must be read only, and must be restricted to authorized users. If DBH PHI or PI is stored in a database, database logging functionality must be enabled. Audit trail data must be archived for at least ten (10) years from the final date of the contract period or from the date of completion of any audit, whichever is later.
System Logging. Any and all systems providing access to PSEI or PHI must maintain an automated audit trail that can be used to identify any user or process which alters PSEI or PHI. The audit trail must be date and time stamped, log both successful and failed accesses, be read only and restricted to authorized users. If PSEI or PHI is stored in a database, logging functionality must be enabled. Audit trail data must be archived for at least ten (10) years after occurrence.
