Please report any problems to the Shared Tools Team at st-help@doit.wisc.edu    Broken Links? Missing Macros? WIKI Retiring Plugins
Child pages
  • Discussion Results from the 2009-04-06 Forum
Skip to end of metadata
Go to start of metadata

Prioritized List of possible IT policy initiatives for FY 2009-2010

Need

Initiative

Votes

A,B,C

Information Resource Management (IRM)
This high-level policy could address such things as definitions, roles and responsibilities, privacy, high-level information security policy and information resource governance.

22%

B

Personally Owned Devices (PODs)
Addresses the storage and processing of sensitive information on POD's.

12%

A,B,C

Role-based Access Control (RBAC)
There are a number of issues arising in conjunction with the Identity and Access Management (IAM) project concerning role-based authentication and authorization.

12%

A,C

IP Version 6 (IP6)
There are many possible IT policy issues surrounding the use of IP version 6.

8%

A,B

Business Continuity Planning (BCP)
BCP would address backups, disaster recovery planning and other preparations to assure that operations can continue with as little disruption as practical.

7%

B

Third Party Applications (TPA)
There can be significant intellectual property and privacy issues when using third-party tools offered by web service providers.

7%

C

Green Practices in IT (GreenIT)
Environmentally friendly practices in information technology can save money and reduce environmental impact.

6%

B

Protection of Information during Transmission (ITransmit)
This initiative complements the previous initiative that addressed encryption of stored information.

6%

A,C

Web Interface Standards (WIS)
A policy establishing web interface standards would help assure that applications remain compatible with the web technologies in widespread use at UW-Madison.

6%

A,C

IT Application and Infrastructure Planning (ITAP)
Improving coordination between applications and infrastructure would better enable the use of new applications and reduce duplication of instructure.

5%

B

Electronic Devices policy, update (EDevices)
A firewall requirement could be added to the "Policy on Electronic Devices Connected to the UW-Madison Network".

3%

C

Open Sources Software (OSS)
Use of open source software can result in significant cost savings, particularly when the amount of customization is small.

3%

A,B,C

Software as a Service (SaaS)
There are potential cost savings as major software vendors make Software as Service (SaaS) available as a standard product offering. There can be significant privacy and intellectual property concerns when using SaaS.

3%

Key: A (Access to information resources), B (Protection of information), C (Collaboration and resources sharing)

Contact

  • No labels