EDIT User Program

Editors are used to manipulate text files. From an editor program, text can be created, modified, deleted and viewed . Text files on the HP NonStop server reside in unstructured files with a disk file code of 101.

Some types of editor programs are:

EDIT

TEDIT

VS

RISK Editors can be used to view data or modify text data files.

AP-ADVICE-EDIT-01 Sensitive application data stored in text files should be strictly secured for READ, WRITE and PURGE access to only authorized personnel.

RISK Most systems contain many text files. Text files are used for configuration files, documents, help file, and many other uses. They are resident on every volume and many subvolumes . It is extremely hard to control the security of the numerous text files.

AP-ADVICE-EDIT-02 System text files, especially those on $SYSTEM.SYSTEM and $SYSTEM.SYSnn should be secured properly to control changing by unauthorized users.

RISK Once a screen editor program is started, it is impossible to secure the use of internal screen editor commands.

RISK Editors are often required by most users for every day work. Securing the editor programs to restrict access is often not reasonable, but the risks remain .

EDIT

EDIT and its components provide the ability to manipulate text (file code 101) files on the HP NonStop server. The EDIT program provides a line editor.

The components of EDIT are:

EDIT

EDITTOC

VS

Edit provides a line editor

TEDIT

TEDIT is a screen editor for text files residing on the server.

The components of TEDIT are:

TEDIT

TEDHELP

TEDMSGS

TEDPROFL

VS

VS is a screen editor for T6530-type terminals, initiated from an EDIT session.

Securing EDITORS

BP-FILE-EDIT-01 EDIT should be secured "UUNU".

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

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

BP-FILE-EDIT-02 TEDIT should be secured "UUNU".

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

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

BP-FILE-EDIT-03 VS should be secured "UUNU".

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

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

	Discovery Questions	Look here:
OPSYS-OWNER-02	Who owns the EDIT file?	Fileinfo
OPSYS-OWNER-02	Who owns the TEDIT file?	Fileinfo
OPSYS-OWNER-02	Who owns the VS file?	Fileinfo
FILE-POLICY	Who is allowed to use editors on the system?	Policy
FILE-EDIT-01	Is the EDIT object file secured correctly?	Fileinfo
FILE-EDIT-02	Is the TEDIT object file secured correctly?	Fileinfo
FILE-EDIT-03	Is the VS object file secured correctly?	Fileinfo