System Utilities

The following programs are system utilities.

TFDS

Failure recovery utilities

TACL tool utilities

TFD Data System

The HP TFDS data system automates tasks associated with data collection and resource recovery in the event of software- related processor or subsystem failure on G-series operating systems. It can be configured to automatically initiate a processor dump and reload the processor if the software failure is a CPU halt. Automating these steps eliminates the time delay of waiting for manual intervention to collect the data and reload the processor.

TFDS can be configured to determine whether the failure is a first-time problem occurrence or the result of a recurring defect. If it is a recurring defect, TFDS will suppress redundant dumps and instead, track the number of occurrences, and notify HP.

TFDS consists of these components :

DUMPUTIL

RCVDUMP

RELOAD

RPDUMP

TFDS

TFDSCOM

TFDSCONF

TFDS gathers information with little or no impact on the production environment. It takes no processor time to constantly monitor the system; it is awakened only when action is necessary.

RISK TFDS is a reporting program, it poses no security risks.

However, it is not normally run by the general user and should only be run by authorized personnel.

DUMPUTIL

The fixup utility, DUMPUTIL, is part of the Fast Memory Dump to relate the two CPU dumps.

RCVDUMP

The Recovery Engine performs data collection and initiates processor reloads when necessary. The object file for the Recovery Engine is RCVDUMP.

Processing an RCVDUMP does have an impact on system performance.

RISK TFDS can accept several dump requests simultaneously , but multiple RCVDUMPs running concurrently places an extreme load on a system.

AP-FILE-TFDS-01 Use the MAXCONDUMPS command to indicate the number of concurrent CPU dumps TFDS should be allowed to initiate.

RELOAD

The RELOAD program reloads processors. It is also used to load processors during a cold load of the system.

PRDUMP

The PRDUMP utility is part of the Fast Memory Dump to post-reload the dump.

TFDS monitor

The TFDS monitor constantly watches system messages for notification of software- related processor halts or software failure. TFDS takes no processor time for this monitoring; it is awakened only when action is necessary. The TFDS monitor process is $ZDMP.

RISK The TFDS process ($ZDMP) must be running when a software failure event occurs to utilize most TFDS services, so it should be running at all times.

AP-ADVICE-TFDS-02 The TFDS process ($ZDMP) should be running at all times.

TFDSCOM

TFDSCOM is the command interpreter for the TFDS Monitor used to display or modify configuration values, to save a specific configuration, to start or cancel activities, and to request help.

TFDSCONF

TFDSCONF is a configuration file used to configure the TFDS system.

Securing TFDS

BP-FILE-TFDS-01 DUMPUTIL should be secured "UUCU".

BP-OPSYS-OWNER-01 DUMPUTIL should be owned by SUPER.SUPER.

BP-OPSYS-FILELOC-01 DUMPUTIL must reside in $SYSTEM.SYSnn

BP-FILE-TFDS-02 RCVDUMP should be secured "UUCU".

BP-OPSYS-OWNER-01 RCVDUMP should be owned by SUPER.SUPER.

BP-OPSYS-FILELOC-01 RCVDUMP must reside in $SYSTEM.SYSnn

BP-FILE-TFDS-03 RELOAD should be secured "UUCU".

BP-OPSYS-LICENSE-01 RELOAD must be LICENSED.

BP-OPSYS-OWNER-01 RELOAD should be owned by SUPER.SUPER.

BP-OPSYS-FILELOC-01 RELOAD must reside in $SYSTEM.SYSnn

BP-FILE-TFDS-04 PRDUMP should be secured "UUCU".

BP-OPSYS-OWNER-01 PRDUMP should be owned by SUPER.SUPER.

BP-OPSYS-FILELOC-01 PRDUMP must reside in $SYSTEM.SYSnn

BP-PROCESS-TFDS-01 The $ZDMP process should be running.

BP-FILE-TFDS-05 TFDS should be secured "UUCU".

BP-OPSYS-LICENSE-01 TFDS must be LICENSED.

BP-OPSYS-OWNER-01 TFDS should be owned by SUPER.SUPER.

BP-OPSYS-FILELOC-01 TFDS must reside in $SYSTEM.SYSnn

BP-FILE-TFDS-06 TFDSCOM should be secured "UUCU".

BP-OPSYS-LICENSE-01 TFDSCOM must be LICENSED.

BP-OPSYS-OWNER-01 TFDSCOM should be owned by SUPER.SUPER.

BP-OPSYS-FILELOC-01 TFDSCOM must reside in $SYSTEM.SYSnn

BP-FILE-TFDS-07 TFDSCONF should be secured "CUUU".

BP-OPSYS-OWNER-03 TFDSCONF should be owned by SUPER.SUPER.

BP-OPSYS-FILELOC-03 TFDSCONF resides in $SYSTEM.ZTFDS

If available, use Safeguard software or a third party object security product to grant access to the TFDS components only to users who require access in order to perform their jobs.

BP-SAFE-TFDS-01 Add a Safeguard Protection Record to grant appropriate access to the TFDS object file.

BP-SAFE-TFDS-02 Add a Safeguard Protection Record to grant appropriate access to the TFDSCOM object file.

BP-SAFE-TFDS-03 Add a Safeguard Protection Record to grant appropriate access to the RELOAD object file.

	Discovery Questions	Look here:
FILE-POLICY	Who is allowed to execute TFDS and related functions on production systems?	Policy
PROCESS-TFDS-01	Is the $ZDMP process running?	Status
OPSYS-OWNER-01	Who owns the DUMPUTIL object file?	Fileinfo
OPSYS-OWNER-01	Who owns the RCVDUMP object file?	Fileinfo
OPSYS-OWNER-01	Who owns the RELOAD object file?	Fileinfo
OPSYS-OWNER-01	Who owns the PRDUMP object file?	Fileinfo
OPSYS-OWNER-01	Who owns the TFDS object file?	Fileinfo
OPSYS-OWNER-01	Who owns the TFDSCOM object file?	Fileinfo
OPSYS-OWNER-03	Who owns the TFDSCONF object file?	Fileinfo
OPSYS-LICENSE-01	Is the RELOAD file licensed?	Fileinfo
OPSYS-LICENSE-01	Is the TFDS file licensed?	Fileinfo
OPSYS-LICENSE-01	Is the TFDSCOM file licensed?	Fileinfo
FILE-TFDS-01	Is the DUMPUTIL object file secured correctly?	Fileinfo
FILE-TFDS-02	Is the RCVDUMP object file secured correctly?	Fileinfo
FILE-TFDS-03 SAFE-TFDS-03	Is the RELOAD file correctly secured with the Guardian or Safeguard system?	Fileinfo Safeguard
FILE-TFDS-04	Is the PRDUMP object file secured correctly?	Fileinfo
FILE-TFDS-05
SAFE-TFDS-01	Is the TFDS file correctly secured with the Guardian or Safeguard system?	Fileinfo Safeguard
FILE-TFDS-06
SAFE-TFDS-02	Is the TFDSCOM file correctly secured with the Guardian or Safeguard system?	Fileinfo Safeguard
FILE-TFDS-07	Is the TFDSCONF object file secured correctly?	Fileinfo

Failure Utilities

The HP NonStop server provides several TACL utilities and utility programs that perform functions when a processor halts and creates a dump file.

These functions should only be performed by qualified personnel, who are normally part of the SUPER Group.

The utilities are:

COPYDUMP

CRUNCH

GARTH

RCVDUMP

COPYDUMP

The COPYDUMP program copies and compresses a tape dump file into a disk dump file.

CRUNCH

A utility program supplied by HP to analyze CPU dumps on pre Release Version G06 operating systems.

GARTH

GARTH is a utility program supplied by HP to analyze CPU dumps on Release version G06 operating systems. The TACL macro GARTH, initiates the GARTHNSK from the ZGARTH subvolume.

RECEIVEDUMP/RCVDUMP

The RECEIVEDUMP TACL command initiates the RCVDUMP program to receive the dump from a halted processor over the interprocessor bus.

Securing Failure Tools

BP-FILE-FTOOLS-01 COPYDUMP should be secured "UUCU".

BP-OPSYS-LICENSE-01 COPYDUMP must be LICENSED.

BP-OPSYS-OWNER-01 COPYDUMP should be owned by SUPER.SUPER.

BP-OPSYS-FILELOC-01 COPYDUMP must reside in $SYSTEM.SYSnn

BP-FILE-FTOOLS-02 CRUNCH should be secured "UUCU".

BP-OPSYS-OWNER-02 CRUNCH should be owned by SUPER.SUPER.

BP-OPSYS-FILELOC-02 CRUNCH must reside in $SYSTEM.SYSTEM

BP-FILE-FTOOLS-03 GARTH should be secured "CUCU".

BP-OPSYS-OWNER-02 GARTH should be owned by SUPER.SUPER.

BP-OPSYS-FILELOC-02 GARTH must reside in $SYSTEM.SYSTEM

BP-FILE-FTOOLS-04 GARTHNSK should be secured "UUCU".

BP-OPSYS-OWNER-03 GARTHNSK should be owned by SUPER.SUPER.

BP-OPSYS-FILELOC-03 GARTHNSK resides in $SYSTEM.ZGARTH

BP-FILE-FTOOLS-05 RCVDUMP should be secured "UUCU".

BP-OPSYS-OWNER-01 RDVDUMP should be owned by SUPER.SUPER.

BP-OPSYS-FILELOC-01 RDVDUMP must reside in $SYSTEM.SYSnn

	Discovery Questions	Look here:
FILE-POLICY	Who is allowed to manage processor halts and related functions on production systems?	Policy
OPSYS-OWNER-01	Who owns the COPYDUMP object file?	Fileinfo
OPSYS-OWNER-01	Who owns the CRUNCH object file?	Fileinfo
OPSYS-OWNER-01	Who owns the GARTH macro file?	Fileinfo
OPSYS-OWNER-01	Who owns the GARTHNSK object file?	Fileinfo
OPSYS-OWNER-01	Who owns the RCVDUMP object file?	Fileinfo
OPSYS-LICENSE-01	Is the COPYDUMP file licensed?	Fileinfo
FILE-FTOOLS-01	Is the COPYDUMP object file secured correctly?	Fileinfo
FILE-FTOOLS-02	Is the CRUNCH object file secured correctly?	Fileinfo
FILE-FTOOLS-03	Is the GARTH file secured correctly?	Fileinfo
FILE-FTOOLS-04	Is the GARTHNSK file secured correctly?	Fileinfo
FILE-FTOOLS-05	Is the RCVDUMP object file secured correctly?	Fileinfo

TACL Tool Utilities

The HP NonStop server provides several TACL utilities and utility programs that perform specific functions for analyzing internal components.

The utilities are:

FCHECK

FILCHECK

TANDUMP

FCHECK

The FCHECK program reports on the internal consistency of Enscribe files.

FCHECK is most often used to verify the structure and validity of a file. FCHECK cannot be used to alter the physical structure of a file.

RISK FCHECK is strictly a reporting tool and, therefore, poses no security risks.

FILCHECK

The FILCHECK program reports on the internal, physical data structure of objects and verifies that the structure is consistent.

The FILCHECK utility checks the physical structure of a DP2 structured object and reports any errors. The internal checks include the following:

Forward and backward pointers in blocks

Relative sector number and checksum of every block

Correct index levels

Data block and index block linkage and length

Block headers and rows in relative files

Offset pointers and order

Existence of any unreclaimed free space in the object

RISK FILCHECK is strictly a reporting tool and, therefore, poses no security risks.

TANDUMP

TANDUMP is a binary file editor, which can display and/or modify the contents of disk files.

This function should only performed by qualified personnel, who are normally part of the SUPER Group.

RISK TANDUMP could be used to display or modify sensitive data or programs. It should not be available to the general user, nor should it be used by non-qualified personnel.

BP-FILE-TANDUMP-01 TANDUMP should not be available to the general user, nor should it be used by non-qualified personnel.

Securing TACL Tools

BP-FILE-TACLTOOL-01 FCHECK should be secured "UUNU".

BP-OPSYS-LICENSE-01 FCHECK must be LICENSED.

BP-OPSYS-OWNER-01 FCHECK should be owned by SUPER.SUPER.

BP-OPSYS-FILELOC-01 FCHECK must reside in $SYSTEM.SYSnn.

BP-FILE- TACLTOOL-02 FILCHECK should be secured "UUNU".

BP-OPSYS-LICENSE-01 FILCHECK must be LICENSED.

BP-OPSYS-OWNER-01 FILCHECK should be owned by SUPER.SUPER.

BP-OPSYS-FILELOC-01 FILCHECK must reside in $SYSTEM.SYSnn.

BP-FILE- TACLTOOL-03 TANDUMP should be secured "UUUU".

BP-OPSYS-OWNER-01 TANDUMP should be owned by SUPER.SUPER.

BP-OPSYS-FILELOC-01 TANDUMP must reside in $SYSTEM.SYSnn.

If available, use Safeguard software or a third party object security product to grant access to the TANDUMP components only to users who require access in order to perform their jobs.

BP-SAFE-TACLTOOL-01 Add a Safeguard Protection Record to grant appropriate access of the FCHECK object file.

BP-SAFE-TACLTOOL-02 Add a Safeguard Protection Record to grant appropriate access of the FILCHECK object file.

BP-SAFE-TACLTOOL-03 Add a Safeguard Protection Record to grant appropriate access of the TANDUMP object file.

	Discovery Questions	Look here:
OPSYS-OWNER-01	Who owns the FCHECK object file?	Fileinfo
OPSYS-OWNER-01	Who owns the FILCHECK object file?	Fileinfo
OPSYS-OWNER-01	Who owns the TANDUMP object file?	Fileinfo
OPSYS-LICENSE-01	Is the FCHECK file licensed?	Fileinfo
OPSYS-LICENSE-01	Is the FILCHECK file licensed?	Fileinfo
FILE-TACLTOOL-01	Is the FCHECK object file secured correctly?	Fileinfo
FILE-TACLTOOL-02	Is the FILCHECK object file secured correctly?	Fileinfo
FILE-POLICY	Who is allowed to execute TANDUMP on production systems?	Policy
FILE-TACLTOOL-03 SAFE-TACLTOOL-01	Is the TANDUMP file correctly secured with the Guardian or Safeguard system?	Fileinfo Safeguard