Mobile Computing Devices Clause Samples

Mobile Computing Devices. To ensure that Mobile Computing Devices (MCDs) do not introduce threats into systems that process or store County information, departments’ management shall: 2.2.3.1 Establish and manage a process for authorizing, issuing and tracking the use of MCDs. 2.2.3.2 Permit only authorized MCDs to connect to County information assets or networks that store, process, transmit, or connects to County information and information assets. 2.2.3.3 Implement applicable access control requirements in accordance with this policy, such as the enforcement of a system or device lockout after 15 minutes of inactivity requiring re-entering of a password to unlock. 2.2.3.4 Install an encryption algorithm that meets or exceeds industry recommended encryption standard for any MCD that will be used to store County information. See Section on Encryption. 2.2.3.5 Ensure that MCDs are configured to restrict the user from circumventing the authentication process. 2.2.3.6 Provide security awareness training to County employees that informs MCD users regarding MCD restrictions. 2.2.3.7 Label MCDs with County address and/or phone number so that the device can be returned to the County if recovered. 2.2.3.8 The installation of any software, executable, or other file to any County computing device is prohibited if that software, executable, or other file downloaded by, is owned by, or was purchased by an employee or contractor with his or her own funds unless approved by the department. If the device (“i” device or smartphone, only) complies with the mobile device management security standards (see section 9.2.3 Mobile Computing Devices), this is not applicable.
View SourceView Similar (11)
Mobile Computing Devices. Data importer shall maintain a program designed to protect data importer’s mobile computing devices from unauthorized access. Such program shall address physical protection, access control and security controls such as encryption, virus protection and device backup.
View Source
Mobile Computing Devices. To ensure that Mobile Computing Devices (“MCDs”) do not introduce threats into systems that process or store County information, departments’ and/or contractors’ management shall: 2.2.3.1 Establish and manage a process for authorizing, issuing and tracking the use of MCDs. 2.2.3.2 Permit only authorized MCDs to connect to County information assets or networks that store, process, transmit, or connects to County information and information assets. 2.2.3.3 Implement applicable access control requirements in accordance with this guideline, such as the enforcement of a system or device lockout after 15 minutes of inactivity requiring re-entering of a password to unlock. 2.2.3.4 Install an encryption algorithm that meets or exceeds industry recommended encryption standard for any MCD that will be used to store County information. 2.2.3.5 Ensure that MCDs are configured to restrict the user from circumventing the authentication process. 2.2.3.6 Provide security awareness training to County and/or contractor employees that informs MCD users regarding MCD restrictions. 2.2.3.7 Label MCDs with County address and/or phone number so that the device can be returned to the County if recovered. 2.2.3.8 The installation of any software, executable, or other file to any County computing device is prohibited if that software, executable, or other file downloaded by, is owned by, or was purchased by an employee or contractor with his or her own funds unless approved by the department.
View Source
Mobile Computing Devices. Iron Mountain will have a policy or procedure in place designed to protect Iron Mountain’s mobile computing devices from unauthorized access. Such policies or procedures shall address physical protection, access control and security controls such as encryption, virus protection and device backup.
View Source

Related to Mobile Computing Devices

  • Transmission and Routing of Exchange Access Traffic PURSUANT TO 251(c)(2) 13 ARTICLE VI MEET-POINT BILLING ARRANGEMENTS 14 ARTICLE VII BLV/BLVI TRAFFIC 16 7.1 Busy Line Verification 16 7.2 Busy Line Verification Interrupt 16 7.3 BLV/BLVI Traffic 16 7.4 BLV/BLVI Compensation 16

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • Television Equipment Recycling Program If this Contract is for the purchase or lease of covered television equipment, then Contractor certifies that it is compliance with Subchapter Z, Chapter 361 of the Texas Health and Safety Code related to the Television Equipment Recycling Program.

  • Traffic Measurement and Billing over Interconnection Trunks 6.1 For billing purposes, each Party shall pass Calling Party Number (CPN) information on at least ninety-five percent (95%) of calls carried over the Interconnection Trunks. 6.1.1 As used in this Section 6, “Traffic Rate” means the applicable Reciprocal Compensation Traffic rate, Measured Internet Traffic rate, intrastate Switched Exchange Access Service rate, interstate Switched Exchange Access Service rate, or intrastate/interstate Tandem Transit Traffic rate, as provided in the Pricing Attachment, an applicable Tariff, or, for Measured Internet Traffic, the FCC Internet Order. 6.1.2 If the originating Party passes CPN on ninety-five percent (95%) or more of its calls, the receiving Party shall ▇▇▇▇ the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. For any remaining (up to 5%) calls without CPN information, the receiving Party shall ▇▇▇▇ the originating Party for such traffic at the Traffic Rate applicable to each relevant minute of traffic, in direct proportion to the minutes of use of calls passed with CPN information. 6.1.3 If the originating Party passes CPN on less than ninety-five percent (95%) of its calls and the originating Party chooses to combine Reciprocal Compensation Traffic and Toll Traffic on the same trunk group, the receiving Party shall ▇▇▇▇ the higher of its interstate Switched Exchange Access Service rates or its intrastate Switched Exchange Access Services rates for all traffic that is passed without CPN, unless the Parties agree that other rates should apply to such traffic. 6.2 At such time as a receiving Party has the capability, on an automated basis, to use such CPN to classify traffic delivered over Interconnection Trunks by the other Party by Traffic Rate type (e.g., Reciprocal Compensation Traffic/Measured Internet Traffic, intrastate Switched Exchange Access Service, interstate Switched Exchange Access Service, or intrastate/interstate Tandem Transit Traffic), such receiving Party shall ▇▇▇▇ the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. If the receiving Party lacks the capability, on an automated basis, to use CPN information on an automated basis to classify traffic delivered by the other Party by Traffic Rate type, the originating Party will supply Traffic Factor 1 and Traffic Factor