Logging. The ISP will require the maintenance of network and application logs as part of BNY Mellon’s security information and event management processes. Logs are retained in accordance with law applicable to BNY Mellon’s provision of the services under the Agreement as well as BNY Mellon’s applicable policies. BNY Mellon uses various tools in conjunction with such logs, which may include behavioral analytics, security monitoring case management, network traffic monitoring and analysis, IP address management and full packet capture.
Logging. Partner will log, including time and date, all attempted accesses to its servers involved in performing obligations to or for Yahoo or otherwise conducted pursuant to this Security Agreement and the Business Agreement, and the result of such attempts, successful or unsuccessful. In order to enable a complete audit trail of activities, Partner must log, including time and date, all commands that require additional privileges, including all failed attempts to execute privileged commands. Partner must protect the logs from tampering. Partner will retain all such log entries for at least six months.
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 3 years after occurrence.
Logging. Data center staff log all scheduled and unscheduled downtime, system alarms, and steps taken to recover. This log is used to determine overall system uptime and steps required improving uptime performance. • Remote monitoring TRX is in the process of creating a web based monitoring application that will allow our customers to view a “dashboard” of all system processes and status. PNR’s on queue, workstations running, database capacity, PNRs processed by hour, etc. will be displayed.
Logging. The date, reason and identity of the Data Processor’s representative are logged when Personal Data are accessed in the course of performing the Data Processor’s obligations under the Agreement and the Contract. The above log records are routinely spot checked to ensure that Personal Data are accessed solely in accordance with the instructions under which the employee works. Routine spot checks are made to ensure that Sub-Processors and their representatives access Personal Data only where relevant to the service provided by them or under direct instruction from the Data Processor. The Data Processor’s processing of Personal Data is performed, in whole or in part, from home and/or remote workplaces. Personal Data are accessed using a personal VPN connection to the Data Processor’s network or using a SSL connection and personal login to Helpdesk Software.
Logging. Al network traffic and all server logs are monitored and logged. The following activities are logged in systems, databases and networks: • All access attempts • All searches and • Activities carried out by system administrators and others with special rights • Security incidents including (i) deactivation of logging, (ii) changes to system rights and (iii) failed log-on attempts The Supplier does not work with shared log-ins. Therefore, it will always be possible to identify which employee performed a specific activity. The relevant log files are stored and protected against manipulation and technical errors. The log files are continuously reviewed to ensure normal operation and to examine unintended incidents. All external access to systems and databases where processing of personal data takes places, is filtered through a secure firewall with a restrictive protocol. A port and IP address filtration has been implemented to ensure limited access to ports and specific IP addresses.