• Home
  • pds2k.com Website
  • About
Follow

Stolen!

Jul26
2012
Written by Christopher Tarricone

Recently we got a call from a client, they had an employee who’s laptop was stolen. According to a recent study there is a laptop stolen every 50 seconds. That is a pretty alarming statistic, but what does that really mean to you or your business? Just think about all of the things that are on your computer.

  • In most cases a copy of all your emails.
  • Do you use the save password feature in your web browser?
  • When was the last time you cleared your browser cache and history?
  • What documents are on your computer and what type of data do they contain?

The list can go on. Before you say “But I have a password on my computer!” there is one more important piece of information you should consider! In a few minutes more than it takes to download a small compressed CD image and burn it, hackers can unlock the Administrator password on almost any Windows laptop. Once they have administrative access to the computer, they can get at anything. There are even a host of applications that will pull the saved usernames and passwords out of web browsers. Applications that can, in mere seconds, provide them with the password to Office documents.

To expand upon the problem, people are using their tablets and smart phones to access corporate data. The question then becomes how does one incorporate all of these devices their your network infrastructure while maintaining the integrity and security of the network infrastructure. To do this you must do the following three things:

  1. Define your IT requirements
  2. Define your legal requirements
  3. Implement some type of mobile management software

1. Define your IT requirements

To begin, you must select the types of devices and operating systems that you are willing (and able) to support. It is not possible to standardize management for mobile devices since each operating system and even the hardware itself can impact IT capabilities. For your Mobile Device Policy, here are baseline criteria to use for assessing operating systems and device types:

Security
  • Built-in encryption
  • Identification of jailbroken or rooted devices
  • Enforceable passwords
  • Geolocation capabilities
  • Remote lock / wipe
Manageability
  • An API that enables Mobile Device and/or Mobile Application Management
  • Extended MDM API via hardware vendor
  • Support of Exchange ActiveSync policies that comply to company standards
Applications
  • A broad range of commercially available productivity apps
  • Support for developing and deploying your own custom apps
  • Availability of key apps specific to the form factor

Based on these criteria, you should be able to define the list of form factors and operating systems you will support.

Network Accessibility

Next, you must create an environment that will support employee-owned devices during the enrollment process. The simplest solution is to set up a guest wireless network that is separated from the internal network. This can serve as the enrollment network for employee-owned devices. Once enrolled, your MDM solution should automatically evaluate and assign privileges and restrictions based upon the policies you’ve created.

Basic privileges include access to company email, company Wi-Fi, and VPN configurations. These privileges should be tied to a policy that defines the security requirements of the company. Devices that do not comply with the security policy should be blocked. For instance: devices that are jailbroken, rooted or have blacklisted apps installed.

Provisioning access through your MDM solution benefits the organization and the employee:

  • Employees receive access immediately
  • IT doesn’t need to manually provision devices
  • Wi-Fi passwords are not shared with employees
  • Remediation of future violations will be automatic since access is tied to the security policy

Management Policies
The final component for IT readiness relates to management policies and restrictions to employee-owned devices. This is broken down into three basic considerations:

    • Policy-based management: Employee information is already organized within directory systems such as Active Directory or Open Directory, including departments, geographies, and job titles. Save yourself a lot of time and base your device policies on these groupings.
    • Security: Create a baseline security policy that enables automatic remediation when devices fall out of compliance. Other criteria should be identified and implemented including company passwords and app blacklists.
    • Document Management:Unless you provide employees with a means to securely access corporate documents, they will invent their own. The best practice is to provide a centrally administered document repository that manages file availability by policy, while allowing IT to delete files as necessary. This is the best model to secure company data while respecting device ownership and user experience.

2. Define your legal requirements

Mobile Device Policy
This is a comprehensive document that should incorporate the specific requirements of your organization, based upon guidance provided by various internal stakeholders including general legal counsel, IT, Human Resources, employees and others.

Each policy is unique but generally should address some or all of these aspects:

Criteria

      • Defines accountability and responsibilities
      • Defines process for policy violation including consequences
      • Focuses on a set of standards without including details such as device type and operating system
      • Sets expectation that standards will be updated periodically

Users & Funding

      • Defines how devices will be used by employees
      • Defines how security requirements will be communicated to employees
      • Whether a technology stipend program is needed and if so, who will pay
      • If required, defines the reimbursement process for recurring costs to employees
      • Includes support for contractors using their own devices on the corporate network

Legal Considerations

      • Enforceable
      • Whether regional or country data privacy laws will restrict security measures available to IT and consents required
      • Rights to audit and monitor activity on personally owned devices and any limitations based on local laws and regulations
      • The ability to distinguish liabilities between users and the organization for usage of features, licenses, apps, etc.
      • Consent for the company to access the device for business purposes
      • Includes how to remove devices from the population and how sensitive data and company property are removed
      • Obligations for employee to report loss of device and employer’s right to wipe it

Human Resources

      • Details of control over corporate information stored on employee-owned devices
      • HR policies that can govern the use of personally owned devices for personal use during work and non-work hours or in a work or non-work environment

3. Implement some type of mobile management software

Now that you have all of the internal requirements identified and in order, you need to select the appropriate software application that will allow you to properly manage and secure corporate- and employee-owned mobile devices.

Similar to the criteria you applied while assessing the different types of operating systems and form factors, you need to ensure the solution you select is able to deliver some baseline and supplementary capabilities:

Platform Flexability
  • Easily installs within the existing environment
  • Leverages existing security and network infrastructure
  • Minimal adaption required
  • Consolidation: Able to manage all IT form factors and operating systems via a single console (ideally to include desktop and laptop computers)
Administration
  • Role-based administration so technicians can be assigned to specific user groups with defined management privileges
Application Management
  • Distribution of in-house and commercial apps
  • Apps management capabilities to support and automate user self-service
  • Support for the Apple ASVPP program (if you purchase Apple apps)
Security
  • Application of multiple policies per device, for example an umbrella security baseline for all devices but separate privileges or restrictions per department or user role
  • Automated remediation of non-compliant devices
  • Secure document distribution and management
  • Remote freeze and wipe capabilities
  • Enterprise password support

Share this:

Posted in Backup, Network Security
SHARE THIS Twitter Facebook Delicious StumbleUpon E-mail
← Backing up to “The Cloud”
Implement a DR Plan Part 2 →

Recent Posts

  • Implement a DR Plan Part 2
  • Stolen!
  • Backing up to “The Cloud”
  • Implement a Disaster Recovery Plan Part 1
  • When do you have enough Network Security

Join us on Facebook

Archives

  • August 2012 (1)
  • July 2012 (3)
  • June 2012 (3)
  • May 2012 (4)

pds2k.com Blog pds2k.com Blog
People you like, Network service you trust

loading Cancel
Post was not sent - check your email addresses!
Email check failed, please try again
Sorry, your blog cannot share posts by email.