Joint Security Requirements Sample Clauses

Joint Security Requirements. 33.11.2.1 Both Parties will maintain accurate and auditable records that monitor user authentication and machine integrity and confidentiality (e.g., password assignment and aging, chronological logs configured, system accounting data, etc.). 33.11.2.2 Both Parties shall maintain accurate and complete records detailing the individual data connections and systems to which they have granted the other Party access or interface privileges. These records will include, but are not limited to, userID assignment, user request records, system configuration, and time limits of user access or system interfaces. These records should be kept until the termination of this Agreement or the termination of the requested access by the identified individual. Either Party may initiate a compliance review of the connection records to verify that only the agreed to connections are in place and that the connection records are accurate. 33.11.2.3 Each Party shall notify the other party immediately, upon termination of employment of an individual user with approved access to the other Party’s network. 33.11.2.4 Both Parties shall use an industry standard virus detection software program at all times. The Parties shall immediately advise each other by telephone upon actual knowledge that a virus or other malicious code has been transmitted to the other Party. 33.11.2.5 All physical access to equipment and services required to transmit data will be in secured locations. Verification of authorization will be required for access to all such secured locations. A secured location is where walls and doors are constructed and arranged to serve as barriers and to provide uniform protection for all equipment used in the data connections which are made as a result of the user’s access to either CLEC or SBC-13STATE network. At a minimum, this shall include: access doors equipped with card reader control or an equivalent authentication procedure and/or device, and egress doors which generate a real-time alarm when opened and which are equipped with tamper resistant and panic hardware as required to meet building and safety standards. 33.11.2.6 Both Parties shall maintain accurate and complete records on the card access system or lock and key administration to the rooms housing the equipment utilized to make the connection(s) to the other Party’s network. These records will include management of card or key issue, activation or distribution and deactivation.
AutoNDA by SimpleDocs
Joint Security Requirements. 7.3.1 Both Parties will maintain accurate and auditable records that monitor user authentication and machine integrity and confidentiality (e.g., password assignment and aging, chronological logs configured, system accounting data, etc.).
Joint Security Requirements. 8.2.1 Both Parties will maintain accurate and auditable records that monitor user authentication and machine integrity and confidentiality (e.g., password assignment and aging, chronological logs configured, system accounting data, etc.). 8.2.2 Both Parties shall maintain accurate and complete records detailing the individual data connections and systems to which they have granted the other Party access or interface privileges. These records will include, but are not limited to, user ID assignment, user request records, system configuration, time limits of user access or system interfaces. These records should be kept until the termination of this Agreement or the termination of the requested access by the identified individual. Either Party may initiate a compliance review of the connection records to verify that only the agreed to connections are in place and that the connection records are accurate. 8.2.3 Each Party shall notify the other party immediately, upon termination of employment of an individual user with approved access to the other Party’s network. 8.2.4 Both Parties shall use an industry standard virus detection software program at all times. The Parties shall immediately advise each other by telephone upon actual knowledge that a virus or other malicious code has been transmitted to the other Party. 8.2.5 All physical access to equipment and services required to transmit data will be in secured locations. Verification of authorization will be required for access to all such secured locations. A secured location is where walls and doors are constructed and arranged to serve as barriers and to provide uniform protection for all equipment used in the data connections which are made as a result of the user’s access to either the WSP or
Joint Security Requirements. 9.3.1 Both Parties will maintain accurate and auditable records that monitor user authentication and machine integrity and confidentiality (e.g., password assignment and aging, chronological logs configured, system accounting data, etc.). 9.3.2 Both Parties shall maintain accurate and complete records detailing the individual data connections and systems to which they have granted the other Party access or interface privileges. These records will include, but are not limited to, user ID assignment, user request records, system configuration, time limits of user access or system interfaces. These records should be kept until the termination of this Agreement or the termination of the requested access by the identified individual. Either Party may initiate a compliance review of the connection records to verify that only the agreed to connections are in place and that the connection records are accurate. 9.3.3 CARRIER shall immediately notify AT&T-22STATE when an employee user ID is no longer valid (e.g. employee termination or movement to another department). 9.3.4 The Parties shall use an industry standard virus detection software program at all times. The Parties shall immediately advise each other by telephone upon actual knowledge that a virus or other malicious code has been transmitted to the other Party. 9.3.5 All physical access to equipment and services required to transmit data will be in secured locations. Verification of authorization will be required for access to all such secured locations. A secured location is where walls and doors are constructed and arranged to serve as barriers and to provide uniform protection for all equipment used in the data connections which are made as a result of the user’s access to either the CARRIER’s or
Joint Security Requirements. 9.2.1 Both Parties will maintain accurate and auditable records that monitor user authentication and machine integrity and confidentiality (e.g., password assignment and aging, chronological logs configured, system accounting data, etc.). 9.2.2 Both Parties shall maintain accurate and complete records detailing the individual data connections and systems to which they have granted the other Party access or interface privileges. These records will include, but are not limited to, user ID assignment, user request records, system configuration, time limits of user access or system interfaces. These records should be kept until the termination of this Agreement or the termination of the requested access by the identified individual. Either Party may initiate a compliance review of the connection records to verify that only the agreed to connections are in place and that the connection records are accurate. 9.2.3 CLEC shall immediately notify the ISCC when a employee user ID is no longer valid (e.g. employee termination or movement to another department). 9.2.4 Both Parties shall use an industry standard virus detection software program at all times. The Parties shall immediately advise each other by telephone upon actual knowledge that a virus or other malicious code has been transmitted to the other Party. 9.2.5 All physical access to equipment and services required to transmit data will be in secured locations. Verification of authorization will be required for access to all such secured locations. A secured location is where walls and doors are constructed and arranged to serve as barriers and to provide uniform protection for all equipment used in the data connections which are made as a result of the user’s access to either the CLEC or SBC-13STATE network. At a minimum, this shall include: access doors equipped with card reader control or an equivalent authentication procedure and/or Page 76 of 113 device, and egress doors which generate a real-time alarm when opened and which are equipped with tamper resistant and panic hardware as required to meet building and safety standards. 9.2.6 Both Parties shall maintain accurate and complete records on the card access system or lock and key administration to the rooms housing the equipment utilized to make the connection(s) to the other Party’s network. These records will include management of card or key issue, activation or distribution and deactivation.
Joint Security Requirements. 8.3.1 Both Parties will maintain accurate and auditable records that monitor user authentication and machine integrity and confidentiality (e.g., password assignment and aging, chronological logs configured, system accounting data, etc.). 8.3.2 Both Parties shall maintain accurate and complete records detailing the individual data connections and systems to which they have granted the other Party access or interface privileges. These records will include, but are not limited to, user ID assignment, user request records, system configuration, time limits of user access or system interfaces. These records should be kept until the termination of this Agreement or the termination of the requested access by the identified individual. Either Party may initiate a compliance review of the connection records to verify that only the agreed to connections are in place and that the connection records are accurate. 8.3.3 CLEC shall immediately notify the AT&T-21STATE when an employee user ID is no longer valid (e.g., employee termination or movement to another department). Page 53 of 127 Contract Id: 4875779

Related to Joint Security Requirements

  • Residency Requirements 1. All single first-year freshmen students are required to live in University housing for at least two academic semesters. All single students who have earned less than 30 credit hours and have not resided in University housing for two academic semesters are required to live on campus for two academic semesters. This policy does not apply to single first-year students who have been out of high school for more than one year, or to single first-year freshmen who live with their parents in Miami-Dade or Broward Counties. Neither does it apply to those students who, for disciplinary or administrative reasons, may be denied the privilege of continued residency on campus. 2. Undergraduate students residing in University housing must be regularly enrolled students of the University, taking a minimum of 12 credit hours each semester. Graduate students (when housed by exception) must carry a minimum of nine credit hours per semester. To apply and sign-up for University Village apartments, students must have 45 or more completed academic credits. In order to move into University Village, students must have 60 or more completed academic credits or have completed 4 academic semesters at the University and be achieving satisfactory academic progress as defined by the University Bulletin.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!