What changed in Microsoft OneNote 2016 STIG V2R1V2R1 changes

Microsoft OneNote 2016 STIG V2R1 (2026-01-05) replaced V1R2 (2017-01-19): 11 checks added, 10 removed. It has 11 checks, against 10 in V1R2.

V2R1 checklistV1R2 checklist Compare V1R2 and V2R1 in STIG Compare

  • 11 added
  • 10 removed
  • 0 updated

Added in V2R1 (11)

  • V-238044CAT IIDisabling of user name and password syntax from being used in URLs must be enforced.
  • V-238045CAT IIEnabling IE Bind to Object functionality must be present.
  • V-238046CAT IISaved from URL mark to assure Internet zone processing must be enforced.
  • V-238047CAT IINavigation to URLs embedded in Office products must be blocked.
  • V-238048CAT IIScripted Window Security must be enforced.
  • V-238049CAT IIAdd-on Management functionality must be allowed.
  • V-238050CAT IILinks that invoke instances of Internet Explorer from within an Office product must be blocked.
  • V-238051CAT IIFile Downloads must be configured for proper restrictions.
  • V-238052CAT IIProtection from zone elevation must be enforced.
  • V-238053CAT IIActiveX Installs must be configured for proper restriction.
  • V-279944CAT IThe version of OneNote running on the system must be a supported version.

Removed since V1R2 (10)

  • V-70829CAT IIDisabling of user name and password syntax from being used in URLs must be enforced.
  • V-70831CAT IIEnabling IE Bind to Object functionality must be present.
  • V-70833CAT IISaved from URL mark to assure Internet zone processing must be enforced.
  • V-70835CAT IINavigation to URLs embedded in Office products must be blocked.
  • V-70837CAT IIAdd-on Management functionality must be allowed.
  • V-70839CAT IILinks that invoke instances of Internet Explorer from within an Office product must be blocked.
  • V-70841CAT IIFile Downloads must be configured for proper restrictions.
  • V-70843CAT IIProtection from zone elevation must be enforced.
  • V-70845CAT IIActiveX Installs must be configured for proper restriction.
  • V-70847CAT IIScripted Window Security must be enforced.

How these changes are found

Checks are matched across the two releases by V-number. A check counts as updated when DISA gave it a new rule revision (the r number in its SV-…_rule id) and its title, severity, check text, fix text, discussion, CCIs or other fields changed — the same comparison STIG Compare makes. Added checks are new V-numbers; removed checks are V-numbers V2R1 no longer has.

Comparing other releases, or this one against an older release? Pick any two in STIG Compare.