Security Overview Sample Clauses

Security Overview. All IZ Gateway Portfolio Project components are secured at the HIPAA level, leveraging APHL’s security and ensuring confidentiality, integrity and availability. Examples of how IIS Jurisdictions’ IZ information is safeguarded: • All connections into the IZ Gateway use an IZ Gateway digital certificate, ensuring that only authenticated (authorized and verified) systems are allowed to connect. • Outgoing connections only occur with known URLs to ensure data transmission to appropriate recipients. • All IZ information is encrypted while in motion. • IZ Gateway does not use, disclose or decrypt IZ information in Connect/Share/Access. • For Multi-Jurisdictional Data Exchange only, which is still under development, the IZ Gateway will access and decrypt IZ information, such as when routing a query to additional Participating IIS Jurisdictions that are 16 identified by the sender within the message and have executed the MOU.
Sample 1Sample 2
AutoNDA by SimpleDocs
Security Overview. The Demandware security strategy is designed to protect your data at multiple levels, including data security, data integrity, and data privacy. To ensure the privacy, security, and availability of your data and transactions, Demandware employs the following technologies in delivering its service. [**]
Sample 1Sample 2
Security Overview. We make every effort to ensure that your information is protected. We use current industry standard encryption and employ SSL encryption to insure that information passed between our site and your browser is secure. Physical Security All servers involved in gathering, storing, and providing the data to you are operated in a secure data center that has restricted access to authorized personnel only. Our data center is monitored 24 hours per day and only certified employees are permitted on premises. A record is kept of all personnel who have entered the secure data center. Access to servers requires multiple levels of authentication. Sensitive data including your access credentials and account numbers are always stored in encrypted format at all times. Our employees are made aware of our security policies, procedures and practices and confirm, on a yearly basis, that they have carefully reviewed and abide by it.
Sample 1
Security Overview. 8.6.8 Offeror must describe its notification process in the event of a security incident, including relating to timing, incident levels. Offeror should take into consideration that Purchasing Entities may have different notification requirements based on applicable laws and the categorization type of the data being processed or stored. Knowledge Services meets the requirement for a notification process in the event of a security incident, including relating to timing and incident levels. Knowledge Services understands and will comply with the requirement that Purchasing Entities may have different notification requirements based on applicable laws and the categorization type of the data being processed or stored. A robust network security monitoring solution is in place that leverages signature based-software and live analysts monitoring the network traffic of our organization. The false positive rate is extremely low and all events are thoroughly analyzed. In the event of an incident, the third party company alerts a local point of contact to investigate the issue. The third party provides full details regarding the event and recommended remediation steps based on the severity of the issue. • Personnel – A local point of contact from Knowledge Services will be contacted by third party monitoring analyst. The local point of contact from Knowledge Services will notify the Contract Manager, who will then contact Purchasing Entity’s point of contact. • Response times – The response time in the event of a data breach is within an hour of identification of a true positive. • Methods of communication – The methods of communication of a data breach are via a portal, email and phone.
Sample 1
Security Overview. All IZ Gateway use cases/components are secured at the HIPAA level, leveraging The Association of Public Health Laboratories (APHL)’s security and ensuring confidentiality, integrity and availability Examples of how IIS Jurisdictions’ IZ information is safeguarded: • All connections into the IZ Gateway use an IZ Gateway digital certificate, ensuring that only authenticated (authorized and verified) systems are allowed to connect. • Outgoing connections only occur with known URLs to ensure data transmission to appropriate recipients. • All IZ information is encrypted while in motion. • IZ Gateway does not use, disclose or decrypt IZ information in Connect/IIS-IIS Exchange/Access. Highly Sensitive/Any User (No encryption) • For Multi-Jurisdictional Data Exchange only, which is still under development, the IZ Gateway will access and decrypt IZ information, such as when routing a query to additional participating IIS jurisdictions that are identified by the sender within the message and have executed the MOU. What Happens in the Event of a Breach? Highly Sensitive/Any User (No encryption) Provider Organizations Per DUA with IIS Jurisdiction, APHL will notify jurisdiction promptly of a data breach.
Sample 1
Security Overview. Using the Online Banking login on the xxx.xxxxxxx.xxx pages is safe, since your account number/username and password are transmitted via secure session that is established between your browser and our systems. Your information is encrypted using 128-bit encryption algorithm and sent to our systems for authentication into Online Banking. Please note ACU never transmits your information without it first being encrypted. You acknowledge the Internet is inherently insecure and all data transfers, including electronic mail, occur openly on the Internet and potentially can be monitored and read by others. Requests for personal information should only be sent to us through the Message Board in your Online Banking account. We cannot and do not warrant data transfers utilizing the open Internet.
Sample 1

Related to Security Overview

  • Project Overview Project Title [Drafting note: ARENA to complete. Insert full long name in accordance with ARENA’s naming convention] i.e. [GMS Number] [Powerworks, voltage control on the Pacific Islands Study] [GMS Number] [study/ project/ fellowship/ scholarship/ R&D Project] Contract Number [Drafting note: ARENA to complete – to be obtained from ARENA’s GMS] Recipient [Drafting note: Recipient to insert full legal name and ABN] Guidelines and policies Advancing Renewables Program – Program Guidelines, 2020 (xxxxx://xxxxx.xxx.xx/xxxxxx/0000/00/XXXXX_XXX_Xxxxxxxxxx_XX_Xxxxxx_Xxxxx_XXXXX.xxx) ARENA Variation Policy (xxxxx://xxxxx.xxx.xx/xxxxxx/0000/00/xxxxx-xxxxxxx-xxxxxxxxx-xxxxxxxxx-xxxxxx.xxx) ARENA Report Writing Guidelines (xxxxx://xxxxx.xxx.xx/xxxxxx/0000/00/xxxxx-xxxxxx-xxxxxxx-xxxxxxxxxx.xxx)

  • Security Badging Any Company employee, or any employee of its contractors or agents, that require unescorted access to the Security Identification Display Area (SIDA) to perform work under this Agreement will be badged with an Airport identification badge (hereinafter referred to as "Badge") provided by Authority’s ID Badging Department and will be subject to an FBI fingerprint-based criminal history records check (CHRC) and an annual Security Threat Assessment (STA). A new or renewed Badge will not be issued to an individual until the results of the CHRC and the STA are completed and indicate that the applicant has not been convicted of a disqualifying criminal offense. If the CHRC or STA discloses a disqualifying criminal offense, the individual’s new or renewed badge application will be rejected. The costs of the CHRC and the annual STA will be paid by Company. These costs are subject to change without notice, and Company will be responsible for paying any increase in the costs. All badged employees of Company and its contractors or agents will comply with Authority's regulations regarding the use and display of Badges. Company will be assessed a fine for each Badge that is lost, stolen, unaccounted for or not returned to Authority at the time of Badge expiration, employee termination, termination of the Agreement, or upon written request by Authority. This fine will be paid by Company within 15 days from the date of invoice. The fine is subject to change without notice, and Company will be responsible for paying any increase in the fine. If any Company employee is terminated or leaves Company’s employment, Authority must be notified immediately, and the Badge must be returned to Authority promptly.

  • Agreement Overview This SLA operates in conjunction with, and does not supersede or replace any part of, the Agreement. It outlines the information technology service levels that we will provide to you to ensure the availability of the application services that you have requested us to provide. All other support services are documented in the Support Call Process.

  • Security of Data a. Each of the parties shall:

  • Overview (a) The Employer is committed to maintaining a stable and skilled workforce, recognising its contribution to the operation of the Employer. As such, full time direct and ongoing employment is a guiding principle of this Agreement.

  • Security Assessment If Accenture reasonably determines, or in good faith believes, that Supplier’s security practices or procedures do not meet Supplier’s obligations under the Agreement, then Accenture will notify Supplier of the deficiencies. Supplier will without unreasonable delay: (i) correct such deficiencies at its own expense; (ii) permit Accenture, or its duly authorized representatives, to assess Supplier’s security-related activities that are relevant to the Agreement; and (iii) timely complete a security questionnaire from Accenture on a periodic basis upon Accenture’s request. Security issues identified by Accenture will be assigned risk ratings and an agreed-to timeframe to remediate. Supplier will remediate all the security issues identified within the agreed to timeframes. Upon Supplier’s failure to remediate any high or medium rated security issues within the stated timeframes, Accenture may terminate the Agreement in accordance with Section 8 above.

  • Registry Interoperability and Continuity Registry Operator shall comply with the Registry Interoperability and Continuity Specifications as set forth in Specification 6 attached hereto (“Specification 6”).

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

  • Project Name Register ASIC

  • Security Bond The security bond provides protection to Owner if Contractor presents an acceptable guaranteed maximum price (“GMP”) to Owner but is unable to deliver the required payment and performance bonds within the time period stated below.

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