DeviceLock, Inc announces the first Release Candidate version of DeviceLock® for Mac OS X!
  1. Devicelock Base Devicelock For Macbook Pro
  2. Devicelock Base Devicelock For Mac Os
  3. Devicelock Base Devicelock For Macbook Air
  4. Devicelock Base Devicelock For Macbook

Devicelock Base Devicelock For Macbook Pro

  • Learn how to use the Policy CSP - DeviceLock setting to specify whether the user must input a PIN or password when the device resumes from an idle state.
  • DeviceLock, Inc., a worldwide leader in endpoint data leak prevention software solutions, announced the Release Candidate version of DeviceLock DLP Suite 8.1.Now DeviceLock DLP Suite 8.1 controls WhatsApp Web, iCloud, IBM Notes (formerly Lotus Notes) and the Torrent protocol.
09 Aug 2013

DeviceLock, Inc., a worldwide leader in endpoint data leak prevention software solutions, announced the first Release Candidate version of DeviceLock for Mac OS X with essential device control for Apple Mac OS computers.

This version contains the following changes in compare with previous beta:

Devicelock base devicelock for macbook

Devicelock Base Devicelock For Mac Os

Deploying DeviceLock Service for Mac First of all, mount DeviceLock Service.dmg. There are multiple ways to install the agent (DeviceLock Service) to client Mac OS systems: The first and easiest way is to launch DeviceLock Service.pkg and follow the instructions that appear on the screen.

Devicelock Base Devicelock For Macbook Air

  • Added ability to import signed service settings using System Preferences Pane.
  • Now you can control DeviceLock Agent for Mac via Group Policy in an Active Directory domain.
  • Added support for DeviceLock Administrators.
  • Improved DeviceLock Enterprise Server integration. DLES now performs monitoring and can use DeviceLock Certificate to authorize on DeviceLock Agent for Mac if necessary.
  • Online/Offline mode detection function now supports 'Domain' and 'Server' connectivity modes.
  • Significant improvements in the audit and shadowing.
  • Added support for the 'Fast Server First' parameter.
  • Added support for multiple servers in the 'DeviceLock Enterprise Server(s)' parameter.
  • Added integration with the Mac OS FileVault encryption.
  • Improved deployment capabilities.
  • Many internal improvements and optimizations.

Devicelock Base Devicelock For Macbook

This Release Candidate version contains the following known limitations:

  • Supported Mac OS versions include: Mac OS X 10.6.8 (Snow Leopard), 10.7 (Lion) and 10.8 (Mountain Lion), 32-bit and 64-bit.
  • The release candidate's installer is not signed so you need to allow installation of unsigned applications for Lion and Mountain Lion, the complete guide is available at http://support.apple.com/kb/HT5290.
  • To allow remote management via DeviceLock Management Console using local user credentials for machine where the agent was installed, the Share File and Folders using SMB (Windows) system option must be enabled for these local users on the computer where DeviceLock Service for Mac is installed or the NTLM hashes must be enabled for these accounts. Please refer to Enabling NTLM.pdf available on the installation dmg image for more information about enabling NTLM authentication for local users. This does not apply for domain users as the NTLM authentication is performed using domain controller.
  • In order to connect to MacOS X Snow Leopard using local user account, specify credentials in this format: COMPUTERaccount, where COMPUTER is the name of computer running DeviceLock Agent for Mac with all letters in uppercase.
  • DeviceLock Management Console might be unable to connect and manage DeviceLock Agent for Mac running on Mac OS Snow Leopard joined to the Windows 2008 Server domain using domain user credentials.
  • To uninstall DeviceLock Agent for Mac, run 'sudo /Library/DeviceLock Agent/Utilities/uninstall'. If the DeviceLock administrators was enabled and the local root user is not in the DeviceLock administrators group then the agent must be stopped before executing uninstall command. The agent must be stopped by a user from DeviceLock administrators group by executing 'DLAgentControl stop', the DLAgentControl can be found in the Utility directory of the dmg image. Please pay attention that there must not be 'sudo' command before DLAgentControl.
  • 'Service Options' parameters except 'DeviceLock Administrators', 'DeviceLock Enterprise Server(s)', 'DeviceLock Certificate', 'Use Group Policy', 'Fast servers first', 'Offline mode detection' are not yet supported in the Mac OS version.
  • Controls for the following device types and ports are not supported in the Mac OS version: BlackBerry, Clipboard, Floppy, Infrared port, iPhone, Palm, Parallel port, Printer, Tape, TS Devices and Windows Mobile devices. However many devices are controlled on a USB level. This includes iPhone , Palm, Printer, Windows Mobile and certain other devices.
  • The following device class parameters in 'Security Settings' are not supported in the Mac OS version: 'Access control for USB Printers', 'Access control for USB scanners and still image devices', 'Access control for serial modem (internal & external)', 'Access control for virtual Optical Drives (Windows 2000 and later)', 'Access control for FireWire storage devices', 'Access control for virtual printers (Windows 2000 and later)', 'Access control for intra-application copy/paste clipboard operations', 'Switch PostScript printer to non-PostScript mode', 'Treat TS forwarded USB devices as regular ones' and 'Block FireWire controller if access is denied'.
  • The Temporary White List feature is not yet supported in the Mac OS version.
  • DeviceLock's encryption detection/enforcement of use features are only supported for Mac OS FileVault in the Mac OS version starting from Mac OS X Lion.
  • DeviceLock Anti-Keylogger controls are not yet supported in the Mac OS version.
  • DeviceLock alerts are not yet supported in the Mac OS version.
  • Content-Aware Rules (real file-type detection and all ContentLock pattern templates, keyword filters, document properties, etc.) are not supported in the Mac OS version.
  • Network protocols control and monitoring functions (NetworkLock) are not supported in the Mac OS version.
  • By default, USB Port permissions are NOT applied to USB Bluetooth devices to avoid conflicts with wireless keyboards and mice. This default behaviour can be changed by configuring the 'Access control USB Bluetooth devices' parameter in 'Security Settings'.
  • By default, USB Port permissions are not applied to Human Interface Devices (HID) manufactured by Apple, Inc. This has been done to avoid disabling keyboards and touchpads on MacBook, MacBook Pro and MacBook Air laptops.
  • By default, Bluetooth permissions are not applied to Bluetooth HID devices, so they are always exempt/allowed. This has been done to not disable wireless HID devices (mice and keyboards) on iMac and Mac Pro hardware.


Sign up for our beta testing program, download DeviceLock® for Mac OS X RC.
The most active beta testers will receive a free license for DeviceLock® with one year of free support and version upgrades.

DeviceLock is a tool designed and developed to ease the work of network administrators, giving them capacity to control access to peripherals and units installed on the network.
This is a useful way to avoid data steals, it's demonstrated that most steal are due to a low protection against the employees.
Thanks to DeviceLock we'll be able to decide the user groups that will be able to access certain location such as USB ports, CD/DVD drives,... as well as to know who and when access them.
Finally, you'll be able to change the properties of the units, so you'll be able to choose if they will be only readable, eliminate temporary files or even protect them against accidental formats.
Restrictions

30-day trial version