End-User Computing Security Guidelines Previous Screen Ron Hale Payoff Providing Effective Security in an End-User Computing Environment Is a Challenge

Total Page:16

File Type:pdf, Size:1020Kb

End-User Computing Security Guidelines Previous Screen Ron Hale Payoff Providing Effective Security in an End-User Computing Environment Is a Challenge 86-10-10 End-User Computing Security Guidelines Previous screen Ron Hale Payoff Providing effective security in an end-user computing environment is a challenge. First, what is meant by security must be defined, and then the services that are required to meet management's expectations concerning security must be established. This article examines security within the context of an architecture based on quality. Problems Addressed This article examines security within the context of an architecture based on quality. To achieve quality, the elements of continuity, confidentiality, and integrity need to be provided. Confidentiality as it relates to quality can be defined as access control. It includes an authorization process, authentication of users, a management capability, and auditability. This last element, auditability, extends beyond a traditional definition of the term to encompass the ability of management to detect unusual or unauthorized circumstances and actions and to trace events in an historical fashion. Integrity, another element of quality, involves the usual components of validity and accuracy but also includes individual accountability. All information system security implementations need to achieve these components of quality in some fashion. In distributed and end-user computing environments, however, they may be difficult to implement. The Current Security Environment As end-user computing systems have advanced, many of the security and management issues have been addressed. A central administration capability and an effective level of access authorization and authentication generally exist for current systems that are connected to networks. In prior architectures, the network was only a transport mechanism. In many of the systems that are being designed and implemented today, however, the network is the system and provides many of the security services that had been available on the mainframe. For example, many workstations now provide power-on passwords; storage capacity has expanded sufficiently so that workers are not required to maintain diskette files; and control over access to system functions and to data is protected not only through physical means but also through logical security, encryption, and other techniques. Architectural Approaches to Information Protection Although tools are becoming available (e.g., from hardware providers, security product developers, and network vendors) that can be used to solve many of the confidentiality and integrity problems common in end-user computing, the approach to implementing security is often not as straightforward as is common in centralized processing environments. The goals of worker empowerment, increased functionality and utility, and the ability of end- users to control their environment must be guarded. In many organizations, end-users have the political strength and independence to resist security efforts that are seen as restrictive or costly. In addition, networks, remote access, distributed data servers, Internet tools, and the other components that have become part of the end-user environment have made security a difficult task. To address the complexity of end-user computing, an architectural approach is required. A security architecture is a way of designing and implementing security solutions so that control points are identified, the effectiveness of controls is ensured, and monitoring and reporting capabilities are provided. It also helps to ensure that an organization's Previous screen security strategy and technical strategy are mutually supportive. The components of an information protection architecture include management, confidentiality and integrity controls, and continuity controls. Management Structure Perhaps the best and most expedient means of bringing security to the end-user platform is to develop an effective management structure. Distributed Security Management Because end-user computing is highly distributed, and because local personnel and managers are responsible for controlling the business environment where end-user solutions are implemented, it is appropriate that security and control responsibilities are also distributed. Centralized administration and management of security in a highly decentralized environment cannot work without a great deal of effort and a large staff. When authority for managing security is distributed within the organization, management can expect a higher degree of voluntary compliance; in particular where adherence to security policies and procedures is included in personnel evaluation criteria. If distributed security responsibility is properly implemented, ensuring that the goals of the security program are consistent with the requirements and goals of the business unit is more likely to be successful. Distributing security responsibilities may mean that traditional information protection roles need to be redefined. In many centralized security organizations, security specialists are responsible for implementing and managing access control. In a distributed end-user environment, this is not practical. There are too many systems and users for the security organization to manage access control. Even with the availability of network and other security tools, it may not be appropriate for security personnel to be responsible for access administration. In many distributed environments where advanced networks have been implemented, access controls may best be managed by network administrators. In a similar manner, server security, UNIX security, and any other system security may best be managed by personnel responsible for that environment. With many technologies that are used in distributed and end-user computing environments, no special classes of administration are defined for security. Administrators have access to root or operate at the operating system level with all rights and privileges. In such cases, it is not appropriate for security personnel to take an active role in managing access security. Their role should be more consultative in nature. They could also be involved with monitoring and risk management planning, which are potentially more beneficial to the organization and more in line with security management responsibilities. Security Management Committee Because security in end-user computing environments is distributive, greater acceptance of security policies and procedures can be expected if the organization as a whole is involved with defining the security environment. To achieve this, a security management committee can be created that represents some of the largest or most influential information technology users and technology groups. This committee, which reports to the security manager, should be responsible for recommending the security policy and for developing the procedures and standards that will be in force throughout the enterprise. Representation on the committee by the internal audit department is often beneficial, and their support and insight can be important in developing an effective security management structure. However, consideration must be given to the control responsibilities of audit and the need to separate their responsibility for monitoring compliance with controls and for Previous screen developing controls as part of the security committee. In some enterprises, this is not a major issue because internal audit takes a more consultative position. If maintaining the independence of audit is important, then audit can participate as an observer. Senior Executive Support The internal audit department traditionally had an advantage over the security organization because of its reporting relationship. Internal auditors in most organizations report to senior executives, which enables them to discuss significant control concerns and to get management acceptance of actions that need to be taken to resolve issues. Security has traditionally reported to IS management and has not had the executive exposure unless there has been a security compromise or other incident. In a distributed environment, it may be beneficial to have the security department and the security management committee report to a senior executive who will be a champion and who has sufficient authority within the enterprise to promote information protection as an important and necessary part of managing the business. Such a reporting relationship will also remove security from the purely technical environment of information systems and place it in a more business- focused environment. Policy and Strategy The ability to communicate security strategy and requirements is essential in an end-user computing environment. This communication generally takes the form of enterprisewide policy statements and is supported by procedures, standards, and guidelines that can be targeted to specific business functions, technology platforms, or information sources. The Information Protection Policy Statement An information protection policy statement should define management expectations for information protection, the responsibilities of individuals and groups for protecting information, and the organizational structure that will assist management in implementing protection approaches that are consistent with the business strategy. Because the statement will be widely distributed and is meant to clearly communicate management's and users' responsibilities, it should not take the form of a legal document. The effectiveness of the information protection policy depends in large part on its effective communication.
Recommended publications
  • Software User Guide
    Software User Guide • For the safe use of your camera, be sure to read the “Safety Precautions” thoroughly before use. • Types of software installed on your computer varies depending on the method of installation from the Caplio Software CD-ROM. For details, see the “Camera User Guide”. Using These Manuals How to Use the The two manuals included are for your Caplio Software User Guide 500SE. Display examples: 1. Understanding How to Use Your The LCD Monitor Display examples may be Camera different from actual display screens. “Camera User Guide” (Printed manual) Terms: This guide explains the usage and functions In this guide, still images, movies, and sounds of the camera. You will also see how to install are all referred to as “images” or “files”. the provided software on your computer. Symbols: This guide uses the following symbols and conventions: Caution Caution This indicates important notices and restrictions for using this camera. 2. Downloading Images to Your Computer “Software User Guide” Note *This manual (this file) This indicates supplementary explanations and useful This guide explains how to download images tips about camera operations. from the camera to your computer using the provided software. Refer to This indicates page(s) relevant to a particular function. “P. xx” is used to refer you to pages in this manual. Term 3. Displaying Images on Your This indicates terms that are useful for understanding Computer the explanations. The provided software “ImageMixer” allows you to display and edit images on your computer. For details on how to use ImageMixer, click the [?] button on the ImageMixer window and see the displayed manual.
    [Show full text]
  • Student Computer User Agreement
    STUDENT COMPUTER USER AGREEMENT GUIDING PRINCIPLE OF THIS AGREEMENT: Lakeside’s technological resources are dedicated to further the school’s mission and to serve the educational pursuits of its students. Students using Lakeside’s technology services are expected to behave in accordance with the Community Expectations documented in the family handbook. Students are expected to act in ways that show consideration and respect for other people and enhance an open atmosphere of trust, both offline and online. TECHNOLOGY SERVICES The use of Lakeside’s technology services – tech support, network access, email accounts, storage services, software subscriptions and all other school-owned computer resources – is a privilege, not a right. This privilege may be revoked at any time for abusive conduct, or failure to abide by the school’s expectations and/or responsible usage listed below. GENERAL EXPECTATIONS ▪ Lakeside email accounts, software and services, and onsite network access are provided primarily for school-related work. ▪ Any user of Lakeside’s electronic communications resources is expected to respect the person and privacy of others. ▪ The configuration of school-issued computers (operating system, security settings and software applications) may not be altered. ▪ Using the Lakeside computer network to exchange or store pirated software, unlawful information, or other unauthorized copyright-protected material (i.e. music, multimedia) in any file format is strictly prohibited. ▪ Students are expected to maintain the integrity of their computing devices so as not to bring viruses, malware or spyware to school. Unprotected and infected devices are forbidden to connect to the school network and, when detected, will be disconnected from the network until resolved.
    [Show full text]
  • The Management of End User Computing a Research Perspective
    HD2 8 .M414 Oe>NeV THE MANAGEMENT OF END USER COMPUTING A RESEARCH PERSPECTIVE John F. Rockart Lauren S. Flannery February 1983 CISR WP #100 Sloan WP // 1410-83 Centerfor Information Systems Research Massachusetts Institute of Technology Sloan School of Management 77 Massachusetts Avenue Cambridge, Massachusetts, 02139 THE MANAGEMENT OF END USER COMPUTING A RESEARCH PERSPECTIVE John F. Rockart Lauren S . Flannery February 1983 CISR WP #100 Sloan WP // 1410-83 Rockart - Flannery 1983 Center for Information Systems Research Sloan School of Management Massachusetts Institute of Technology MAY 3 1 1983 RECe;v£d 1- ABSTRACT Based on interviews with 200 end users and 50 information systems managers concerned with end user computing, end users can be classified into six distinct types. Each of them needs differentiated education, support and control from the Information Systems function. End users exist primarily in staff functions. They develop and use a wide spectrum of computing applications ranging from "operational systems" of the type usually developed by information systems professionals to complex analytical programs. To support a large number of their applications a new computing environment, "the third environment" (in addition to the traditional COBOL and timesharing environments) must be developed by Information Systems (I/S) management. Close attention must also be paid by I/S management to the need to involve "functional support personnel" (end users in each functional area who spend most of their time programming and aiding other end users) in the I/S end user management process. An end user strategy is needed in each organization. In addition, users cite increasing needs for support from I/S management.
    [Show full text]
  • (Malicious Software) Installed on Your Computer Without Your Consent to Monitor Or Control Your Computer Use
    Spyware is a type of malware (malicious software) installed on your computer without your consent to monitor or control your computer use. Clues that spyware is on a computer may include a barrage of pop-ups, a browser that takes you to sites you don't want, unexpected toolbars or icons on your computer screen, keys that don't work, random error messages, and sluggish performance when opening programs or saving files. In some cases, there may be no symptoms at all. While the term spyware suggests that software that secretly monitors the user's computing, the functions of spyware extend well beyond simple monitoring. Spyware programs can: Collect information stored on the computer or attached network drives, Collect various types of personal information, such as Internet surfing habits, sites that have been visited Collect user names and passwords stored on your computer as well as those entered from the keyboard. Interfere with user control of the computer Install additional software on the computer Redirect Web browser activity. Change computer settings, resulting in slow connection speeds, different home pages, and/or loss of Internet or functionality of other programs. The best defense against spyware and other unwanted software is not to download it in the first place. Here are a few helpful tips that can protect you from downloading software you don't want: Update your operating system and Web browser software, and set your browser security high enough to detect unauthorized downloads. Use anti-virus and anti-spyware, as well as a firewall software, and update them all regularly.
    [Show full text]
  • ICU Medical Mednet™ Software User Guide
    Software User Guide For a list of ICU Medical MedNet compatible devices approved by country, refer to the ICU Medical MedNet Device Compatibility Matrix available through your ICU Medical Technical Support. 430-98350-001 (%, 2017-) Notes: ICU Medical MedNet™ Software User Guide Rx Only 16037-92-01 IMPORTANT Refer to this guide for proper use, warnings, and cautions associated with the installation and upgrade of the ICU Medical MedNet™ Software performed by the ICU Medical Service Team. Please contact your sales representative for any questions associated with installing and configuring the ICU Medical MedNet™ Software. The help files included with the ICU Medical MedNet™ software are provided as reference only. Please read this entire guide before using the ICU Medical MedNet™ Software. Please also read the ICU Medical Release Notes before using the ICU Medical MedNet™ Software. Intended Use The ICU Medical MedNet™ Medication Management Suite (MMS) is intended to facilitate networked communication between MMS compatible computer systems and MMS compatible Infusion pumps. The MMS provides trained healthcare professionals with the capability to send, receive, report, and store information from interfaced external systems, and to configure and edit infusion programming parameters. The MMS is intended to provide a way to automate the programming of infusion parameters, thereby decreasing the amount of manual steps necessary to enter infusion data. All data entry and validation of infusion parameters is performed by a trained healthcare professional
    [Show full text]
  • Unix / Linux User Administration
    UUNNIIXX // LLIINNUUXX -- UUSSEERR AADDMMIINNIISSTTRRAATTIIOONN http://www.tutorialspoint.com/unix/unix-user-administration.htm Copyright © tutorialspoint.com Advertisements In this chapter, we will discuss in detail about user administration in Unix. There are three types of accounts on a Unix system − Root account This is also called superuser and would have complete and unfettered control of the system. A superuser can run any commands without any restriction. This user should be assumed as a system administrator. System accounts System accounts are those needed for the operation of system-specific components for example mail accounts and the sshd accounts. These accounts are usually needed for some specific function on your system, and any modifications to them could adversely affect the system. User accounts User accounts provide interactive access to the system for users and groups of users. General users are typically assigned to these accounts and usually have limited access to critical system files and directories. Unix supports a concept of Group Account which logically groups a number of accounts. Every account would be a part of another group account. A Unix group plays important role in handling file permissions and process management. Managing Users and Groups There are four main user administration files − /etc/passwd − Keeps the user account and password information. This file holds the majority of information about accounts on the Unix system. /etc/shadow − Holds the encrypted password of the corresponding account. Not all the systems support this file. /etc/group − This file contains the group information for each account. /etc/gshadow − This file contains secure group account information.
    [Show full text]
  • OS Security Basics & Unix Access Control
    Information Security CS 526 Topic 8: Operating Systems Security Basics & Unix Access Control CS526 Topic 8: Operating System 1 Security Basics Readings for This Lecture • Wikipedia • CPU modes • System call • Filesystem Permissions • Other readings • UNIX File and Directory Permissions and Modes • http://www.hccfl.edu/pollock/A Unix1/FilePermissions.htm • Unix file permissions • http://www.unix.com/tips- tutorials/19060-unix-file- permissions.html CS526 Topic 8: Operating System 2 Security Basics Announcements and Outline • Outline of this topic – Brief overview of the goals of OS security – Memory protection, CPU modes, and system calls – Access control basic concepts – UNIX File System permissions – UNIX processes CS526 Topic 8: Operating System 3 Security Basics What Security Goals Does Operating System Provide? • Originally: time-sharing computers: enabling multiple users to securely share a computer – Separation and sharing of processes, memory, files, devices, etc. • What is the threat model? – Users may be malicious, users have terminal access to computers, software may be malicious/buggy, and so on • Security mechanisms – Memory protection – Processor modes – User authentication – File access control CS526 Topic 8: Operating System 4 Security Basics What Security Goals Does Operating System Provide? • More recent past and present: Networked desktop computers: ensure secure operation in networked environment • New threat? – Attackers coming from the network. Network-facing programs on computers may be buggy. Users may be hurt via online communication. • Security mechanisms – Authentication; Access Control – Secure Communication (using cryptography) – Logging & Auditing – Intrusion Prevention and Detection – Recovery CS526 Topic 8: Operating System 5 Security Basics What Security Goals Does Operating System Provide? • Present and near future: mobile computing devices: • New threat? – Apps (programs) may be malicious.
    [Show full text]
  • Unix Login Profile
    Unix login Profile A general discussion of shell processes, shell scripts, shell functions and aliases is a natural lead in for examining the characteristics of the login profile. The term “shell” is used to describe the command interpreter that a user runs to interact with the Unix operating system. When you login, a shell process is initiated for you, called your login shell. There are a number of "standard" command interpreters available on most Unix systems. On the UNF system, the default command interpreter is the Korn shell which is determined by the user’s entry in the /etc/passwd file. From within the login environment, the user can run Unix commands, which are just predefined processes, most of which are within the system directory named /usr/bin. A shell script is just a file of commands, normally executed at startup for a shell process that was spawned to run the script. The contents of this file can just be ordinary commands as would be entered at the command prompt, but all standard command interpreters also support a scripting language to provide control flow and other capabilities analogous to those of high level languages. A shell function is like a shell script in its use of commands and the scripting language, but it is maintained in the active shell, rather than in a file. The typically used definition syntax is: <function-name> () { <commands> } It is important to remember that a shell function only applies within the shell in which it is defined (not its children). Functions are usually defined within a shell script, but may also be entered directly at the command prompt.
    [Show full text]
  • Informational Supplement Best Practices on Spyware Prevention and Detection the Internet Has Become a Popular Method for Both C
    Informational Supplement Best Practices on Spyware Prevention and Detection The Internet has become a popular method for both conducting business and managing finances through online banking relationships. While most financial institutions and some individuals have taken steps to protect their computers, many firewall and anti-virus software packages do not protect computers from one of the latest threats, “spyware” – a form of software that collects personal and confidential information about a person or organization without their proper knowledge or informed consent, and reports it to a third party. This informational supplement describes the various challenges and best practices related to spyware. Financial institutions should consider these recommendations to prevent and detect spyware on both bank-owned and customer computers. Spyware Infection Spyware is usually installed without a user’s knowledge or permission. However, users may intentionally install spyware without understanding the full ramifications of their actions. A user may be required to accept an End User Licensing Agreement (EULA), which often does not clearly inform the user about the extent or manner in which information is collected. In such cases, the software is installed without the user’s “informed consent.” Spyware can be installed through the following methods: • Downloaded with other Internet downloads in a practice called “bundling.” In many cases, all the licensing agreements may be included in one pop-up window that, unless read carefully, may leave the user unaware of “bundled” spyware. • Directly downloaded by users who were persuaded that the technology offers a benefit. Some spyware claims to offer increased productivity, virus scanning capabilities or other benefits.
    [Show full text]
  • Chapter 6 Operating Systems
    CSCA0201 FUNDAMENTALS OF COMPUTING Chapter 6 Operating Systems 1 Operating Systems 1. Operating Systems 2. Types of Operating System 3. Major Functions 4. User Interface 5. Examples of Operating System 2 Operating Systems Operating Systems • The operating system is the most important program that runs on a computer. • Operating system is an interface between computer and user. • It is responsible for the management and coordination of activities and the sharing of the resources of the computer. 3 Operating Systems Operating Systems 4 Operating Systems Operating Systems 5 Operating Systems Types of Operating System • Real-time • Multi-user vs. Single-user • Multi-tasking vs. Single-tasking • Distributed • Embedded 6 Operating Systems Types of Operating System Real-Time • A real-time operating system is a multitasking operating system that aims at executing real-time applications. • Responds to input instantly. 7 Operating Systems Types of Operating System Multi-user vs. Single user . A multi-user operating system allows multiple users to access a computer system concurrently. Time-sharing system can be classified as multi-user systems as they enable a multiple user access to a computer through the sharing of time. Single-user operating systems, as opposed to a multi-user operating system, are usable by a single user at a time. 8 Operating Systems Types of Operating System Multi-tasking vs. Single-tasking . When a single program is allowed to run at a time, the system is grouped under a single-tasking system . While in case the operating system allows the execution of multiple tasks at one time, it is classified as a multi-tasking operating system.
    [Show full text]
  • FMS Software Version 5 User Manual
    FMS SOFTWARE VERSION 5 USER MANUAL P/N 6002773, REVISION Q OCTOBER 2020 Manual History The following is a manual history of the FMS Software User Manual (P/N 6002773). Revision Date A July 2009 B December 2009 C May 2010 D August 2010 E November 2010 F February 2011 G June 2012 H October 2012 J April 2014 K January 2015 L July 2015 M August 2016 N September 2017 P January 2019 Q October 2020 ii Warranty / Software License Part Number 6002773 / Revision Q / October 2020 Copyright ©TSI Incorporated / 2009-2020 / All rights reserved. Address TSI Incorporated / 500 Cardigan Road / Shoreview, MN 55126 / USA E-mail Address [email protected] Limitation of Warranty (For country-specific terms and conditions outside of the USA, please visit www.tsi.com.) and Liability Seller warrants the goods, excluding software, sold hereunder, under normal use and service as (effective April 2014) described in the operator's manual, to be free from defects in workmanship and material for 12 months, or if less, the length of time specified in the operator's manual, from the date of shipment to the customer. This warranty period is inclusive of any statutory warranty. This limited warranty is subject to the following exclusions and exceptions: a. Hot-wire or hot-film sensors used with research anemometers, and certain other components when indicated in specifications, are warranted for 90 days from the date of shipment; b. Pumps are warranted for hours of operation as set forth in product or operator’s manuals; c. Parts repaired or replaced as a result of repair services are warranted to be free from defects in workmanship and material, under normal use, for 90 days from the date of shipment; d.
    [Show full text]
  • Methods and Qualities of a Good User Interface Design
    2008:PR002 User Interface Design – Methods and Qualities of a Good User Interface Design Ravi Chandra Chaitanya Guntupalli MASTER’S THESIS Software Engineering, 2008 Department of Technology, Mathematics and Computer Science MASTER’S THESIS User Interface Design – Methods and Qualities of a Good User Interface Design Summary User interface (UI) plays a vital role in software. In terms of visibility, its design and precision holds the primary importance for depicting the exact amount of information for the intended user. Every minor decision taken for the designing of UI can contribute to the software both positively and negatively. Therefore, our study is intended to highlight the strategies that are currently being used for successfully designing UIs, and make appropriate suggestions for betterment of UI designs based on case studies and research findings. Author: Ravi Chandra Chaitanya. Guntupalli Examiner: Dr. Samantha Jenkins Advisor: Dr. Samantha Jenkins Programme: Software Engineering, 2008 Subject: Software Engineering Level: Master Date: June, 2008 Report Number: 2008:PR002 Keywords User interface design, Software Quality, Reliability, Efficiency, Conciseness, Portability, Consistency, Maintainability, Understandability, System status visibility, System consistency, Error handling, Feedback systems, Memory loading, Efficiency, Appropriate outlook, UI design principles, Usability design, Interface design, Information design, Stake holder, End user. Publisher: University West, Department of Technology, Mathematics and Computer Science,
    [Show full text]