Quantcast
Channel: Shavlik User Community : Document List - All Communities
Viewing all articles
Browse latest Browse all 1352

Ivanti Patch Definition Naming Convention for Microsoft Patches

$
0
0

Overview

 

Starting with the April 11th 2017 Patch Tuesday, Microsoft no longer uses a traditional naming format for Security Bulletins. To help our customer's, we created our own naming format as follows:

 

  • Starting on Patch Tuesday April 10, 2018 the ID names will change to follow the description below.
  • Windows 10 and Office updates are now under their own ID and content can be searched by KB numbers after Tuesday April 10, 2018

The new Security Bulletin mappings our products will be using: MS[YY]-[MM]-[PP]-[KB]

  • MS = Microsoft
  • YY = Year
  • MM = Month Released
  • PP =  Product
  • Followed by the KB number

 

Here are some examples:

  • MS18-03-OFF-3114416
    • All Office patches
  • MS18-03-IE-4089187
    • All IE patches
  • MS18-03-AFP-4088785
    • All Microsoft released Flash patches
  • MS18-03-W10-4088776
    • All Windows 10 patches, rollups and Deltas
  • MS18-03-SO7-4088878
    • Security Only Update for Windows 7 and Server 2008 R2
  • MS18-03-SO8-4088880
    • Security Only Update for Server 2012
  • MS18-03-SO81-4088879
    • Security Only Update for Windows 8.1 and Server 2012 R2
  • MS18-03-MR7-4088875
    • Monthly Rollup for Windows 7 and Server 2008 R2 (this is the rollup that includes non-security fixes)
  • MS18-03-MR8-4088877
    • Monthly Rollup for Server 2012 (this is the rollup that includes non-security fixes)
  • MS18-03-MR81-4088876
    • Monthly Rollup for Windows 8.1 and Server 2012 R2 (this is the rollup that includes non-security fixes)

 

  .NET Patches will follow a slightly different naming scheme:

  • MS[YY]-[MM]-[TT][PP]-[KB]
    • YY = Year
    • MM = Month
    • TT = Type (Security Only or Monthly Rollup)
    • PP = Product (.NET)
    • KB = Parent KB
  • MS17-12-SONET-1234567MS17-12-MRNET-1234567
    • Security only patches associated with that parent KB
    • Security patch type
    • Monthly Rollup associated with that parent KB
    • Non-Security patch type

 

Non-security .NET Patches also have a slightly different naming scheme:

  • MSNS[YY]-[MM]-[TT][PP]-[KB]
    • YY = Year
    • MM = Month
    • TT = Type (Quality Preview or Quality Rollup)
    • PP = Product (.NET)
    • KB = Parent KB
  • MSNS17-12-QPNET-1234567MSNS17-12-QRNET-1234567
    • Quality Preview patches associated with that parent KB
    • Non-Security patch type
    • Quality Rollup associated with that parent KB
    • Non-Security patch type

 

Additional Information

 

Additional Naming Conventions

  • QP = Quality Preview
  • NS = Non-Security

 

Microsoft released the following article for FAQ on the changes made: Security Updates Guide dashboard and API:

 

Q: Why is the security bulletin ID number (e.g. MS16-XXX) not included in the new Security Update Guide?

A: The way Microsoft documents security updates is changing. The previous model used security bulletin webpages and included security bulletin ID numbers (e.g. MS16-XXX) as a pivot point. This form of security update documentation, including bulletin ID numbers, is being retired and replaced with the Security Update Guide. Instead of bulletin IDs, the new guide pivots on vulnerability ID numbers and KB Article ID numbers.

 

Affected Products

 

Shavlik Protect

Ivanti Patch for Windows Servers

Ivanti Patch for SCCM

 

 

        


Viewing all articles
Browse latest Browse all 1352

Trending Articles