The SEEVIEW product provides multi-windowed capability to 6500-series terminals. SEEVIEW allows the user to view several windows simultaneously , similar to a PC workstation environment. SEEVIEW is only applicable for 65xx terminals. SEEVIEW is not necessary for environments without 6500-series terminal access.
RISK SEEVIEW is a tool and creates no extra risk. If a user can run an application in one session, then running multiple sessions incurs no risk to the system.
The components of SEEVIEW are:
SEEDIT
SEEGATE
SEELOCL/SEECSTM
SEENET
SEESHELL
SEEVIEW
SEEVIEWS
BP-FILE-SEEVIEW “01 SEEVIEW should be secured "UUNU".
BP-OPSYS-OWNER-02 SEEVIEW should be owned by SUPER.SUPER.
BP-OPSYS-FILELOC-02 SEEVIEW must reside in $SYSTEM.SYSTEM.
BP-FILE-SEEVIEW “02 SEESHELL should be secured "NUNU".
BP-OPSYS-OWNER-02 SEESHELL should be owned by SUPER.SUPER.
BP-OPSYS-FILELOC-02 SEESHELL must reside in $SYSTEM.SYSTEM.
BP-FILE-SEEVIEW “03 SEEDIT should be secured "UUNU".
BP-OPSYS-OWNER-02 SEEDIT should be owned by SUPER.SUPER.
BP-OPSYS-FILELOC-02 SEEDIT must reside in $SYSTEM.SYSTEM.
BP-FILE-SEEVIEW “04 SEEGATE should be secured "NUNU".
BP-OPSYS-OWNER-02 SEEGATE should be owned by SUPER.SUPER.
BP-OPSYS-FILELOC-02 SEEGATE must reside in $SYSTEM.SYSTEM.
BP-FILE-SEEVIEW “05 SEELOCL should be secured "NUNU".
BP-OPSYS-OWNER-02 SEELOCL should be owned by SUPER.SUPER.
BP-OPSYS-FILELOC-02 SEELOCL must reside in $SYSTEM.SYSTEM.
BP-FILE-SEEVIEW “06 SEENET should be secured "NUNU".
BP-OPSYS-OWNER-02 SEENET should be owned by SUPER.SUPER.
BP-OPSYS-FILELOC-02 SEENET must reside in $SYSTEM.SYSTEM.
BP-FILE-SEEVIEW “07 SEEVIEWS should be secured "NUNU".
BP-OPSYS-OWNER-02 SEEVIEWS should be owned by SUPER.SUPER.
BP-OPSYS-FILELOC-02 SEEVIEWS must reside in $SYSTEM.SYSTEM.
Discovery Questions | Look Here: | |
---|---|---|
FILE-POLICY | Are users allowed to use SEEVIEW on their 6500 series terminals? | Policy |
OPSYS-OWNER-02 | Who owns the SEEVIEW object file? | Fileinfo |
OPSYS-OWNER-02 | Who owns the SEESHELL object file? | Fileinfo |
OPSYS-OWNER-02 | Who owns the SEEDIT object file? | Fileinfo |
OPSYS-OWNER-02 | Who owns the SEEGATE object file? | Fileinfo |
OPSYS-OWNER-02 | Who owns the SEELOCL object file? | Fileinfo |
OPSYS-OWNER-02 | Who owns the SEENET object file? | Fileinfo |
OPSYS-OWNER-02 | Who owns the SEEVIEWS object file? | Fileinfo |
FILE-SEEVIEW-01 | Is the SEEVIEW object file secured correctly? | Fileinfo |
FILE-SEEVIEW-02 | Is the SEESHELL object file secured correctly? | Fileinfo |
FILE-SEEVIEW-03 | Is the SEEDIT object file secured correctly? | Fileinfo |
FILE-SEEVIEW-04 | Is the SEEGATE object file secured correctly? | Fileinfo |
FILE-SEEVIEW-05 | Is the SEELOCL object file secured correctly? | Fileinfo |
FILE-SEEVIEW-06 | Is the SEENET object file secured correctly? | Fileinfo |
FILE-SEEVIEW-07 | Is the SEEVIEWS object file secured correctly? | Fileinfo |