• Log In
  • Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • HomePage
  • About
    • Jan Yeomans
    • Rich
  • Structure
    • Jan’s Syllabus
    • Rich’s Syllabus
  • Schedule
    • First Half of Semester
      • Week 1: IT Governance
      • Week 2: IT’s Role and the Control Environment
      • Week 3: IT Administrative Controls
      • Week 4: Enterprise Architecture
      • Week 5: IT Strategy
      • Week 6: Project Portfolio Management
      • Week 7: Policy
    • Second Half of Semeter
      • Week 8: IT Services and Quality
      • Week 9: IT Outsourcing & Cloud Computing
      • Week 10: Monitoring & Evaluating IT
      • Week 11: IT Risk
      • Week 12: IT Security
      • Week 13: Disaster Recovery & Business Continuity
  • Assignments
    • Policy Project
    • Audit Plan Project
  • Webex
    • Sessions 8/30, 9/6, 9/27, 10/11, 11/1, 11/29
  • HBR Coursepack
  • Gradebook

MIS 5202 IT Governance

Temple University

Week 7 Wrap-up: Policy

October 19, 2016 by Richard Flanagan Leave a Comment

Up until now we have been talking mainly about doing the “Right Things”.  Policies is our first topic focused on “Done Right”.  The basic idea of policies is that they simplify decision making and encourage consistant orginzational behavior.  The idea works something like this:

  1. Senior management desires the organization to follow a certain objective behavior.
  2. It is impossibile, or impractical, for senior management to make all the decisions that are necessary to acheive this objective.
  3. Instead, management approves a policy that describes its objective and how they expect the organization to make related decisions and behave in a  compliant manner.  The policy may also set up a structure or role to which it delegates additional policy making responsibility in relation to this objective.
  4. The larger the organization, and the more complex the behavoir associated with the objective, the more likely it is that there will be several related policies organized under an overview policy.
  5. At the end of the day, an employee facing a decision on how to behave in a certain situation should be able to look at the policy and decide for him or herself what to do.

Once available, a policy is apt to generate any number of standards, guidelines and procedures that are intended to help realize the objective.  These can all be thought of as controls.  Thus, a security policy may say that employees will have unque userids (with least priviledge access)  and are accountable for how their userids are used.  This generates any number of controls from how userids are provisioned, who needs to approve a new role,  what tasks are not permitted in the same role, what passwords are acceptable, how often they need to be changed, etc.  These controls are then audited to see if the organization’s controls, if followed,  will enable the objective to be meet (sufficiency) and how well each control works (effectiveness).

Filed Under: Week 07: Policy Documents & Video Tagged With:

Reader Interactions

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Primary Sidebar

Weekly Discussions

  • Uncategorized (4)
  • Week 01: IT Governance (6)
  • Week 02: IT's Role & the Control Environment (3)
  • Week 03: IT Administrative Controls (2)
  • Week 04: Enterprise Architecture (2)
  • Week 05:IT Strategy (4)
  • Week 06: Project Portfolio Management (2)
  • Week 07: Policy Documents & Video (7)
  • Week 08: IT Services & Quality (2)
  • Week 09: IT Outsourcing & Cloud Computing (2)
  • Week 10: Monitoring & Evaluating IT (3)
  • Week 11: IT Risk (3)
  • Week 12: IT Security (2)
  • Week 13: Disaster Recovery & Business Continuity (1)
  • Week 14: Maturity Models (8)

Copyright © 2025 · Magazine Pro Theme on Genesis Framework · WordPress · Log in