Access, Intervention, Transfer and Separation Control. (a) U-Visit will maintain documented security architecture of networks managed by U-Visit in its operation of the Service. U-Visit will separately review such network architecture, including measures designed to prevent unauthorized network connections to systems, applications and network devices, for compliance with its secure segmentation, isolation, and defense in depth standards prior to implementation. U-Visit may use wireless networking technology in its maintenance and support of the Service and associated components. Such wireless networks, if any, will be encrypted and require secure authentication and will not provide direct access to Service networks. Service networks do not use wireless networking technology.
(b) U-Visit will maintain measures for a Service that are designed to logically separate and prevent Customer Personal Data from being exposed to or accessed by unauthorized persons.
(c) To the extend described in the relevant Agreement Documents, U-Visit will encrypt Customer Personal Data not intended for public or unauthenticated viewing when transferring Customer Personal Data over public networks and enable use of a cryptographic protocol, such as HTTPS, SFTP, and FTPS, for secure transfer of Customer Personal Data to and from the Service over public networks.
(d) U-Visit will encrypt Customer Personal Data at rest when specified in Agreement Documents. If the Service includes management of cryptographic keys, U-Visit will maintain documented procedures for secure key generation, issuance, distribution, storage, rotation, revocation, recovery, backup, destruction, access, and use.
(e) If U-Visit requires access to Customer Personal Data, U-Visit will restrict and limit such access to least level required to provide and support the Service. Such access, including administrative access to any underlying components (privileged access), will be individual, role based, and subject to approval and regular validation by authorized U-Visit personnel following the principles of segregation of duties. U-Visit will maintain measures to identify and remove redundant and dormant accounts with privileged access and will promptly revoke such access upon the account owner’s separation or request of authorized U-Visit personnel, such as the account owner’s manager.
(f) Consistent with industry standard practices, and to the extent natively supported by each component managed by U-Visit within the Service, U-Visit will maintain technical measures enfor...
Access, Intervention, Transfer and Separation Control a. The Supplier will maintain a documented security architecture for Components. The Supplier will separately review such security architecture, including measures designed to prevent unauthorized network connections to systems, applications and network devices, for compliance with its secure segmentation, isolation, and defense-in-depth standards prior to implementation.
b. The Supplier may use wireless networking technology in its maintenance and support of the Supplier Services and associated Components. Such wireless networks, if any, will be encrypted and require secure authentication and will not provide direct access to the Supplier Cloud Services networks. The Supplier Cloud Services networks do not use wireless networking technology.
c. The Supplier will maintain measures for the Supplier Service that are designed to logically separate and prevent Content from being exposed to or accessed by unauthorized persons. The Supplier will maintain appropriate isolation of its production and non-production environments, and, if Content is transferred to a non -production environment, for example to reproduce an error at the Buyer's request, security and privacy protections in the non -production environment will be equivalent to those in production.
d. The Supplier will encrypt Content not intended for public or unauthenticated viewing when transferring Content over public networks and enable use of a cryptographic protocol, such as HTTPS, SFTP, or FTPS, for the Buyer’s secure transfer of Content to and from the Supplier Services over public networks.
e. The Supplier will encrypt Content at rest if and as specified in the Supplier Services Document. If the Supplier Service includes management of cryptographic keys, the Supplier will maintain documented procedures for secure key generation, issuance, distribution, storage, rotation, revocation, recovery, backup, destruction, access, and use.
f. If the Supplier requires access to Content to provide the Supplier Services, and if such access is managed by the Supplier, the Supplier will restrict access to the minimum level required. Such access, including administrative access to any underlying Components (privileged access), will be individual, role-based, and subject to approval and regular validation by authorized the Supplier personnel following the principles of segregation of duties. The Supplier will maintain measures to identify and remove redundant and dormant accounts with privileged access and will ...
Access, Intervention, Transfer and Separation Control a. IBM will maintain a documented security architecture for Components. IBM will separately review such security architecture, including measures designed to prevent unauthorized network connections to systems, applications and network devices, for compliance with its secure segmentation, isolation, and defense-in-depth standards prior to implementation.
b. IBM may use wireless networking technology in its maintenance and support of the IBM Services and associated Components. Such wireless networks, if any, will be encrypted and require secure authentication and will not provide direct access to IBM Cloud Services networks. IBM Cloud Services networks do not use wireless networking technology.
c. IBM will maintain measures for an IBM Service that are designed to logically separate and prevent Content from being exposed to or accessed by unauthorized persons. IBM will maintain appropriate isolation of its production and non - production environments, and, if Content is transferred to a non -production environment, for example to reproduce an error at Client's request, security and privacy protections in the non -production environment will be equivalent to those in production.
d. IBM will encrypt Content not intended for public or unauthenticated viewing when transferring Con tent over public networks and enable use of a cryptographic protocol, such as HTTPS, SFTP, or FTPS, for Client's secure transfer of Content to and from the IBM Services over public networks.
e. IBM will encrypt Content at rest if and as specified in an IBM Services Document. If an IBM Service includes management of cryptographic keys, IBM will maintain documented procedures for secure key generation, issuance, distribution, storage, rotation, revocation, recovery, backup, destruction, access, and use.
f. If IBM requires access to Content to provide the IBM Services, and if such access is managed by IBM, IBM will restrict access to the minimum level required. Such access, including administrative access to any underlying Components (privileged access), will be individual, role-based, and subject to approval and regular validation by authorized IBM personnel following the principles of segregation of duties. IBM will maintain measures to identify and remove redundant and dormant accounts with privileged access and will promptly revoke such access upon the account owner's separation or upon the request of authorized IBM personnel, such as the account owner's manager.
g. Consistent with in...
Access, Intervention, Transfer and Separation Control. 5.1 Documented security architecture of networks managed by or on behalf of Acoustic in its operation of the SaaS Product will be maintained. Such network architecture, including measures designed to prevent unauthorized network connections to systems, applications and network devices, will be reviewed for compliance with secure segmentation, isolation, and defense-in-depth standards prior to implementation. SaaS Product networks do not use wireless-networking technology. Wireless-networking technology may be used in the maintenance and support of the SaaS Product and associated Components. Such wireless networks, if any, will be encrypted, will require secure authentication, and will not provide direct access to SaaS Product networks.
5.2 Measures that are designed to logically separate and prevent Content from being exposed to or accessed by unauthorized persons will be maintained for each SaaS Product. Appropriate isolation of its production and non-production environments will be maintained, and, if Content is transferred to a non-production environment, for example in order to reproduce an error at Partner's request, security and privacy measures designed to provide the same level of protection as in the production environment will be maintained in the non-production environment.
5.3 To the extent described in the relevant Acoustic Documentation, Content not intended for public or unauthenticated viewing will be encrypted when transferred over public networks, and the SaaS Product shall enable use of a cryptographic protocol, such as HTTPS or SFTP, for Partner's secure transfer of Content to and from the SaaS Product over public networks.
5.4 Content will be encrypted at rest when and as specified in the relevant Acoustic Documentation. If the SaaS Product includes management of cryptographic keys, documented procedures will be maintained for secure key generation, issuance, distribution, storage, rotation, revocation, recovery, backup, destruction, access, and use.
5.5 If access to Content is required, it will be restricted to the minimum level required. Such access, including administrative access to any underlying Components (“Privileged Access”), will be individual, role- based, and subject to approval and regular validation by authorized personnel following the principles of segregation of duties. Adequate measures will be maintained to identify and remove redundant and dormant accounts with Privileged Access and such Privileged Access will promp...
Access, Intervention, Transfer and Separation Control. (a) Pindrop will maintain measures for Pindrop-Controlled Systems that are designed to logically separate and prevent Company’s Confidential Information stored within Pindrop-Controlled Systems from being exposed to or accessed by unauthorized persons. Pindrop will maintain isolation of its production and non-production environments, and, if Company’s Confidential Information is transferred to a non- production environment, for example to reproduce an error at Company’s request, security and privacy protections in the non-production environment will be equivalent to those in production.
(b) Pindrop will encrypt Company’s Confidential Information that is subject to long-term storage within Pindrop-Controlled Systems and when Company’s Confidential Information is transmitted by Pindrop over public networks. Pindrop will maintain documented procedures for encryption key generation, issuance, distribution, storage, rotation, revocation, recovery, backup, destruction, access, and use. To the extent that encryption is impractical, Pindrop will use compensating controls designed to protect Company’s Confidential Information.
(c) If Pindrop requires access to Company’s Confidential Information that is stored within Pindrop-Controlled Systems, and if such access is managed by Pindrop, Pindrop will deploy measures designed to restrict access to the minimum level required. Such access, including, without limitation, administrative access, will be individual, role- based, and subject to approval and regular validation by authorized Pindrop personnel following the principles of segregation of duties. Pindrop will maintain measures to identify and remove redundant and dormant accounts with privileged access and will promptly revoke such access upon the account owner’s separation or upon the request of authorized Pindrop personnel, such as the account owner’s manager.
(d) For Pindrop-Controlled Systems, Pindrop will:
(i) monitor and periodically test the Pindrop-Controlled Systems to assess the effectiveness of the Security Policy;
(ii) maintain technical measures enforcing timeout of inactive sessions, lockout of accounts after multiple sequential failed login attempts, strong password or passphrase authentication, and password change frequency;
(iii) monitor use of privileged access and maintain security information and event management measures designed to: (1) identify unauthorized access, use or tampering; (2) facilitate a timely and appropriate response, and (3) en...
