Unit VI study guide  due by 24 hrs!!!

https://online.columbiasouthern.edu/bbcswebdav/institution/CSEG_Content/Courses/CSES/BBA/BBA3551/16P/Student/CSU/2B21/UnitVI.pdf

 

Instructions

Recently, a terminated employee used his mobile device to log in to the company network and steal sensitive data. As the manager of the information technology (IT) security department, you were asked by your boss to present a summary of what the organization should do to prevent this from happening again. Create a PowerPoint presentation of your summary. In your PowerPoint presentation, you should include the components listed below.

• Explain the goal of information security in relation to mobile devices.
• Identify the three sources of threats, provide a summary of each, and provide at least one example of each.
• Explain technical safeguards, and discuss which technical safeguard(s) should be used for mobile devices.
• Explain data safeguards, and discuss which data safeguard(s) should be used in this type of scenario.
• Explain human safeguards, and discuss which human safeguard(s) should be implemented.
• Discuss why the organization needs an incident response plan to secure information and knowledge.

Your presentation must be a minimum of six slides in length, not counting the title and reference slides. Be sure that any graphics used are appropriate and support the content of your presentation. You must use at least two references in your presentation, and they should be cited and referenced in APA format. Please cite all sources used.

 Unit VI reading

5 hurdles to mobile and wireless deployments … and how to overcome them: today’s work force is demanding mobile, flexible, and real-time access to critical data. But, you’re bound to encounter a few potholes along the road to anytime-anywhere computing

Author: Bob VieraitisDate: Nov. 2003From: Mobile Business Advisor(Vol. 21, Issue 5)Publisher: Advisor Publications, Inc.Document Type: ArticleLength: 3,299 wordsFull Text: 

IN THIS ARTICLE, I’ll first discuss five hurdles that hamper mobile rollouts, delay return on investment, and negatively impact user productivity, I’ll then outline a planning framework–a checklist, if you will Jill overcoming these obstacles.

Hurdle #1

Complexity of the technology base

Unlike today’s PC/LAN (and even WAN) environments, mobile and wireless technologies are composed of a patchwork of different technologies, standards, and works-in-progress. This complexity is most evident when it comes to devices, network standards, and network service plans.

Devices–Wireless devices come in many different shapes and sizes, are manufactured by multiple vendors, and run on various operating systems. It isn’t unusual to have to support Microsoft Windows Pocket PC, Windows CE, Palm OS, RIM, and RIM/J2ME in some combination. Vendors of wireless devices include HP, Palm/Handspring, Sony, Kyocera,

Samsung, and Research in Motion–just to name a few. In addition, although some of these combinations are similar, no two configurations have identical management interfaces. Further complicating the situation, each operating system and hardware vendor continues to release new versions of hardware, software, device drivers, and applications.

Networks and standards–The typical enterprise has to use multiple networks and multiple carriers to ensure its mobile work force has seamless wireless coverage. Even if you go with a single primary carrier, roaming agreements increase cost and require some knowledge of other carriers to troubleshoot and resolve problems. Wireless network technologies encompass multiple connection standards (e.g., CDMA, GPRS, 802.11b/g/a) and evolving security standards (WEP/WPA, LEAP, TLS, TTLS, 802.1x, 802.11i, etc.), all made more difficult by vendor-to-vendor hardware and software incompatibilities.

Network service plans—Mobile operators and carriers provide and market different service plans, which change over time. Different types Of users might require different types of service plans. These factors present a serious and ongoing management challenge for IT organizations.

You can select a single vendor and set of standards for devices, connectivity, and services, or face the challenge of integrating, managing, and supporting incompatible software and hardware components from a range of vendors. However, even if you select a single platform, you still aren’t off the hook; you’ll encounter incompatibilities as new versions of hardware, software, and firmware are released.

In your organization, you might already have a variety of hardware and software deployed–some initiated by IT, some initiated by individual departments, and some implemented by users without IT’s help, knowledge, or consent. Even if you use a corporate standard for new deployments, you must integrate your current installed base with new technologies. This can result in extensive manual effort and ongoing high costs.

Hurdle #2

Insufficient security and control

Mobile and wireless devices create an entirely new set of security concerns and exacerbate others. For the following reasons, mobile devices also make it more difficult to maintain control over IT assets and important corporate data. Proliferation of remote users–Wireless networking renders physical security mechanisms (e.g., locked doors and security systems) meaningless when it comes to protecting the network. And, with the low cost of WLAN hardware, individual employees can easily install unsecured access points behind the corporate firewall. It’s also common for enterprises to provide wireless connectivity to visitors. These factors significantly weaken or bypass the access control mechanisms that protect wired networks.

Applications and data outside corporate boundaries–Mobile devices carry corporate applications and large amounts of corporate data outside the corporate firewall. In addition, small handheld devices are far more likely to be lost or stolen than PCs, and are more easily removed from the premises when employees are terminated. These devices could also let an unauthorized user gain access to corporate data behind the firewall on the corporate LAN.

Weak security of wireless networks–Weaknesses in wireless security have been widely reported. The use of virtual private network (VPN) technologies to access the corporate network can help address this, but they add overhead and may not be suitable for all applications.

Short lifecycle and more devices–Handheld device technology is evolving quickly. And, because handheld devices and laptops are used on the road, they wear out taster than stationary desktop PCs. The short life of handheld devices leads to greater quantities of such devices throughout the enterprise, making their tracking, security, and management a challenge.

Evolving security standards–The wireless world is in the midst of an evolution in security standards, some of which won’t be finalized for years. In the meantime, your best bet is to implement best available security policies, and be prepared to adapt to new standards and technologies as they become available. This increases cost and complexity and highlights the need for internal expertise to manage wireless security. Personal and shared devices–Many organizations let employees use their personal devices to store and access corporate data. Regardless of who owns the devices, if they carry corporate data, your organization must manage and secure them as if they were company-issued. In some applications, devices may be shared or rotated among workers. In such situations, managing configurations and security for these devices can be a challenge.

Hurdle #3

Remote management and support

As mobile and wireless devices begin to play more of a role in critical business processes, it becomes more important to support them as you would other enterprise systems. The fact that users are distributed and disconnected complicates matters.

Wireless device users don t always connect from the same location, and these connections are intermittent and unpredictable. Roaming, moving from cell to cell or between access points causes regular disruptions in the data signal. And, many networks and applications don’t support host-centric “push” communication, even when the users are connected. In such cases, IT might not have physical control over, or access to, the mobile devices.

This results in a radically different support profile. IT has to manage, control, and support remote devices, ensuring remote users get required software updates in a timely fashion. IT also has to be able to detect hardware and software problems, diagnose errors, and resolve them without requiring the user to return the device.

Hurdle #4

Handheld device limitations

A mobile and wireless initiative may employ laptops PDAs, tablet PCs, or a number of other types devices, all of which have their own strengths and weaknesses. Handheld devices in particular, although opening up a host of new possibilities, create new management chalices for IT, such as:

Constrained operating systems–The operating systems of many handheld devices don’t offer robust support for applications, network APIs, or a substantial amount of memory.

Battery life and volatile storage–The battery life of mobile devices remains limited. The current generation of handheld devices usually don’t include built-in hard disks. If the battery dies, all the applications and data are lost. IT must minimize the loss of applications and data and find a way to let users easily restore them if they’re lost.

Hurdle #5

Limitations of wireless computing

Mobile users may access corporate resources via a number of options, including dial-up, synchronization via a cradle, or remote wired connections through a VPN. However, the :trend today is toward wireless access. In addition to some of the Standards and security issues I mentioned earlier, the current State of wireless connectivity creates a host of new challenges for IT, such as:

Constrained networks and intermittent connections–Wireless less networks, including Wi-Fi, have a number of unique technical constraints you don’t have to deal with on wired networks. Roaming between networks, carriers; towers, and other signal hand-offs don’t have an equivalent in the wired world. Activation on wireless a WAN requires a business relationship and technical information for deployment. TCP/IP is supported differently on each wireless platform, and has internal incompatibilities with standard wired IP protocol stacks. The IP connection, after it’s made, must tunnel through a fragile radio link before connecting with the Internet or wired LAN.

You can overcome these constraints, but deployment and support requires detailed knowledge of wireless communication. Most IT organizations have deep knowledge of PC operating systems and LAN/WAN technology, but not the knowledge to support wireless deployments.

Non-standard device drivers and firmware–Wireless devices, wireless modems and their associated drivers vary among networks, and manufacturers. Furthermore, connections to wireless networks require additional configuration settings that must be synchronized at both the network layer and on the device to work.

The solution? A shift in management

Taken together, these five hurdles demonstrate the need for a new approach to managing the lifecycle of mobile and wireless deployments. To this end, AirPrism has developed an enterprise mobility management framework. The framework is organized around the four IT objectives I mention in the sidebar on page 21.

For specific details on dealing with these challenges, MOBILE BUSINESS ADVISOR subscribers can read an extended version of this article online at http://Advisor.com/doc/12812.

Deployment

Whether launching a wireless initiative from scratch or trying to gain control over thousands of existing employee owned devices, deployment is a challenge. Deployment is more than simply distributing devices. It involves a number of complex activities that represent the crucial first step to a successful initiative

The questions you must answer in deployment include:

* How many devices are in use, what types are they, and who’s using them?

* What types of wireless cards, service plans, and accounts are associated with each device?

* How will you install software on, and deliver patches to, each device (taking into consideration different device types, operating systems, and versions)?

* How will you configure settings on each device?

* How will you configure and activate each device for wireless access?

The entire process of deployment, including loading software, configuring the devices and activating them on the network is time-consuming, error-prone, and costly. A solution for mobile and wireless deployment should include the following functionality:

Asset discovery–Asset discovery capabilities let IT automate the process of capturing detailed information about each device. Traditional desktop management systems discover computers by scanning the local network. Discovery of mobile devices is more difficult than desktop computers because the devices may reside outside the corporate LAN and routinely move on and off the network. In addition, there’s no industry-standard mechanism for discovering hardware details on handheld devices.

Imaging–Imaging abilities let IT create a standard copy of the applications, configurations, and data required by a device or a group of devices. After you create an image, you can quickly and automatically assign it to any device under management.

Personalization–It’s important for IT to be able to quickly customize devices for each user. For example, e-mail settings are unique for each user. As a user replaces his device, it should be easy to migrate his profile to the new device. Service activation–Automating the process of configuring devices with required service parameters and activating the service with the mobile operator or carrier is an important timesaver. For wireless WAN activation, the solution should automatically connect with carriers to obtain the settings needed for device activation and ensure they’re properly set and synchronized. The solution should provide support for networks such as Wi-Fi, GPRS, and CDMA, and be able to support new networks as required.

Security and control

Security is at (or near) the top of virtually every company’s list of IT priorities, and I can’t overemphasize its role in a wireless and mobile deployment. Some of the specific questions you should consider when planning a mobile security strategy are:

* How will you configure settings and enforce policies on thousands of devices?

* How will you prevent unauthorized access to the device?

* How will you keep users from tampering with device configurations?

* How will you detect unauthorized devices and prevent them from accessing the corporate network?

* How will you disable and erase devices if necessary?

* How will you protect critical data.

* How will you detect network intruders and viruses and keep them from tampering with or damaging device content?

Given these challenges, and the constraints I outlined earlier, an effective security solution for wireless and mobile deployments must provide:

Access control–Includes a power-on password login screen to prevent unauthorized users from accessing the device. To let users login when offline, authentication must take place locally.

Device protection The ability to lock down devices against user tampering or intrusion. IT should have policies defining what the user is permitted to do on the device.

Security policies should include rights that control what the user is and isn’t allowed to do; for example:

* Install and uninstall applications

* Access certain applications

* Change device system settings

* Change device network settings

Data protection–Includes safeguarding critical data via encryption and mechanisms that let you purge sensitive data on select remote devices.

Remote security–You should be able to lock devices and encrypt or purge data on an individual device or group of devices via commands sent from a central console. You send these commands when a device is reported lost or stolen, when an employee is terminated, or when a device has been inactive for a predetermined period.

Management

Lack of a solid management plan and tools to manage mobile and wireless devices result in higher total cost of ownership and decreases the likelihood of meeting return-on-investment goals. After you deploy and secure the devices, their ongoing maintenance will raise issues such as:

* How will you track diverse hardware and software assets?

* How will you deliver critical software updates to remote users?

* How will you monitor device status and location?

* How will you track application, data, and network usage?

A management solution for wireless and mobile devices must incorporate the following features:

Asset inventory–You must be able to track all mobile assets, including detailed information about the devices’ relationships with users, service accounts, and other components.

Configuration–I’ve briefly touched on this in the sections about imaging, personalization, and service activation. Configuration capabilities automatically configure each device based on user, hardware, software, and network requirements. You should be able to define configurations for each individual device, for all devices under management, or for any size group. After they’re defined, the configurations are automatically delivered to the device. After the devices are loaded, you should have a process set up for automatically testing the device to ensure it has been correctly deployed.

Software distribution–You must be able to centrally manage the distribution and installation of new applications, soft ware updates, and data files to mobile devices via cradle, wireless LAN, and wireless WAN connections.

Content distribution–Content distribution capabilities let you publish and deliver documents to mobile users over various connections. It’s important to consider issues such as document formatting and bandwidth usage.

Software license tracking–IT must be able to track the number of applications being used by mobile users and how they’re being used.

Monitoring–Some companies want to be able to view the latest status and location of mobile devices and users. It’s also helpful to be able to view errors or alarms, such as those indicating low battery conditions.

Support

As devices carry more of users’ day-to-day computing burden, downtime becomes more than an inconvenience. Users can find themselves out of touch, or worse, unable to work altogether. Before you deploy mobile and wireless devices, you must answer the following questions:

* How will you remotely support thousands of distributed and mobile users?

* How will you detect, diagnose, and fix problems?

* How will you restore data and applications if a device is lost or stolen?

To provide support capabilities for a distributed user base, a management solution should provide visibility into the current state of every device in the field, tracking detailed information about each device–from high-level status to individual settings and parameters. An effective solution must let you and your staff proactively monitor and support users, and includes these features:

Diagnosis and healing–Automated self-diagnosis and self-healing are important. The solution should let you test all configurations and identify errors on the network, device, wireless modem, and software. With this information, it can identify specific problems, categorize them, and send error messages to the central server. Automated error detection and self-healing improve application. uptime while reducing Help calls and support costs.

Backup and recovery–Automatic backup of critical mobile device data to a central server lets you restore the latest backup to a new device in the event a device is lost or stolen.

User self-help–In some situations, it’s appropriate for users to perform management tasks without the assistance of support staff. In situations where the IT staff isn’t available or the user prefers self-help, the user can proactively identify and repair problems.

Troubleshooting–Automated diagnosis and healing may not be effective in all cases. Troubleshooting tools can help you remotely recognize and solve technical problems.

Rethinking existing tools and processes

Mobile and wireless technologies hold great promise for the enterprise, yet, as with all major innovations, they require you to rethink existing tools and processes. As companies continue to invest in these new technologies, they will encounter situations that require new solutions. Fortunately, there are now tools and methodologies available to help you with these initiatives, and ensure their successful completion.

This article is based on the whitepaper, “Five Hurdles to Successful Mobile and Wireless Deployment: A Guide to Enterprise Mobility I Management” from AirPrism. http://www.airprism.com.

HOW DO YOU DEFINE SUCCESS?

The true success of any technology project is based on the day-to-day experiences of two of IT’s main constituencies: users and business managers. The final costs and benefits of the deployment are determined by how well the project meets the needs of these two groups.

A user judges the success of a mobile/wireless project with these factors in mind:

* Can I do my job better, faster, easier?

* Is the system simple to use?

* Do I have to change the way I work?

* How many problems will I encounter with this technology?

* How painful is it to resolve these issues?

* How much time will I spend keeping the system running properly.

Business managers look at these factors:

* Are the business benefits being achieved?

* What are the security risks and possible legal/competitive exposures?

* How likely are unexpected costs?

* Do the benefits outweigh the costs?

To meet these objectives, it’s helpful to translate them into specific metrics IT can use to track and evaluate its own performance. For mobile and wireless deployments, there are four basic objectives on which IT should focus:

1. Rapid and efficient deployment

* Reduce the time to commission devices

* Create consistency across devices

* Minimize user involvement

* Easily migrate/replace devices with user-specific data and settings

2. Effective device and data security

* Protect corporate data and network resources

* Respond quickly and effectively to potential security breaches, such as virus attacks and lost or stolen devices

3. Efficient management

* Maintain the reliability and proper functioning of devices

* Eliminate the need to physically touch systems to perform maintenance

* Ensure that users have up-to-date software and data

* Track the location and status of corporate assets

* Ensure compliance with corporate policies

4. Reliable support

* Minimize user downtime

* Reduce the number of incidents logged with the Help desk

* Reduce the time required to resolve and close incidents

* Remotely troubleshoot and fix devices

* Meet service level agreements

No matter how carefully you have selected the applications, evaluated the appropriate devices, and calculated the ROI, if you don’t meet these objectives, the success of your mobile and wireless initiative is at risk.

Bob Vieraitis is vice president of marketing at AirPrism, Inc. AirPrism’s software enables enterprise IT organizations to more efficiently deploy, secure, manage, and support mobile devices. Bob has more than 18 years of high-tech experience, including positions as vice president of product marketing at Portal Software, vice president of marketing at Golfweb and director of software product marketing at Sun Microsystems. He holds a bachelor of science degree in computer science from M.I.T, and an master’s in business administration from Babson College. http://www.airprism.com.

Vieraitis, Bob

Copyright: COPYRIGHT 2003 Advisor Publications, Inc.http://www.ad-visorads.com/home.htmlSource Citation (MLA 8th Edition)  Vieraitis, Bob. “5 hurdles to mobile and wireless deployments … and how to overcome them: today’s work force is demanding mobile, flexible, and real-time access to critical data. But, you’re bound to encounter a few potholes along the road to anytime-anywhere computing.” Mobile Business Advisor, vol. 21, no. 5, Nov. 2003, p. 20+. Gale OneFile: Computer Science, https://link.gale.com/apps/doc/A110026621/CDB?u=oran95108&sid=CDB&xid=2093ba2d. Accessed 4 Nov. 2020.

Gale Document Number: GALE|A110026621