Email Security (EMS Sample Clauses

Email Security (EMS. EMS from Censornet is a 100% cloud-based service that analyzes email traffic and removes unwanted or malicious messages. The service scans all inbound (and outbound) messages for threats including malware and phishing attacks, and examines URLs embedded in messages protecting users from inappropriate or malicious web pages. Organisations route email through Censornet’s Cloud by changing their MX record. We use world-class, highly accredited providers to deliver EMS that include Amazon, IBM and Microsoft. In Europe specific data centre locations include Frankfurt, Dublin and Amsterdam. Organizations choose which data centre or centres process their mail. In the UK data centre locations include London. In the US data centre locations include Wyoming, Texas and Virginia. In the UAE data centre locations include Dubai. Email messages flow through the infrastructure within the selected data centre(s) above and are checked for spam and viruses and other content. If the message is ‘clean’ it is logged and delivered to the customer’s email server. The conversation with the customer’s email server is also logged. Log information includes IP addresses, To, From and Subject fields, server responses, and other metadata, but does not include the message body or any file attachments. Log data is stored in the same data centre that processes email traffic. Some log data may be replicated for reporting and visualization. The ‘home’ region selected at the time of account provisioning determines the location of this data. During processing the message is written to disk. Once delivered to the customer’s email server it is immediately deleted. This typically takes no more than a few seconds. If a message is determined to be spam then the message may optionally be written to a quarantine where it is stored for thirty (30) days. Organization’s may choose to delete spam rather than quarantine it. The quarantine is located specifically in the following data centres: Amsterdam (for UK and EU customers), Dallas TX (for US customers) and Dubai (for UAE customers).
View SourceView Similar (2)
Email Security (EMS. EMS from Censornet is a 100% cloud-based service that analyzes email traffic and removes unwanted or malicious messages. The service scans all inbound (and outbound) messages for threats including malware and phishing attacks, and examines URLs embedded in messages protecting users from inappropriate or malicious web pages. Organisations route email through Censornet’s Cloud by changing their MX record. Certain EMS features use API integration with Microsoft Exchange Online via the MS Graph API and appropriate access must be granted explicitly to use these features (e.g. Post Deliver Deletion of previously delivered messages). The Censornet email solution is an Integrated Cloud Email Security (ICES) solution. We use world-class, highly accredited providers to deliver EMS that include Amazon, IBM and Microsoft. In Europe specific data centre locations include Frankfurt, Dublin and Amsterdam. Organizations choose which data centre or centres process their mail. In the UK data centre locations include London. In the US data centre locations include Wyoming, Texas and Virginia. In the UAE data centre locations include Dubai. In India data centre locations include Pune. Email messages flow through the infrastructure within the selected data centre(s) above and are checked for spam and viruses and other content. If the message is ‘clean’ it is logged and delivered to the customer’s email server. The conversation with the customer’s email server is also logged. Log information includes IP addresses, To, From and Subject fields, server responses, and other metadata, but does not include the message body or any file attachments. Log data is stored in the ‘home’ region selected at the time of account provisioning. Some log data may be replicated for optimisation, reporting and visualization purposes in the same data centre that processes email traffic. During processing the message is written to disk. Once successfully delivered to the customer’s email server it is immediately deleted. This typically takes no more than a few seconds. If a message is determined to be spam then the message may optionally be written to a quarantine where it is stored for thirty (30) days. Organization’s may choose to delete spam rather than quarantine it. The quarantine is located specifically in the following data centres: Amsterdam (for UK and EU customers) Dallas TX (for US customers), Dubai (for UAE customers) and Pune (for India).
View SourceView Similar (2)
Email Security (EMS. EMS from Censornet is a 100% cloud-based service that analyses email traffic and removes unwanted or malicious messages. The service scans all inbound (and outbound) messages for threats including malware and phishing attacks, and examines URLs embedded in messages protecting users from inappropriate or malicious web pages. Organisations route email through Censornet’s Cloud by (a) changing their DNS MX record or (b) using the ‘Connector Mode’ for Microsoft 365 via Transport Rules. Certain EMS features use API integration with Microsoft Exchange Online via the MS Graph API and appropriate access must be granted explicitly to use these features (e.g. Post Deliver Deletion of previously delivered messages). Using Microsoft Transport Rules and Connectors requires registration of the Censornet Email Security application within Microsoft Entra ID and assigned the Exchange Administrator role. We use world-class, highly accredited providers to deliver EMS that include Amazon and Microsoft. In Europe specific data centre locations include Frankfurt, Dublin and Amsterdam. Organizations choose which data centre or centres process their mail. In the UK data centre locations include London. In the US data centre locations include Wyoming, Texas and Virginia. Email messages flow through the infrastructure within the selected data centre(s) above and are checked for spam and viruses and other content. If the message is ‘clean’ it is logged and delivered to the customer’s email server. The conversation with the customer’s email server is also logged. Log information includes IP addresses, To, From and Subject fields, server responses, and other metadata, but does not include the message body or any file attachments. Log data is stored in the ‘home’ region selected at the time of account provisioning. Some log data may be replicated for optimisation, reporting and visualization purposes in the same data centre that processes email traffic. During processing the message is written to disk. Once successfully delivered to the customer’s email server it is immediately deleted. This typically takes no more than a few seconds except in the event that processing queues are created through a transient spike in optionally be SMTP traffic. If a message is determined to be spam then the message may written to a quarantine where it is stored for thirty (30) days. Organization’s may choose to delete spam rather than quarantine it. The quarantine is located specifically in the selected...
View SourceView Similar (2)

Related to Email Security (EMS

  • Contractor Security Clearance Customers may designate certain duties and/or positions as positions of “special trust” because they involve special trust responsibilities, are located in sensitive locations, or have key capabilities with access to sensitive or confidential information. The designation of a special trust position or duties is at the sole discretion of the Customer. Contractor or Contractor’s employees and Staff who, in the performance of this Contract, will be assigned to work in positions determined by the Customer to be positions of special trust, may be required to submit to background screening and be approved by the Customer to work on this Contract.

  • Delivery and Control of Security Collateral (a) Any certificates or instruments representing or evidencing Security Collateral shall be delivered to and held by or on behalf of the Collateral Trustee pursuant hereto and shall be in suitable form for transfer by delivery, or shall be accompanied by duly executed instruments of transfer or assignment in blank, all in form and substance satisfactory to the Collateral Trustee. The Collateral Trustee shall have the right, at any time in its discretion and without notice to any Pledgor, to transfer to or to register in the name of the Collateral Trustee or any of its nominees any or all of the certificates and instruments representing or evidencing the Security Collateral, if any, subject only to the revocable rights specified in Section 9(a). In addition, the Collateral Trustee shall have the right at any time to exchange certificates or instruments representing or evidencing Security Collateral, if any, for certificates or instruments of smaller or larger denominations. (b) At such time as any Pledgor has or acquires any Security Collateral in which such Pledgor has any right, title or interest and that constitutes an “uncertificated security” (within the meaning of Article 8 of the UCC), such Pledgor will use its commercially reasonable efforts to cause the issuer thereof to agree in an authenticated record substantially in the form of Exhibit B with such Pledgor and the Collateral Trustee that such issuer will comply with instructions with respect to such security originated by the Collateral Trustee without further consent of such Pledgor, such authenticated record to be in form and substance satisfactory to such issuer and the Collateral Trustee. (c) With respect to any Pledged Equity in which any Pledgor has any right, title or interest and that is not a security (within the meanings of Article 8 and Article 9 of the UCC), such Pledgor will notify each such issuer of Pledged Equity that such Pledged Equity is subject to the security interest granted hereunder. (d) With respect to any Pledged Debt in which any Pledgor has any right, title or interest, the Pledgor will notify each such issuer of Pledged Debt that such Pledged Debt is subject to the security interest granted hereunder. (e) If, at any time, an issuer converts any Pledged Equity into a “security” within the meaning of Articles 8 and 9 of the UCC, the relevant Pledgor will either (i) use its commercially reasonable efforts to cause the issuer of such Pledged Equity to issue certificates or instruments evidencing or representing the Pledged Equity and deliver the originals of such certificates or instruments promptly to the Collateral Trustee (or as directed by the Collateral Trustee), and, if it or any Person other than the relevant Pledgor, receives any such certificates or instruments, shall promptly deliver or cause to be delivered to the Collateral Trustee, the originals of such certificates or instruments or (ii) if the security is an uncertificated security (within the meaning of Article 8 of the UCC), use its commercially reasonable efforts to cause the issuer of such Pledged Equity to enter into an Uncertificated Securities Control Agreement pursuant to clause (b) above. (f) At such time as any Pledgor has or acquires any Security Collateral in which such Pledgor has any right, title or interest and that is not a security (within the meaning of Article 8 of the UCC), such Pledgor agrees that the Collateral Trustee may file a financing statement in the relevant jurisdiction. (g) No Pledgor shall take or omit to take any action which would or could reasonably be expected to have the result of materially adversely affecting or impairing the Liens in favor of the Collateral Trustee and the holders of Parity Lien Obligations with respect to the Collateral.

  • Technical Security Controls 35 a. Workstation/Laptop encryption. All workstations and laptops that store PHI COUNTY 36 discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of 37 COUNTY either directly or temporarily must be encrypted using a FIPS 140-2 certified algorithm which 1 is 128bit or higher, such as AES. The encryption solution must be full disk unless approved by the 2 COUNTY.

  • Data Security and Privacy Plan As more fully described herein, throughout the term of the Master Agreement, Vendor will have a Data Security and Privacy Plan in place to protect the confidentiality, privacy and security of the Protected Data it receives from the District. Vendor’s Plan for protecting the District’s Protected Data includes, but is not limited to, its agreement to comply with the terms of the District’s Bill of Rights for Data Security and Privacy, a copy of which is set forth below and has been signed by the Vendor. Additional components of Vendor’s Data Security and Privacy Plan for protection of the District’s Protected Data throughout the term of the Master Agreement are as follows: (a) Vendor will implement all state, federal, and local data security and privacy requirements including those contained within the Master Agreement and this Data Sharing and Confidentiality Agreement, consistent with the District’s data security and privacy policy. (b) Vendor will have specific administrative, operational and technical safeguards and practices in place to protect Protected Data that it receives from the District under the Master Agreement. (c) Vendor will comply with all obligations contained within the section set forth in this Exhibit below entitled “Supplemental Information about a Master Agreement between Chazy Central Rural School District and [Name of Vendor].” Vendor’s obligations described within this section include, but are not limited to: (i) its obligation to require subcontractors or other authorized persons or entities to whom it may disclose Protected Data (if any) to execute written agreements acknowledging that the data protection obligations imposed on Vendor by state and federal law and the Master Agreement shall apply to the subcontractor, and (ii) its obligation to follow certain procedures for the return, transition, deletion and/or destruction of Protected Data upon termination, expiration or assignment (to the extent authorized) of the Master Agreement. (d) Vendor has provided or will provide training on the federal and state laws governing confidentiality of Protected Data for any of its officers or employees (or officers or employees of any of its subcontractors or assignees) who will have access to Protected Data, prior to their receiving access. (e) Vendor will manage data security and privacy incidents that implicate Protected Data and will develop and implement plans to identify breaches and unauthorized disclosures. Vendor will provide prompt notification to the District of any breaches or unauthorized disclosures of Protected Data in accordance with the provisions of Section 5 of this Data Sharing and Confidentiality Agreement.

  • Data Security and Privacy Except as would not, individually or in the aggregate, reasonably be expected to be material to the business of the Company Group, taken as a whole, the Company and each of its Subsidiaries (i) is in compliance with all Data Security Requirements and (ii) has taken commercially reasonable steps consistent with standard industry practice by companies of similar size and maturity, and in compliance in all material respects with all Data Security Requirements to protect (A) the confidentiality, integrity, availability and security of its Business Systems that are involved in the Processing of Personally Identifiable Information, in the conduct of the business of the Company and its Subsidiaries as currently conducted; and (B) Personally Identifiable Information Processed by or on behalf of the Company or such Subsidiary or on their behalf from unauthorized use, access, disclosure, theft and modification. Except as would not, individually or in the aggregate, reasonably be expected to be material to the business of the Company Group, taken as a whole, (i) there are, and since January 1, 2022, have been, no pending complaints, investigations, inquiries, notices, enforcement proceedings, or Actions by or before any Governmental Authority and (ii) since January 1, 2022, no fines or other penalties have been imposed on or written claims, notice, complaints or other communications have been received by the Company or any Subsidiary, relating to any Specified Data Breach or alleging non-compliance with any Data Security Requirement. The Company and each of its Subsidiaries have not, since January 1, 2022, (1) experienced any Specified Data Breaches, or (2) been involved in any Legal Proceedings related to or alleging any violation of any Data Security Requirements by the Company Group or any Specified Data Breaches, each except as would not be material to the business of the Company Group, taken as a whole. The consummation of the transactions contemplated by this Agreement will not cause the Company Group to breach any Data Security Requirement, except as would not reasonably be expected to be material to the business of the Company Group, taken as a whole.