Platform Access Controls Sample Clauses

Platform Access Controls. Pantheon will encrypt Data Controller Personal Data not intended for public or unauthenticated viewing when transferring Data Controller Personal Data over public networks. Pantheon will make available to Data Controller such tools as may be necessary and available to Pantheon to support further application of cryptographic protocol, such as TLS or SSH, for the secure transfer of Data Controller Personal Data to and from the Services over public networks. Pantheon applies standard encryption technologies to protect Data Controller data both at rest and in transit where appropriate. Pantheon establishes sessions to the Pantheon web servers utilizing Hypertext Transfer Protocol Secure (HTTPS) and automates adding and renewing Transport Layer Security (TLS) certificates for custom domains added to customer websites. Pantheon users authenticate to production servers over secure shell (SSH) encryption protocol using a uniquely assigned SSH key-pair in which the private key is enabled only with the internal user’s unique username and SSH key stored in a hardware token. Pantheon will monitor use of privileged access and maintain security information an event management measures designed to i) identify unauthorized access and activity, ii) facilitate an appropriate response, and iii) to enable internal and independent third- party audits of compliance with documented Pantheon Risk Management and Information Security policy. Logs, in which privileged access and activity are recorded, will be retained in compliance with Pantheon’s records retention standards. Pantheon will maintain measures designed to protect against unauthorized access, modification and accidental or deliberate destruction of such logs.
Sample 1
AutoNDA by SimpleDocs

Related to Platform Access Controls

  • Access Controls a. Authorized Access - DST shall have controls that are designed to maintain the logical separation such that access to systems hosting Fund Data and/or being used to provide services to Fund will uniquely identify each individual requiring access, grant access only to authorized personnel based on the principle of least privileges, and prevent unauthorized access to Fund Data.

  • System Access Control Data processing systems used to provide the Cloud Service must be prevented from being used without authorization. Measures: • Multiple authorization levels are used when granting access to sensitive systems, including those storing and processing Personal Data. Authorizations are managed via defined processes according to the SAP Security Policy • All personnel access SAP’s systems with a unique identifier (user ID). • SAP has procedures in place so that requested authorization changes are implemented only in accordance with the SAP Security Policy (for example, no rights are granted without authorization). In case personnel leaves the company, their access rights are revoked. • SAP has established a password policy that prohibits the sharing of passwords, governs responses to password disclosure, and requires passwords to be changed on a regular basis and default passwords to be altered. Personalized user IDs are assigned for authentication. All passwords must fulfill defined minimum requirements and are stored in encrypted form. In the case of domain passwords, the system forces a password change every six months in compliance with the requirements for complex passwords. Each computer has a password-protected screensaver. • The company network is protected from the public network by firewalls. • SAP uses up–to-date antivirus software at access points to the company network (for e-mail accounts), as well as on all file servers and all workstations. • Security patch management is implemented to provide regular and periodic deployment of relevant security updates. Full remote access to SAP’s corporate network and critical infrastructure is protected by strong authentication.

  • Data Access Control Persons entitled to use data processing systems gain access only to the Personal Data that they have a right to access, and Personal Data must not be read, copied, modified or removed without authorization in the course of processing, use and storage. Measures: • As part of the SAP Security Policy, Personal Data requires at least the same protection level as “confidential” information according to the SAP Information Classification standard. • Access to Personal Data is granted on a need-to-know basis. Personnel have access to the information that they require in order to fulfill their duty. SAP uses authorization concepts that document grant processes and assigned roles per account (user ID). All Customer Data is protected in accordance with the SAP Security Policy. • All production servers are operated in the Data Centers or in secure server rooms. Security measures that protect applications processing Personal Data are regularly checked. To this end, SAP conducts internal and external security checks and penetration tests on its IT systems. • SAP does not allow the installation of software that has not been approved by SAP. • An SAP security standard governs how data and data carriers are deleted or destroyed once they are no longer required.

  • System Access CUSTOMER agrees to provide to PROVIDER, at CUSTOMER’S expense, necessary access to the mainframe computer and related information technology systems (the “System”) on which CUSTOMER data is processed during the times (the “Service Hours”) specified in the PSAs, subject to reasonable downtime for utility outages, maintenance, performance difficulties and the like. In the event of a change in the Service Hours, CUSTOMER will provide PROVIDER with at least fifteen (15) calendar days written notice of such change.

  • Access Control Supplier will maintain an appropriate access control policy that is designed to restrict access to Accenture Data and Supplier assets to authorized Personnel. Supplier will require that all accounts have complex passwords that contain letters, numbers, and special characters, be changed at least every 90 days, and have a minimum length of 8 characters.

  • User IDs and Password Controls All users must be issued a unique user name for accessing DHCS PHI or PI. Username must be promptly disabled, deleted, or the password changed upon the transfer or termination of an employee with knowledge of the password, at maximum within 24 hours. Passwords are not to be shared. Passwords must be at least eight characters and must be a non-dictionary word. Passwords must not be stored in readable format on the computer. Passwords must be changed every 90 days, preferably every 60 days. Passwords must be changed if revealed or compromised. Passwords must be composed of characters from at least three of the following four groups from the standard keyboard: • Upper case letters (A-Z) • Lower case letters (a-z) • Arabic numerals (0-9) • Non-alphanumeric characters (punctuation symbols)

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Information regarding Interconnection Facilities 4.2.1 The SPD shall be required to obtain all information from the STU/CTU/concerned authority with regard to the Interconnection Facilities as is reasonably necessary to enable it to design, install and operate all interconnection plant and apparatus on the SPD’s side of the Delivery Point to enable delivery of electricity at the Delivery Point. The transmission of power up to the point of interconnection where the metering is done for energy accounting shall be the responsibility of the SPD at his own cost.

  • Access to Network Interface Device (NID 2.4.3.1. Due to the wide variety of NIDs utilized by BellSouth (based on subscriber size and environmental considerations), Mpower may access the on-premises wiring by any of the following means: BellSouth shall allow Mpower to connect its loops directly to BellSouth’s multi-line residential NID enclosures that have additional space and are not used by BellSouth or any other telecommunications carriers to provide service to the premise. Mpower agrees to install compatible protectors and test jacks and to maintain the protection system and equipment and to indemnify BellSouth pursuant to Section 8 of the General Terms and Conditions of this Agreement.

  • Network Access TENANT may find it necessary to purchase a network interface card, wireless PC card or other hardware in order to connect to the internet service. LANDLORD is not responsible for the purchase of these items and LANDLORD cannot guarantee compatibility with any device TENANT may have. The computer and network card must have software installed that supports the Internet Protocol commonly referred to as TCP/IP. Any conflicts between the software compatibility of the network and the TENANT’S computer operating system or any other feature will be the responsibility of the TENANT to resolve. LANDLORD will not be responsible for software issues related to the user’s personal computer.

Time is Money Join Law Insider Premium to draft better contracts faster.