Policies and Logging Sample Clauses

Policies and Logging. The Braze Services are operated in accordance with the following procedures to enhance security: ● Dashboard User passwords are never transmitted or stored in clear text ● Braze uses industry-standard methods to determine password validity ● API key information for third-party services provided by the customer are encrypted for storage ● Braze keeps audit logs for all access to production servers ● Server access is controlled via public key access, instead of passwords, and only permitted while on VPN that requires multi-factor authentication ● Logs are stored in a secure centralized host to prevent tampering ● Braze application and ssh audit logs are stored for one year ● Passwords are not logged under any circumstances ● Access to Braze mail and document services is only allowed on approved mobile devices that have automated security policies enforced, such as encryption, autolock and passwords ● All access to customer dashboard accounts by Braze Employees must be done through an internal service that is accessible via a 3-factor VPN only ● As part of Braze’s Employee Information Security Policy, employees may not store any Customer Data on removable media
AutoNDA by SimpleDocs
Policies and Logging. The Braze Services are operated in accordance with the following procedures to enhance security: • User passwords are never transmitted in clear text and use industry-standard hashing functions to determine password validity • API key information for third-party services provided by the customer are encrypted for storage • Braze keeps audit logs for all access to production servers • Server access is controlled via public key access instead of using passwords. Server access is only permitted while on VPN that requires multi-factor authentication. • Logs are stored in a secure centralized host to prevent tampering • Braze application and ssh audit logs are stored for one year • Passwords are not logged under any circumstances • Access to Braze mail and document services is only allowed on approved mobile devices that have automated security policies enforced, such as encryption, autolock and passwords • All access to customer dashboard accounts by Braze Employees must be done via an internal service that is accessible via a three factor VPN only. As part of Braze’s Employee Information Security Policy, employees may not store any Customer Data on removable media.
Policies and Logging. The ET Services are operated in accordance with the following procedures to enhance security: • User passwords are never transmitted unencrypted. • User access log entries will be maintained, containing date, time, URL executed or identity ID operated on, operation performed (viewed, edited, etc.) and source IP address. • Logs will be stored in a secure centralized host to prevent tampering. • Passwords are not logged under any circumstances. • Watchdog Behavioral Monitoring Program alerts ET Security to anomalous behavior within the ET Services.
Policies and Logging. The Service is operated in accordance with the following procedures to enhance security: User passwords are stored using a one-way hashing algorithm (SHA-256) and are never transmitted unencrypted. User access log entries will be maintained, containing date, time, User ID, URL executed or entity ID operated on, operation performed (viewed, edited, etc.) and source IP address. Note that source IP address might not be available if NAT (Network Address Translation) or XXX (Port Address Translation ) is used by Customer or its ISP. If there is suspicion of inappropriate access, SFDC can provide Customer log entry records to assist in forensic analysis. This service will be provided to Customer on a time and materials basis. Logging will be kept for a minimum of 90 days. Logging will be kept in a secure area to prevent tampering. Passwords are not logged under any circumstances. Certain administrative changes to the Service (such as password changes and adding custom fields) are tracked in an area known as the “Setup Audit Log” and are available for viewing by Customer’s system administrator. Customer may download and store this data locally. SFDC personnel will not set a defined password for a User. Passwords are reset to a random value (which must be changed on first use) and delivered automatically via email to the requesting User. Intrusion Detection. SFDC, or an authorized third party, will monitor the Service for unauthorized intrusions using network-based intrusion detection mechanisms. User Authentication. Access to the Service requires a valid User ID and password combination, which are encrypted via SSL while in transmission. Following a successful authentication, a random session ID is generated and stored in the user’s browser to preserve and track session state. Security Logs. SFDC shall ensure that all SFDC systems, including firewalls, routers, network switches and operating systems, log information to their respective system log facility or a centralized syslog server (for network systems) in order to enable the security audits referred to herein.
Policies and Logging. The Services are operated pursuant to the following procedures to enhance security: • User passwords are never transmitted in clear text and use industry-standard hashing functions to determine password validity; • API key information for third-party services provided by the customer are encrypted for storage; • Inkit keeps audit logs for all access to production servers; • Server access is controlled via public key access instead of using passwords. Server access is only permitted while on VPN that requires multi-factor authentication; • Logs are stored in a secure centralized host to prevent tampering; • Inkit application and ssh audit logs are stored for one year; • Passwords are not logged under any circumstances; • Access to Inkit mail and document services is only allowed on approved mobile devices that have automated security policies enforced, such as encryption, autolock, and password; • All access to customer dashboard accounts by Inkit employees must be done via an internal service that is accessible only via a three factor VPN. As part of Inkit’s information security policy, employees may not store any Customer Data on removable media.

Related to Policies and Logging

  • 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.

  • Policies and Procedures i) The policies and procedures of the designated employer apply to the employee while working at both sites.

  • Meals and Lodging (a) Meal and lodging expenses shall not be allowed without prior approval of the appointing authority or designee as necessary for the purpose of conducting County business. Excess charges greater than the amounts listed below in paragraphs (b) and (c) may be authorized under special conditions, such as a convention requirement or in an area of unusually high cost (such as San Francisco Bay area, Sacramento, Los Angeles and San Diego). Original receipts are mandatory to obtain reimbursement for all lodging expenses, and except as provided below for all meal expenses claimed.

  • Responsibilities of Business Associate Business Associate agrees:

  • KEYS AND LOCKS The Tenant agrees not to install additional or different locks or gates on any doors or windows of the unit without the written permission of the Landlord. If the Landlord approves the Tenant's request to install such locks, the Tenant agrees to provide the Landlord with a key for each lock. When this Agreement ends, the Tenant agrees to return all keys to the dwelling unit to the Landlord. The Landlord may charge the Tenant $ for each key not returned.

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!