Data Loss Prevention Capability Sample Clauses

Data Loss Prevention Capability. The Supplier must have in place appropriate software, systems and processes that are designed to detect and prevent loss of Amplitel Data.
AutoNDA by SimpleDocs
Data Loss Prevention Capability. The Supplier must have in place appropriate software, systems and processes that are designed to detect and prevent loss of Telstra Data.

Related to Data Loss Prevention Capability

  • Packet Switching Capability 4.5.1 The packet switching capability network element is defined as the function of routing or forwarding packets, frames, cells or other data units based on address or other routing information contained in the packets, frames, cells or other data units.

  • Local Circuit Switching Capability, including Tandem Switching Capability 4.2.1 Local circuit switching capability is defined as: (A) line-side facilities, which include, but are not limited to, the connection between a loop termination at a main distribution frame and a switch line card; (B) trunk-side facilities, which include, but are not limited to, the connection between trunk termination at a trunk-side cross-connect panel and a switch trunk card; (C) switching provided by remote switching modules; and (D) all features, functions, and capabilities of the switch, which include, but are not limited to: (1) the basic switching function of connecting lines to lines, line to trunks, trunks to lines, and trunks to trunks, as well as the same basic capabilities made available to BellSouth’s customers, such as a telephone number, white page listings, and dial tone; and (2) all other features that the switch is capable of providing, including but not limited to customer calling, customer local area signaling service features, and Centrex, as well as any technically feasible customized routing functions provided by the switch. Any features that are not currently available but are technically feasible through the switch can be requested through the BFR/NBR process.

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

  • DISASTER RECOVERY AND BUSINESS CONTINUITY The Parties shall comply with the provisions of Schedule 5 (Disaster Recovery and Business Continuity).

  • System Upgrade Facilities and System Deliverability Upgrades Connecting Transmission Owner shall design, procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Appendix A hereto. The responsibility of the Developer for costs related to System Upgrade Facilities and System Deliverability Upgrades shall be determined in accordance with the provisions of Attachment S to the NYISO OATT.

  • Loop Testing/Trouble Reporting 2.1.6.1 NOW will be responsible for testing and isolating troubles on the Loops. NOW must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, NOW will be required to provide the results of the NOW tests which indicate a problem on the BellSouth provided Loop.

  • Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

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