Interconnection Security Agreement Sample Contracts
Interconnection Security Agreement for Cloud Connectivity PROTECTED A Between Shared Services Canada and Department: <Department> Version: 1.4 Date: June 17, 2020Interconnection Security Agreement • June 17th, 2020
Interconnection Security Agreement Between Universal Service Administrative Company (“USAC”) SERVICE PROVIDER Governing Interconnection Between USAC National Lifeline Accountability Database and/or National Verifier (“NLAD and/or NV”) Service Provider...Interconnection Security Agreement • September 13th, 2022
Interconnection Security Agreement for Project Assessment and Reporting SystemInterconnection Security Agreement • October 28th, 2010
Interconnection Security Agreement BetweenInterconnection Security Agreement • January 28th, 2020
Interconnection Security Agreement ExamplesInterconnection Security Agreement • August 30th, 2021
iVnitlelifromrmingalend Fpluenmk sUqrubabnbulsenoervteinrsw. iIlmliepsoblitleaHkalystwyhseonmMetitimchepselonatsthheis gaonoygcoalrpdleigxa. nCkaitncdalesdtliningelaulcstoabifly.
INTERCONNECTION SECURITY AGREEMENT BETWEEN {REQUESTING PARTY} AND {HOSTING PARTY} {DATE} {PARTY SEAL(S) OPTIONAL} Prepared by: {INITIATING PARTY} {ADDRESS} Prepared for: {PARTY} (optional)Interconnection Security Agreement • September 3rd, 2021
This ISA is valid for {duration} after the last date on either signature below. At that time, it will be updated, reviewed, and reauthorized. This ISA must also be updated, reviewed, verified, and/or revised, as required, for any separate events during the {duration} validity period. Either party may terminate this agreement upon {days} advanced notice in writing, or in the event of a security incident that necessitates an immediate response.
INTERCONNECTION SECURITY AGREEMENTInterconnection Security Agreement • April 25th, 2008
INTERCONNECTION SECURITY AGREEMENTInterconnection Security Agreement • August 19th, 2020
[NOTE: While this template is not classified in any manner, each completed ISA is "For Official Use Only" at a minimum. An ISA may be classified if required. Delete this note.]
Interconnection Security Agreement withInterconnection Security Agreement • June 22nd, 2018
Agreement PurposeInterconnection Security Agreement • March 12th, 2025
This ISA is intended to minimize security risks and ensure the confidentiality, integrity, and availability of shared data and systems that have a network interconnection with Axon Enterprise, Inc. for the benefit of the Governmental Unit. This ISA ensures the adequate security of shared data and systems being accessed and provides that all network access satisfies the requirements of the parties.
System Name (SYSTEM ACRONYM)] Interconnection Security Agreement (ISA)Interconnection Security Agreement • June 5th, 2015
The requirements for interconnection between [Organization A Name] and [Organization B Name] are for the express purpose of exchanging data between [System Name (System Acronym)], owned by [Organization A Name], and [System Name (System Acronym)], owned by [Organization B Name]. [Organization B Name] requires the use of [Organization A Name’s] [Component Name] and [Organization A Name] requires the use of [Organization B Name’s] [Component Name], as approved and directed by the Director of [Department or Agency Name].
INTERCONNECTION SECURITY AGREEMENTInterconnection Security Agreement • March 11th, 2021
This INTERCONNECTION SECURITY AGREEMENT (“ISA”), dated MONTH, YEAR (the “Effective Date”), is between the UNIVERSAL SERVICE ADMINISTRATIVE COMPANY (“USAC”), a not-for-profit corporation organized under the laws of Delaware, and SERVICE PROVIDER.
INTERCONNECTION SECURITY AGREEMENT BETWEEN NIST AND iEdison ORGANIZATIONSInterconnection Security Agreement • November 19th, 2024
This ISA applies to users of iEdison – institutions, private companies, other Federal agencies – that plan to use the iEdison Application Programming Interface (API).
INTERCONNECTION SECURITY AGREEMENTInterconnection Security Agreement • July 26th, 2017
INTERCONNECTION SECURITY AGREEMENT Between the {ETS Contractor}, GSA-Federal Acquisition Service E-Gov Travel Program Management Office, and {Agency} (Seal/Logo goes here if desired) {Include Date here}Interconnection Security Agreement • November 29th, 2011