Monitoring and Audit. 7.12.1 To deter unauthorized access events, a warning or no trespassing message will be displayed at the point of initial entry (i.e., network entry or applications with direct entry points). Each Party should have several approved versions of this message. Users should expect to see a warning message similar to this one: 7.12.2 After successful authentication, each session will display the last logon date/time and the number of unsuccessful logon attempts. The user is responsible for reporting discrepancies.
Appears in 10 contracts
Sources: Telecommunications, Peering Agreement, Peering Agreement
Monitoring and Audit. 7.12.1 6.2.10.1 To deter unauthorized access events, a warning or no no-trespassing message will be displayed at the point of initial entry (i.e., network entry or applications with direct entry points). Each Party should have several approved versions of this message. Users should expect to see a warning message similar to this one:
7.12.2 6.2.10.2 After successful authentication, each session will display the last logon date/time and the number of unsuccessful logon attempts. The user is responsible for reporting discrepancies.
Appears in 8 contracts
Sources: Interconnection Agreement, Interconnection Agreement, Interconnection Agreement
Monitoring and Audit. 7.12.1 6.2.10.1 To deter unauthorized access events, a warning or no no- trespassing message will be displayed at the point of initial entry (i.e., network entry or applications with direct entry points). Each Party should have several approved versions of this message. Users should expect to see a warning message similar to this one:
7.12.2 6.2.10.2 After successful authentication, each session will display the last logon date/time and the number of unsuccessful logon attempts. The user is responsible for reporting discrepancies.
Appears in 6 contracts
Sources: Interconnection Agreement, Interconnection Agreement, Interconnection Agreement
Monitoring and Audit. 7.12.1 9.11.1 To deter unauthorized access events, a warning or no trespassing message will be displayed at the point of initial entry (i.e., network entry or applications with direct entry points). Each Party should have several approved versions of this message. Users should expect to see a warning message similar to this one:
7.12.2 9.11.2 After successful authentication, each session will display the last logon date/time and the number of unsuccessful logon attempts. The user is responsible for reporting discrepancies.
Appears in 2 contracts
Sources: XDSL Attachment, Access to Operations Support Systems (Oss) Agreement
Monitoring and Audit. 7.12.1 9.12.1 To deter unauthorized access events, a warning or no trespassing message will be displayed at the point of initial entry (i.e., network entry or applications with direct entry points). Each Party should have several approved versions of this message. Users should expect to see a warning message similar to this one:: CN:07072017-8312 000076
7.12.2 9.12.2 After successful authentication, each session will display the last logon date/time and the number of unsuccessful logon attempts. The user is responsible for reporting discrepancies.
Appears in 1 contract
Sources: Telecommunications
Monitoring and Audit. 7.12.1 9.12.1 To deter unauthorized access events, a warning or no trespassing message will be displayed at the point of initial entry (i.e., network entry or applications with direct entry points). Each Party should have several approved versions of this message. Users should expect to see a warning message similar to this one:
7.12.2 9.12.2 After successful authentication, each session will display the last logon date/time and the number of unsuccessful logon attempts. The user is responsible for reporting discrepancies.
Appears in 1 contract
Sources: Telecommunications Agreement
Monitoring and Audit. 7.12.1 6.2.10.1 To deter unauthorized unaut horized access events, a warning or no no- trespassing message will be displayed at the point of initial entry (i.e., network entry or applications with direct entry points). Each Party should have several approved versions of this message. Users should expect to see a warning message similar to this one:
7.12.2 6.2.10.2 After successful authentication, each session will display the last logon date/time and the number of unsuccessful logon attempts. The user is responsible for reporting discrepancies.
Appears in 1 contract
Sources: Interconnection Agreement
Monitoring and Audit. 7.12.1 8.12.1 To deter unauthorized access events, a warning or no trespassing message will be displayed at the point of initial entry (i.e., network entry or applications with direct entry points). Each Party should have several approved versions of this message. Users should expect to see a warning message similar to this one:
7.12.2 8.12.2 After successful authentication, each session will display the last logon date/time and the number of unsuccessful logon attempts. The user is responsible for reporting discrepancies.
Appears in 1 contract
Sources: Wholesale Agreement
Monitoring and Audit. 7.12.1 11.11.1 To deter unauthorized access events, a warning or no trespassing message will be displayed at the point of initial entry (i.e., network entry or applications with direct entry points). Each Party should have several approved versions of this message. Users should expect to see a warning message similar to this one:
7.12.2 11.11.2 After successful authentication, each session will display the last logon date/time and the number of unsuccessful logon attempts. The user is responsible for reporting discrepancies.
Appears in 1 contract
Sources: Interconnection Agreement