Please report any problems to the Shared Tools Team at st-help@doit.wisc.edu    Broken Links? Missing Macros? WIKI Retiring Plugins
Child pages
  • Incident Resp Subcommittee Description
Skip to end of metadata
Go to start of metadata

File Created Comment

Incident Response Subcommittee Description-2018-03-07.docx

Mar 09, 2018 11:32 SUPERCEEDED, 3/7 version (the original) that focuses on alignment with UW System Policy. Not necessary because the policy and procedures are already in alignment.

Incident Response Subcommittee Description-2018-03-26.docx

Mar 27, 2018 11:46 CURRENT: 3/26 version, with purpose changed to recommending improvements to the policy and procedures.

Incident Response Subcommittee

of the Policy Planning and Analysis Team

Purpose

The purpose of the Incident Response Subcommittee of the Policy Planning and Analysis Team (PAT) is to make recommendations on how to improve the UW-Madison Incident Response Policy and  Procedures .  The subcommittee may also make recommendations on ways to increase compliance.

Organization and Reporting

The Subcommittee is commissioned by the PAT Executive Committee (PAT EC) as described in the PAT Charter . The PAT EC serves as the sponsor of the the Subcommittee, and will advise the Subcommittee as needed.  The Subcommittee reports to the PAT EC, which will comment on and pass the Subcommittee’s recommendations to the PAT, and from there onward to the Office of Cybersecurity .

Scope

The Subcommittee :

  1. should make recommendations on how to improve the UW-Madison Incident Response Policy and  Procedures .
  2. may make recommendations on how to increase compliance.

Out-of-Scope

The Subcommittee :

  1. should not write or revise the text of UW-Madison IT policies and related documents. The IT Policy Process will be used to create or revise IT policy documents.
  2. should not implement recommendations to improve compliance.

Timeframe

The UW-Madison policy and procedures are already in alignment with UW System Policy.

  1. The Subcommittee should deliver a preliminary report by July 13th.
  2. The final report should be delivered by October 12 th .

 

  • No labels