HP-UX Software Assistant Administration Guide (5900-3003, March 2013)

1
The short form of the external HP security identifier. It is comprised of the numeric portion of
the HPSBUX identifier, 02284, plus the revision number, r4.
2
The long form of the external HP security identifier, also called the HPSBUX identifier.
3
The software security response team number, which is used internally to HP.
4
The revision number. A security bulletin revision can be issued for minor or significant changes.
NOTE: The Common Vulnerabilities and Exposures (CVE) identifier, if there is one associated
with the bulletin, is available with the detailed information on the HPSC. Follow the hyperlink in
the HTML report to access this information.
Patches that fix critical issues (CRIT)
Problems are categorized as critical based on the severity of the problem, not how likely the
problem might occur. Critical problems include system panics or hangs, process failures, data
corruption, severe performance degradation, and application-specific critical issues.
If there is a newer patch in the supersession chain, that patch might be listed in the Action report,
not the patch listed as missing in this section.
Patches with warnings (PW)
This section reports patches with warnings identified by the PW orPCW analyzer. If a newer
recommendable patch exists, it will be selected. Note that in some instances the best course of
action is to retain a patch with a warning.
1
This is the posting date of the most recent patch warning.
2
Patches with critical warnings are identified here.
Specific patch (PATCH), and patch or recommended successor (CHAIN)
Given a user-specified list, the PATCH and CHAIN analyzers identify user-specified patches that
can be installed. Patches are omitted from the list because the base product is not present or
because the patch or its replacement is already installed. In an Issue report, these two analyzers
are equivalent; they differ in the recommendations made within the SWA Action report.
Automatically invoked analyzers
You might have a section for Automatically invoked analyzers (AUTO) in your report, which is an
analyzer SWA always runs and cannot be deselected. Problems in this category include missing
dependent patches and unrecognized patches. An unidentified patch can be a sign of a special
release or site-specific patch. An out-of-date catalog file might also cause unidentified patches.
20 Creating and interpreting reports