Mobile Device Detection Sample Clauses
Mobile Device Detection. Varnish’s Mobile Device Detection module detects which mobile device people are using to visit a website and adds business logic to the Varnish caching layer based on this information.
Network Interface Device 2.7.1 The NID is defined as any means of interconnection of the customer’s premises wiring to BellSouth’s distribution plant, such as a cross-connect device used for that purpose. The NID is a single line termination device or that portion of a multiple line termination device required to terminate a single line or circuit at the premises. The NID features two (2) independent ▇▇▇▇▇▇▇▇ or divisions that separate the service provider’s network from the customer’s premises wiring. Each chamber or division contains the appropriate connection points or posts to which the service provider and the customer each make their connections. The NID provides a protective ground connection and is capable of terminating cables such as twisted pair cable. 2.7.2 BellSouth shall permit NewPhone to connect NewPhone’s Loop facilities to the customer’s premises wiring through the BellSouth NID or at any other technically feasible point.
Interoperability MCP must make available to Members their electronic health information held by MCP pursuant to 42 Code of Federal Regulations Section 438.10 and in accordance with APL 22-026 or any subsequent version of the APL. MCP must make available an application program interface that makes complete and accurate Network Provider directory information available through a public-facing digital endpoint on MCP’s website pursuant to 42 Code of Federal Regulations Sections 438.242(b) and 438.10(h).
Data Encryption 2.1. For all COUNTY data, The CONTRACTOR shall encrypt all non-public data in transit regardless of the transit mechanism. 2.2. For all COUNTY data, if the CONTRACTOR stores sensitive personally identifiable or otherwise confidential information, this data shall be encrypted at rest. Examples are social security number, date of birth, driver’s license number, financial data, federal/state tax information, and hashed passwords. 2.3. For all COUNTY data, the CONTRACTOR’S encryption shall be consistent with validated cryptography standards as specified in National Institute of Standards and Technology Security Requirements as outlined at ▇▇▇▇://▇▇▇▇▇▇▇.▇▇▇▇.▇▇▇/nistpubs/Legacy/SP/nistspecialpublication800-111.pdf