ENDPOINT PROTECTION Sample Clauses
The ENDPOINT PROTECTION clause establishes requirements for securing devices such as computers, smartphones, and tablets that connect to a network or handle sensitive data. It typically mandates the use of security software, regular updates, and monitoring to prevent unauthorized access or malware infections on these endpoints. By setting these standards, the clause helps protect organizational data from breaches and ensures that all connected devices adhere to a consistent security baseline.
ENDPOINT PROTECTION. 2.1 During the Subscription Term, the Supplier shall provide the Customer and its End Users with the following;
2.1.1 access to required Products and licenses on a monthly per user (or per server) basis;
2.1.2 access to a hosted and maintained Sophos Central console for self-management,; and
2.1.3 subject to level of Subscription, access to advanced reports and threat intelligence.
ENDPOINT PROTECTION. The Cloud Environment leverages auto-updating threat detection tools to monitor for and provide protection from suspicious activities and malware (collectively, “Malicious Activity”) on in-scope endpoints. insightsoftware does not monitor Customer Data for Malicious Activity.
ENDPOINT PROTECTION. All customer data will reside within secure data centre environments. Data transported using portable media including laptop PCs, USB sticks; removable hard-disks and CD/DVD are limited to the absolutely minimum. The following security controls will be implemented if information is transported using any removable media:
ENDPOINT PROTECTION. Supplier will provide Endpoint Protection software and the SaaS platform to manage the endpoints. Supplier will also provide staff to manage, tune and support the platform. The following are included: Windows – FileScan; ContentControl; UserControl; Application Backlisting; DataProtection; TrafficScan; AntiPhishing Firewall; BehavioralScan; MailServers (Exchange - only servers); DeviceControl; AntiExploit. Mac – FileScan; Update Server; and Content Control with TrafficScan + Antiphishing Linux – FileScan; and Update Server Customer will install the software to secure endpoints and/or entry points on Customer’s end-user devices to prevent file- based malware and detect and block malicious activity through automated vulnerability scanning.
ENDPOINT PROTECTION. 14.1 - For Kyos Assist or Kyos Serenity customers, Kyos provides next generation endpoint protection software for any compatible User Equipment, Core Equipment or Virtual Server. Endpoint protection for a Component is a mandatory requirement for inclusion in the Kyos Assist or Kyos Serenity contract.
ENDPOINT PROTECTION. The MSP will administrate and monitor the Sophos Antivirus software. Alerts from Sophos will be integrated with the MSP alert and ticketing system.
ENDPOINT PROTECTION. Device information alongside the security and anti-virus protection alerts per device as well as historic alert data (affected device, malware type, date etc.). • Endpoint Protection/Endpoint Detection & Response: Contact information, IP address and device information, License data, machine and user specific data, location data, and other data required to provide the service. Some data will be processed to improve threat identification as part of the service. • Mobile Device Management: certain license information, your name, email address, username, IP address, meta data, location data, login credentials and mobile device data and similar in order to activate your license, respectively link it to your account and for the use of mobile de vice management more broadly. In addition, data changed through linked 3rd party accounts may be synced with your TeamViewer account and merged with data in the TeamViewer service. • Backup: Any data that the Customer chooses to backup, e.g., various files and folders that may include personal data. All data is encrypted, and only the Customer is able to download and decrypt the content from the backup. The creation, storage, recovery, and deletion of backups is executed in line with the parameters defined by the Customer. • IoT: Content data exchanged between TeamViewer clients during an IoT connection session (e.g., file transfers, remote control commands); data in connection with sensor management, e.g., IoT sensor information (Sensor ID, sensor names, metric names, metric value type (i.e., Celsius, kilogram, meter), data type (text, number, etc.) as well as IoT API credentials (e.g., certificates and credentials used to authenticate IoT devices to push IoT sensor data); data in connection with the analysis, visualization and setting of the measurements from sensors as well as processing of this data in the TeamViewer IoT cloud managed and adjusted by the Customer. • Meeting: subject of meeting, time zone, meeting ID, meeting start time, meeting end time; meeting scheduling and outlook integration (e.g., time and date of meetings, participants etc.); user account information (TeamViewer ID, username, IP address, profile picture, language settings, meeting ID, phone number, location, password). • Service Camp/Service Desk: Personal data in connection with ticket processing and reporting (e.g., TeamViewer IDs, emails, ticket subjects, date and time of tickets, content of the tickets, assignees as well as parameters defin...
ENDPOINT PROTECTION. Device information alongside the security and anti-virus protection alerts per device as well as historic alert data (af- fected device, malware type, date etc.). • Endpoint Protection/Endpoint Detection & Response: Contact infor- mation, IP address and device information, License data, machine and user specific data, location data, and other data required to provide the service. Some data will be processed to improve threat identification as part of the service. • Mobile Device Management: certain license information, your name, email address, username, IP address, meta data, location data, login cre- dentials and mobile device data and similar in order to activate your li- cense, respectively link it to your account and for the use of mobile de- vice management more broadly. In addition, data changed through linked 3rd party accounts may be synced with your TeamViewer account and merged with data in the TeamViewer service. • Backup: Any data that the Customer chooses to backup, e.g., various files and folders that may include personal data. All data is encrypted, and only the Customer is able to download and decrypt the content from the backup. The creation, storage, recovery, and deletion of backups is exe- cuted in line with the parameters defined by the Customer. • IoT: Content data exchanged between TeamViewer clients during an IoT connection session (e.g., file transfers, remote control commands); data in connection with sensor management, e.g., IoT sensor information (Sensor ID, sensor names, metric names, metric value type (i.e., Celsius, kilogram, meter), data type (text, number, etc.) as well as IoT API creden- tials (e.g., certificates and credentials used to authenticate IoT devices to push IoT sensor data); data in connection with the analysis, visualiza- tion and setting of the measurements from sensors as well as processing of this data in the TeamViewer IoT cloud managed and adjusted by the Customer. • Meeting: subject of meeting, time zone, meeting ID, meeting start time, meeting end time; meeting scheduling and outlook integration (e.g., time and date of meetings, participants etc.); user account information (TeamViewer ID, username, IP address, profile picture, language set- tings, meeting ID, phone number, location, password). • Service Camp/Service Desk: Personal data in connection with ticket processing and reporting (e.g., TeamViewer IDs, emails, ticket subjects, date and time of tickets, content of the tickets, assignees as well as...
ENDPOINT PROTECTION. Windows based MANAGED DEVICES are protected with MANAGED SECURITY PLATFORMS.