Select any two versions of this STIG to compare the individual requirements
Select any old version/release of this STIG to view the previous requirements
Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(NCPASRPT) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZNCP0000) Verify that the accesses to the Quest NC-Pass installation data sets are properly restricted. If the following guidance is true, this is not a finding. ___ The TSS data set rules for the data sets restricts READ access to all authorized users. ___ The TSS data set rules for the data sets restricts WRITE and/or greater access to systems programming personnel. ___ The TSS data set rules for the data sets specify that all (i.e., failures and successes) WRITE and/or greater access is logged.
The IAO will ensure that WRITE and/or greater access to Quest NC-Pass installation data sets is limited to System Programmers only, and all WRITE and/or greater access is logged. READ access can be given to all authorized users. The installing Systems Programmer will identify and document the product data sets and categorize them according to who will have WRITE and/or greater access and if required that all WRITE and/or greater access is logged. He will identify if any additional groups have WRITE and/or greater access for specific data sets, and once documented he will work with the IAO to see that they are properly restricted to the ACP (Access Control Program) active on the system. Data sets to be protected will be: SYS2.NCPASS. SYS3.NCPASS. (data sets that are not altered by product STCs, can be more specific) The following commands are provided as a sample for implementing data set controls: TSS PERMIT(<syspaudt>) DSN(SYS2.NCPASS.) ACCESS(R) TSS PERMIT(<syspaudt>) DSN(SYS2.NCPASS.) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(<tstcaudt>) DSN(SYS2.NCPASS.) ACCESS(R) TSS PERMIT(<tstcaudt>) DSN(SYS2.NCPASS.) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(<audtaudt>) DSN(SYS2.NCPASS.) ACCESS(R) TSS PERMIT(ALL) DSN(SYS2.NCPASS.) ACCESS(R) TSS PERMIT(<syspaudt>) DSN(SYS3.NCPASS.) ACCESS(R) TSS PERMIT(<syspaudt>) DSN(SYS3.NCPASS.) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(<tstcaudt>) DSN(SYS3.NCPASS.) ACCESS(R) TSS PERMIT(<tstcaudt>) DSN(SYS3.NCPASS.) ACCESS(ALL) ACTION(AUDIT) TSS PERMIT(<audtaudt>) DSN(SYS3.NCPASS.) ACCESS(R) TSS PERMIT(*) DSN(SYS3.NCPASS.) ACCESS(R)
Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(NCPASSTC) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZNCP0001) Verify that the accesses to the Quest NC-Pass STC data sets are properly restricted. ___ The TSS data set rules for the data sets restricts READ access to auditors. ___ The TSS data set rules for the data sets restricts UPDATE access to domain level security administrators. ___ The TSS data set rules for the data sets restricts WRITE and/or greater access to systems programming personnel. ___ The TSS data set rules for the data sets restricts WRITE and/or greater access to the Quest NC-Pass’s STC(s) and/or batch user(s).
The IAO will ensure that WRITE and/or greater access to Quest NC-Pass STC data sets is limited to System Programmers and/or Quest NC-Pass’s STC(s) and/or batch user(s) only. UPDATE access can be given to domain level security administrators. READ access can be given to auditors. The installing Systems Programmer will identify and document the product data sets and categorize them according to who will have update and alter access and if required that all update and allocate access is logged. He will identify if any additional groups have update and/or alter access for specific data sets, and once documented he will work with the IAO to see that they are properly restricted to the ACP (Access Control Program) active on the system. Data sets to be protected will be: SYS3.NCPASS.*.PASSCAF SYS3.NCPASS.*.PASSVSDD The following commands are provided as a sample for implementing data set controls: TSS PERMIT(<syspaudt>) DSN(SYS3.NCPASS.*.PASSCAF) ACCESS(ALL) TSS PERMIT(<tstcaudt>) DSN(SYS3.NCPASS.*.PASSCAF) ACCESS(ALL) TSS PERMIT(NCASS STCs) DSN(SYS3.NCPASS.*.PASSCAF) ACCESS(ALL) TSS PERMIT(<secaaudt>) DSN(SYS3.NCPASS.*.PASSCAF) ACCESS(U) TSS PERMIT(<audtaudt>) DSN(SYS3.NCPASS.*.PASSCAF) ACCESS(R) TSS PERMIT(<syspaudt>) DSN(SYS3.NCPASS.*.PASSVSDD) ACCESS(ALL) TSS PERMIT(<tstcaudt>) DSN(SYS3.NCPASS.*.PASSVSDD) ACCESS(ALL) TSS PERMIT(NCASS STCs) DSN(SYS3.NCPASS.*.PASSVSDD) ACCESS(ALL) TSS PERMIT(<secaaudt>) DSN(SYS3.NCPASS.*.PASSVSDD) ACCESS(U) TSS PERMIT(<audtaudt>) DSN(SYS3.NCPASS.*.PASSVSDD) ACCESS(R)
Refer to the following report produced by the TSS Data Collection: - TSSCMDS.RPT(@ACIDS) Verify that the ACID(s) for the Quest NC-Pass started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding. FACILITY(STC, BATCH) PASSWORD(xxxxxxxx,0) SOURCE(INTRDR) NOSUSPEND MASTFAC(NCPASS)
The IAO working with the systems programmer will ensure the Quest NC-Pass Started Task(s) is properly identified and/or defined to the System ACP. If the product requires a Started Task, verify that it is properly defined to the System ACP with the proper attributes. Most installation manuals will indicate how the Started Task is identified and any additional attributes that must be specified. The following commands are provided as a sample for defining Started Task(s): TSS CREATE(NCPASS) TYPE(USER) - NAME('STC, Quest NC-Pass') DEPT(xxxx) - FAC(STC,BATCH) PASS(xxxxxxxx,0) - SOURCE(INTRDR) NOSUSPEND MASTFAC(NCPASS)
Refer to the following report produced by the TSS Data Collection: - TSSCMDS.RPT(#STC) Automated Analysis Refer to the following report produced by the TSS Data Collection: - PDI(ZNCP0032) If the Quest NC-Pass started task(s) is (are) defined in the TSS STC record, this is not a finding.
The IAO working with the systems programmer will ensure the Quest NC-Pass Started Task(s) is properly identified and/or defined to the System ACP. A unique ACID must be assigned for the CA 1 Tape Management started task(s) thru a corresponding STC table entry. The following commands are provided as a sample for defining Started Task(s): TSS ADD(STC) PROCNAME(NCPASS) ACID(NCPASS)
Refer to the following report produced by the TSS Data Collection: - TSSCMDS.RPT(FACLIST) - Preferred report containing all control option values in effect including default values - TSSCMDS.RPT(TSSPRMFL) - Alternate report containing only control option values explicitly coded at TSS startup If the Quest NC-Pass Facility Matrix table is defined as stated below, this is not a finding. FACILITY DISPLAY FOR NCPASS INITPGM=NCS ID=14 TYPE=099 ATTRIBUTES=IN-USE,ACTIVE,SHRPRF,NOASUBM,NOABEND,MULTIUSER,NOXDEF ATTRIBUTES=LUMSG,STMSG,SIGN(M),INSTDATA,NORNDPW,AUTHINIT ATTRIBUTES=NOPROMPT,NOAUDIT,RES,WARNPW,NOTSOC,LCFTRANS ATTRIBUTES=MSGLC,NOTRACE,NOEODINIT,IJU,NODORMPW,NONPWR ATTRIBUTES=LUUPD MODE=FAIL DOWN=GLOBAL LOGGING=INIT,SMF,MSG,SEC9 UIDACID=8 LOCKTIME=000 DEFACID=*NONE* KEY=8 MAXUSER=03000 PRFT=003
The IAO working with the systems programmer will ensure the Facility Matrix Table for Quest NC-Pass is proper defined using the following example: *****NCPASS FAC(USERxx=NAME=NCPASS,PGM=NCS,ID=nn,ACTIVE,NOASUBM) FAC(NCPASS=LUMSG,STMSG,NORNDPW,WARNPW,MODE=FAIL) FAC(NCPASS=LOG(SMF,INIT,MSG,SEC9),UIDACID=8,LOCKTIME=000)
Refer to the following reports produced by the TSS Data Collection and Data Set and Resource Data Collection: - TSSCMDS.RPT(@ACIDS) - TSSCMDS.RPT(@ALL) - SENSITVE.RPT(WHOHABS) If all sensitive users requiring NC-Pass validation has the NCPASS Facility and permitted to the SECURID resource in the ABSTRACT resource class, this is not a finding. NOTE: Sensitive users include systems programming personnel, security personnel, and other staff (e.g., DASD management, operations, auditors, technical support, etc.) with access to sensitive resources (e.g., operator commands, ACP privileges, etc.) that can modify the operating system and system software, and review/modify the security environment.
The IAO will ensure that sensitive users are properly validated to Quest NC-Pass. NOTE: Sensitive users include systems programming personnel, security personnel, and other staff (e.g., DASD management, operations, auditors, technical support, etc.) with access to sensitive resources (e.g., operator commands, ACP privileges, etc.) that can modify the operating system and system software, and review/modify the security environment. Sensitive users requiring access to NC-PASS must be granted access to the NCPASS Facility and the SECURID resource in the ABSTRACT resource class. Use the following commands as an example: TSS ADD(acid) FAC(NCPASS) TSS PERMIT(acid) ABS(SECURID)