Security Guide for Interconnecting Information Technology Systems Sample Clauses

Security Guide for Interconnecting Information Technology Systems. This agreement will be reviewed annually and will be re-signed by all parties every third year. RMA CIS Xxxx Xxxxx Date Information System Owner Xxxxxx Xxxxxx Date Information System Security Program Manager Xxxxxxx Xxxxxxxx Date CIS Authorizing Official [AIP System Name (System Acronym)] Name Date Title x [AIP System Name (System Acronym)] System Owner (assignment of security responsibility): Name Date Title [AIP System Name (System Acronym)] System Security Officer: Name Date Title x [AIP System Name (System Acronym)] CIO/COO/Director or designee: (responsible executive) Table of Contents NONDISCLOSURE STATEMENTS II INTERCONNECTION SECURITY AGREEMENT AUTHORIZATION 1 1 INTRODUCTION 4 2 CONNECTION PURPOSE 4 2.1 System Identification 4
Sample 1Sample 2Sample 3See All (6)
AutoNDA by SimpleDocs
Security Guide for Interconnecting Information Technology Systems. This agreement will be reviewed annually and will be re-signed by all Parties on a yearly basis. This ISA, dated MONTH [•], YEAR (the “Effective Date”), is between USAC and SERVICE PROVIDER. USAC _________________________________ ___________
Sample 1Sample 2
Security Guide for Interconnecting Information Technology Systems. This agreement will be reviewed annually and will be re-signed by all Parties on a yearly basis. This ISA, dated MONTH [•], YEAR (the “Effective Date”), is between USAC and SERVICE PROVIDER. USAC _________________________________ ___________ Name DATE Title __________________________________ ___________ Name DATE Title ----------------------------------------------------------------------------------------------------------- SERVICE PROVIDER OFFICIALS ­­­­­­­­­­­­­­­­­_________________________________ Official Title DATE ­­­­­­­­­­­­­­­­­­­­­­­­­­_________________________________ ___________ Official DATE Title Table of contents 1 Introduction 1 2 Connection Purpose 1 3 Connection Specifics… 3 4 System Vulnerabilities 3 5 Incident Reporting 4 6 Backups/Updates/Changes… 5 7 User Community… 5 8 Rules of Behavior… 6 9 Controls… 6 10 Limitations of Liability… 6 11 Cost Considerations … 7 12 Material Changes to System Configuration… 7 13 Personnel Changes … 8 14 Audit Trail Responsibilities … 8 15 Representations… 8 16 Topological drawings… 9
Sample 1
Security Guide for Interconnecting Information Technology Systems. Memorandum of Agreement (MOA) / Memorandum of Understanding (MOU) Purpose Initiating Party Approval Authority Renewal Timeframe The MOA/U outlines the terms and conditions regarding the development, management, operation, and security of an interconnection between organizational entities for the purpose of establishing a joint project in which they each contribute their own resources and the scope of work is very broad and generally not specific to any one project and there is no exchange of funds between the partners. • Authorized Federal Approving Official/Business Owner (ex. Agency) • Office/Program Director level or higher, from both parties involved. ATO Accreditation period with the potential of extension or as specified otherwise.
Sample 1
Security Guide for Interconnecting Information Technology Systems. Service Level Agreement (SLA) Purpose Initiating Party Approval Authority Renewal Timeframe The SLA specifies relevant service/operational/organization level agreement details between a service provider and CMS. • Service Provider, including program manager or equivalent. • Service Provider, including program manager or equivalent. • CMS contract management staff (e.g. COR) As specified in the contract, and revised upon contract or service provider modification.
Sample 1
Security Guide for Interconnecting Information Technology Systems. At a minimum, the {Agency} shall update their security plan and related documents annually.
Sample 1
Security Guide for Interconnecting Information Technology Systems. This agreement will be reviewed annually and will be re-signed by all parties every third year. RMA Crop Information System (CIS) Name Date RMA Application Owner Name Date X Information System Owner Name Date x RMA Information System Security Manager Name Date x RMA Authorizing Official [System B Name (System Acronym)] Name Date x Information System Owner Name Date [Agency] Information System Security Manager Name Date [System] Authorizing Official Table of Contents DOCUMENT INFORMATION II NONDISCLOSURE STATEMENTS III INTERCONNECTION SECURITY AGREEMENT AUTHORIZATION 1 1 INTRODUCTION 4 2 CONNECTION PURPOSE 4 2.1 System Identification 4 2.2 Connection Purpose and Information Shared/Passed 4 2.3 Information Sensitivity 5 3 BUSINESS REQUIREMENTS 5
Sample 1
AutoNDA by SimpleDocs
Security Guide for Interconnecting Information Technology Systems. In addition to the requirements expressly stated in this Section, CONTRACTOR must comply with any other State or Federal law, regulation, or administrative rule relating to the specific HHSC program area that CONTRACTOR supports.
Sample 1

Related to Security Guide for Interconnecting Information Technology Systems

  • Information Technology Accessibility Standards Any information technology related products or services purchased, used or maintained through this Grant must be compatible with the principles and goals contained in the Electronic and Information Technology Accessibility Standards adopted by the Architectural and Transportation Barriers Compliance Board under Section 508 of the federal Rehabilitation Act of 1973 (29 U.S.C. §794d), as amended. The federal Electronic and Information Technology Accessibility Standards can be found at: xxxx://xxx.xxxxxx-xxxxx.xxx/508.htm.

  • INFORMATION TECHNOLOGY The following applies to all contracts for information technology commodities and contractual services. “Information technology” is defined in section 287.012(15), F.S., to have the same meaning as provided in section 282.0041, F.S.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

  • NYS OFFICE OF INFORMATION TECHNOLOGY SERVICES NOTIFICATION All New York State Agencies must notify the Office of Information Technology Services of any and all plans to procure IT and IT -related products, materials and services meeting required thresholds defined in Technology Policy NYS–P08-001: xxxxx://xxx.xx.xxx/sites/default/files/documents/NYS-P08-001.pdf, as may be amended, modified or superseded. SALES REPORTING REQUIREMENTS Contractor shall furnish OGS with quarterly sales reports utilizing Appendix I - Report of Contract Sales. Purchases by Non- State Agencies, political subdivisions and others authorized by law shall be reported in the same report and indicated as required. All fields of information shall be accurate and complete. OGS reserves the right to unilaterally make revisions, changes and/or updates to Appendix I - Report of Contract Sales or to require sales to be reported in a different format without processing a formal amendment and/or modification. Further, additional related sales information and/or detailed Authorized User purchases may be required by OGS and must be supplied upon request. Reseller Sales Product sold through Reseller(s) must be reported by Contractor in the required Appendix I – Report of Contract Sales. Due Date The Appendix I - Report of Contract Sales will be quarterly (January - March, April - June, July - September and October - December). Reports will be due 1 month after the closing quarter. SERVICE REPORTS FOR MAINTENANCE/SUPPORT AND WARRANTY WORK Service Reports for Authorized User An Authorized User in an RFQ may require compliance with any or all of this section. If requested by the Authorized User, the Contractor shall furnish the Authorized User with service reports for all Maintenance/support and warranty work upon completion of the services. The service reports may include the following information in either electronic or hard copy form as designated by the Authorized User:  Date and time Contractor was notified  Date and time of Contractor’s arrival  Make and model of the Product  Description of malfunction reported by Authorized User  Diagnosis of failure and/or work performed by Contractor  Date and time failure was corrected by Contractor  Type of service – Maintenance/support or warranty  Charges, if any, for the service Service Reports for OGS

  • Accessibility of Information Technology Contractor represents and warrants that any software/ hardware/ communications system/ equipment (collectively “technology”), if any, provided under this Agreement adheres to the standards and/or specifications as may be set forth in the Section 508 of the Rehabilitation Act of 1973 standards guide and is fully compliant with WCAG 2.0 AA standards for accessibility and compliant with any applicable FCC regulations. Technology that will be used on a mobile device must also be navigable with Voiceover on iOS devices in addition to meeting WCAG 2.0 level AA. If portions of the technology or user experience are alleged to be non-compliant or non- accessible at any point, District will provide Contractor with notice of such allegation and Contractor shall use its best efforts to make the technology compliant and accessible. If a state or federal department, office or regulatory agency, or if any other third party administrative agency or organization (“Claimants”), make a claim, allegation, initiates legal or regulatory process, or if a court finds or otherwise determines that technology is non-compliant or non-accessible, Contractor shall indemnify, defend and hold harmless the District from and against any and all such claims, allegations, liabilities, damages, penalties, fees, costs (including but not limited to reasonable attorneys’ fees), arising out of or related to Xxxxxxxxx’ claims. Contractor shall also fully indemnify District for the full cost of any user accommodation that is found to be necessary due to an identifiable lack of accessibility in the Contractor’s technology. If necessary, an independent 3rd party accessibility firm using POUR standards (Perceivable, Operable, Understandable and Robust) may be used to validate the accessibility of the technology.

  • Information Technology Enterprise Architecture Requirements If this Contract involves information technology-related products or services, the Contractor agrees that all such products or services are compatible with any of the technology standards found at xxxxx://xxx.xx.xxx/iot/2394.htm that are applicable, including the assistive technology standard. The State may terminate this Contract for default if the terms of this paragraph are breached.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Electronic and Information Resources Accessibility and Security Standards a. Applicability: The following Electronic and Information Resources (“EIR”) requirements apply to the Contract because the Grantee performs services that include EIR that the System Agency's employees are required or permitted to access or members of the public are required or permitted to access. This Section does not apply to incidental uses of EIR in the performance of the Agreement, unless the Parties agree that the EIR will become property of the State of Texas or will be used by HHSC’s clients or recipients after completion of the Agreement. Nothing in this section is intended to prescribe the use of particular designs or technologies or to prevent the use of alternative technologies, provided they result in substantially equivalent or greater access to and use of a Product.

  • Information and Services Required of the Owner § 3.1.1 The Owner shall provide information with reasonable promptness, regarding requirements for and limitations on the Project, including a written program which shall set forth the Owner’s objectives, constraints, and criteria, including schedule, space requirements and relationships, flexibility and expandability, special equipment, systems, sustainability and site requirements.

  • Joint Network Implementation and Grooming Process Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia:

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