November University Policy Distribution

The November university policy distribution contains one (1) revised policy.

Revised Policy

Click on the links above to view the drafts and ensure that your feedback is captured for review during the post-comment period. Comments can include attachments, including word documents and PDFs. Feedback on the items above is due at 5:00 pm on Friday, December 11.


DRAFT POLICY REVISIONS 

SYS 640, Foreign Gifts and Contracts Reporting

These policy revisions will be effective upon signature by the president. 

  • The purpose of this policy is to establish general parameters for completing reports regarding foreign transactions required by law throughout the UW System. As the policy was up for scheduled review in November 2026, an initial review was completed leading to the following suggested revisions:
    • Section 1. Proposed changes to words for technical clarity; replaced “and” with “or” in the last sentence, changing it to “…by the institution or state or federal law”.
    • Section 2. Updated titles of the responsible officers.
    • Section 3.
      • Added “(UW)” after University of Wisconsin.
      • Proposed change to words for technical clarity; replaced “procedures” with “processes”. Change made in two places.
    • Section 4.
      • Proposed changes to words for clarity; replaced “…; contracts with; and any ownership…” with “…, contracts with, or ownership…” in the first sentence.
      • Proposed slight change to words for clarity; replaced “a single calendar year” with “the designated reporting period”.
    • Section 5.
      • Proposed changes for clarity; replaced “with legal oversight” for “that (1) has (a) legal authority to enforce regulatory or policy requirements or (b) statutory governing authority…, and (2) requires…”
      • Proposed slight change to words for clarity; replaced “legal oversight” with “legal authority to enforce regulatory or policy requirements or that has statutory governing authority”.
    • Section 6.
      • Proposed change to words for technical clarity; replaced “policy and/or procedures” with “process”.
      • Proposed change to words for clarity; replaced “…that at a minimum includes” with “Each process shall include, at a minimum,”.
      • 6.I. Proposed change replacing “and any” with “or”.
      • 6.I.1. Proposed change replacing “a report shall be provided” with “on or before January 31 and July 31 of each year, all institutions shall file a report”. Removed “by January 31 and July 31 of each year,” further down in paragraph.
      • 6.I.1. Added “with the U.S.” for clarity of “Department of Education”.
      • 6.I.1. Added “as amended” for clarity.
      • 6.I.2. Updated reporting details that have recently changed. Replaced “A report shall be provided annually to the National Science Foundation (NSF)” with “On or before October 31 or as indicated by the relevant federal agency, any institution that is a recipient of direct funding or subject to an amendment to said funding from the National Science Foundation (NSF) shall file an annual report with ”.
      • 6.I.2. Added “as amended” for clarity.
      • 6.I.2. Updated wording and sentence structure. Replaced “which requires institutions to” with “Institutions shall”. Replaced “when” with “whether or not”.
      • 6.I.2. Added “as defined in the statute” for clarity. Replaced “i.e…. etc.,” with “e.g…”
      • 6.I.2. Updated reporting details that have recently changed. Replaced “calendar” with “fiscal”.
      • 6.I.2. To support reporting details that have recently changed and may change again, added “See the NSF webpage on Foreign Financial Disclosure Report for additional information. Hyperlinking NSF webpage to https://www.research.gov/research-web/content/aboutffd#psm.
      • 6.II. Proposed changes to internal UWSA processes in Section 6.A.II. Replaced “provide semiannual reminders of reporting requirements to each institution” with “remind all UW institutions of the reporting requirements no less than 60 days prior to the deadline”.
      • 6.III. Proposed changes for clarity.
      • Replaced “with that party” with “from that party,”.
      • Replaced “will” with “shall”.
      • Removed “to investigate” for clarity.
      • 6.V. Proposed changes for clarity, adding word “affected”.
    • Section 7. Added additional related documents to serve as resources, including:

 


SYS Policy Approvals

Since November 6 2026, Interim President Wachter has approved the following interim policy action revision:

SYS 1000, Information Security: General Security and Definitions

(Effective November 11, 2026)

  • Summary of Policy and Policy Revisions
    • The purpose of this policy is to provide a list of general terms and definitions that are used in the 1000 series of the UW System Administrative policy set. The following revisions are proposed to align with the revisions to SYS 1039, Information Security: IT Risk Management:
    • Revised the definition of “residual risk”
    • Revised the definition of “risk appetite”
    • Revised the definition of “risk executive”
    • Added a definition for “risk owner”
    • Added a definition for “risk register”
    • Added a definition for “risk tolerance”
    • Revising the definition of “high impact system”
  • University Comments and Concerns
    • As these are technical revisions, the policy drafts were not distributed to the universities for comment. The Finance and General Administrative Policy Committee had no comments during their review.

SYS 1039, Information Security: IT Risk Management

(Approved November 11, 2026, effective May 1, 2027)

  • Policy Revisions
    • Reframed SYS 1039 around a scalable minimum baseline for IT risk management rather than requiring all IT asset-related risks to be formally managed and centrally reported.
    • Expanded and clarified the scope of IT risk management to include systems, services, data, processes, projects, technology-related activities, third-party services, cloud providers, and external data processors.
    • Refocused risk identification on meaningful risks that may affect university objectives and operations rather than treating individual vulnerabilities, findings, or control deficiencies as risks by default.
    • Clarified risk ownership and decision-making authority. Risk ownership should align with responsibility and authority for the affected activity or business outcome and should not default to IT or information security simply because the risk was identified through an IT or security assessment, review, or other risk management process.
    • Strengthened escalation expectations by requiring risks with residual risk above the university’s risk appetite, or risks beyond an owner’s decision-making authority, to be elevated to the appropriate level for review and decision.
    • Retained mitigation, transfer, avoidance, and acceptance as recognized risk treatment options while clarifying expectations for treatment ownership, decision-making, and documentation.
    • Replaced broad risk register expectations with a more focused requirement for universities to maintain a designated risk register for risks warranting ongoing oversight, treatment, or decision-making. At a minimum, risks exceeding the university’s risk appetite must be maintained in the register.
    • Clarified that policy exceptions may be documented separately from the risk register. Exceptions resulting in residual risk above the university’s risk appetite must be linked or otherwise associated with a corresponding risk register entry.
    • Replaced routine central reporting of individual risk acceptances and policy exceptions with periodic enterprise reporting of universities’ most significant IT risks. This allows UW Administration to focus on common trends, systemic exposures, and opportunities for coordinated mitigation or investment without transferring local risk ownership or decision-making authority.
    • Updated terminology and governance concepts to better align the policy set with recognized risk management practices and current UW risk governance objectives.

SYS 1039.A, Information Security: IT Risk Management Standard 

(Approved November 11, 2026, effective May 1, 2027)

  • Procedure Revisions
    • Replaced the current requirement to record information security risks in a centralized UW System Risk Register with a university-managed approach that can be scaled based on local needs, capabilities, and maturity.
    • Established a repeatable risk identification process while clarifying that threats, vulnerabilities, findings, incidents, and control deficiencies may inform risk identification but do not, by themselves, constitute a complete statement of risk.
    • Allows universities to use informal screening or triage to determine whether a potential risk warrants formal assessment, reducing unnecessary administrative effort for routine operational issues.
    • Requires formal risk assessments to consider likelihood and impact, document residual risk, and consider the university’s defined risk appetite when determining whether treatment, escalation, or ongoing oversight is necessary.
    • Encourages universities to periodically conduct broader institution-wide risk identification activities to identify significant, cross-cutting, or systemic risks that may not surface through routine processes, without imposing a comprehensive assessment as a recurring compliance requirement.
    • Clarifies risk ownership by aligning ownership with responsibility and authority for the affected activity, process, system, service, or business outcome. Risk owners are responsible for reviewing risks, making or recommending decisions within their authority, overseeing treatment, and escalating risks when necessary.
    • Requires universities to identify designated risk executives or authorized designees to support appropriate escalation and risk acceptance decisions.
    • Simplifies risk treatment requirements by focusing on the selected response, responsible parties, and expected timeframes rather than prescribing extensive treatment documentation and validation processes.
    • Establishes minimum risk register requirements for risks requiring ongoing governance while allowing universities to maintain additional information based on local methodology, tooling, regulatory requirements, or program maturity.
    • Establishes local documentation requirements for policy exceptions and requires periodic review of active exceptions and reassessment when material changes occur.
    • Requires risk and policy exception records to remain current and available to the Office of Information Security, Internal Audit, or other authorized parties upon request.
    • Simplifies risk closure by allowing risks to be closed or removed from active tracking when they no longer warrant ongoing oversight, treatment, or decision-making, provided the basis for closure is documented.

SYS 1039.B, Information Security: Risk Acceptance and Policy Exception Reporting

(Approved November 11, 2026, effective May 1, 2027)

  • Procedure Revisions
    • Replaces the current Notification of Risk Acceptance procedure with a new Enterprise IT Risk Reporting procedure focused on systemwide visibility into significant IT risks rather than central administration of individual risk acceptance decisions.
    • Eliminates the routine requirement for universities to submit individual risk acceptance notifications and policy exceptions to the Office of Information Security. These decisions remain locally documented and must be available to authorized parties upon request.
    • Requires universities to periodically provide a prioritized set of their most significant identified IT risks according to a recurring schedule established by the Office of Information Security.
    • Requires university leadership review of significant IT risks as part of the enterprise reporting process, reinforcing risk management as a governance and leadership activity rather than solely an information security function.
    • Establishes a limited set of minimum reporting information, including the risk statement, affected area or institutional context, residual risk rating, assigned risk owner, selected risk response, and current status.
    • Directs the Office of Information Security to aggregate and analyze reported risks to identify common themes, shared or systemic exposures, emerging concerns, and opportunities for coordinated mitigation, investment, policy, guidance, or other enterprise action.
    • Clarifies that enterprise reporting does not transfer risk ownership or decision-making authority to the Office of Information Security and that reporting a risk does not constitute approval or acceptance of the risk.

SYS 1039, 1039.A, and 1039.B University Comments and Concerns

    • Following university distribution, feedback was primarily focused on implementation burden, risk governance terminology, reporting expectations, and clarity of requirements. The policy set was further refined after distribution to address these themes and to establish a more scalable and practical baseline across universities.
    • Implementation burden and scalability: Feedback raised concerns with prescriptive requirements, including comprehensive risk assessment expectations. Recommendation incorporated. Requirements were simplified and greater flexibility was provided for universities with different levels of risk management maturity.
    • Risk acceptance and policy exception reporting: Feedback questioned routine central reporting of individual risk decisions and exceptions. Recommendation incorporated. The final revision retains local documentation requirements while refocusing SYS 1039.B on enterprise reporting of significant IT risks and trends.
    • Risk terminology and governance: Feedback included recommendations regarding terms such as Risk Owner and Risk Tolerance. No change made in some areas. Risk Owner was retained, and Risk Appetite remains the primary governance concept to avoid unnecessary complexity.
    • Risk identification and impact: Feedback recommended clarifying the types of impacts considered when identifying risks, including reputational impact. Recommendation incorporated. Risk identification language was refined and aligned more closely with the UW risk assessment methodology.
    • Editorial and structural comments: Numerous wording, formatting, and cross-reference recommendations were received. Recommendations incorporated where applicable. Several comments were ultimately superseded by broader restructuring of the policy set.
    • In addition to changes made in response to university feedback, the policy set was further simplified by reducing prescriptive documentation requirements, clarifying what warrants formal risk management, strengthening ownership and escalation expectations, and shifting enterprise reporting toward significant risk themes and shared exposures.

 


Federal Fridays 

The Universities of Wisconsin Federal Update Working group has a Federal Updates web page for the public to learn about the federal issues the UW is monitoring. The site provides a dashboard view of the various issues organized by topic, with a summary and links related to the topic.