{"stig":{"title":"z/OS Quest NC-Pass for RACF Security Technical Implementation Guide","version":"7","release":"2"},"checks":[{"vulnId":"V-224523","ruleId":"SV-224523r1145267_rule","severity":"medium","ruleTitle":"Quest NC-Pass installation data sets will be properly protected.","description":"Quest NC-Pass installation data sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these data sets could result in violating the integrity of the base product, which could result in compromising the operating system or sensitive data.","checkContent":"Refer to the following report produced by the Data Set and Resource Data Collection:\n\n- SENSITVE.RPT(NCPASRPT).\n\nAutomated Analysis\nRefer to the following report produced by the Data Set and Resource Data Collection:\n\n- PDI(ZNCP0000).\n\nVerify 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.\n \nThe RACF data set rules for the data sets restricts READ access to all authorized users.\n\nThe RACF data set rules for the data sets restricts WRITE and/or greater access to systems programming personnel.\n\nThe RACF data set rules for the data sets specify that all (i.e., failures and successes) WRITE and/or greater access is logged.\n\nThe RACF data set rules for the data sets specify UACC(NONE) and NOWARNING.","fixText":"The ISSO 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.\n\nThe 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. The installing systems programmer will identify if any additional groups have WRITE and/or greater access for specific data sets, and once documented, will work with the ISSO to ensure they are properly restricted to the Access Control Program (ACP) active on the system.\n\nData sets to be protected will be:\nSYS2.NCPASS.\nSYS3.NCPASS. (data sets that are not altered by product STCs, can be more specific)\n\nThe following commands are provided as a sample for implementing data set controls:\n\nad 'SYS2.NCPASS.**' uacc(none) owner(sys2) -\n\taudit(success(update) failures(read)) -\n\tdata('Quest NC-Pass Install DS')\npe 'SYS2.NCPASS.**' id(<syspaudt> <tstcaudt>) acc(a)\npe 'SYS2.NCPASS.**' id(<audtaudt>) acc(r)\npe 'SYS2.NCPASS.**' id(*) acc(r)\n\nad 'SYS3.NCPASS.**' uacc(none) owner(sys3) -\n\taudit(success(update) failures(read)) -\n\tdata('Quest NC-Pass Install DS')\npe 'SYS3.NCPASS.**' id(<syspaudt> <tstcaudt>) acc(a)\npe 'SYS3.NCPASS.**' id(<audtaudt>) acc(r)\npe 'SYS3.NCPASS.**' id(*) acc(r)\n\nsetr generic(dataset) refresh","ccis":["CCI-001499","CCI-002234"]},{"vulnId":"V-224524","ruleId":"SV-224524r1145269_rule","severity":"medium","ruleTitle":"Quest NC-Pass STC data sets will be properly protected.","description":"Quest NC-Pass STC data sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these data sets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.","checkContent":"Refer to the following report produced by the Data Set and Resource Data Collection:\n\n- SENSITVE.RPT(NCPASSTC).\n\nAutomated Analysis\nRefer to the following report produced by the Data Set and Resource Data Collection:\n\n- PDI(ZNCP0001).\n\nVerify that the accesses to the Quest NC-Pass STC data sets are properly restricted. If the following guidance is true, this is not a finding.\n\nThe RACF data set rules for the data sets restricts READ access to auditors.\n\nThe RACF data set rules for the data sets restricts UPDATE access to domain level security administrators.\n\nThe RACF data set rules for the data sets restricts WRITE and/or greater access to systems programming personnel.\n\nThe RACF 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).\n\nThe RACF data set rules for the data sets specify UACC(NONE) and NOWARNING.","fixText":"The ISSO will ensure that WRITE and/or greater access to Quest NC-Pass STC data sets is limited to systems 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.\n\nThe 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. The installing systems programmer will identify if any additional groups have WRITE and/or greater access for specific data sets, and once documented will work with the ISSO to ensure they are properly restricted to the ACP (Access Control Program) active on the system.\n\nData sets to be protected will be:\nSYS3.NCPASS.*.PASSCAF\nSYS3.NCPASS.*.PASSVSDD\n\nThe following commands are provided as a sample for implementing data set controls:\n\nad 'SYS3.NCPASS.*.PASSCAF.**' uacc(none) owner(sys3) -\n\taudit(failures(read)) -\n\tdata('Vendor DS Profile: Quest NC-Pass')\nad 'SYS3.NCPASS.*.PASSVSDD.**' uacc(none) owner(sys3) -\n\taudit(failures(read)) -\n\tdata('Vendor DS Profile: Quest NC-Pass')\npe ' SYS3.NCPASS.*.PASSCAF.**' id(<syspaudt> <tstcaudt> NCPASS STCs) acc(a)\npe ' SYS3.NCPASS.*.PASSCAF.**' id(<secaaudt>) acc(u)\npe ' SYS3.NCPASS.*.PASSCAF.**' id(<audtaudt>) acc(r)\npe ' SYS3.NCPASS.*.PASSVSDD.**' id(<syspaudt> <tstcaudt> NCPASS STCs) acc(a)\npe ' SYS3.NCPASS.*.PASSVSDD.**' id(<secaaudt>) acc(u)\npe ' SYS3.NCPASS.*.PASSVSDD.**' id(<audtaudt>) acc(r)\n\nsetr generic(dataset) refresh","ccis":["CCI-001499"]},{"vulnId":"V-224525","ruleId":"SV-224525r1144940_rule","severity":"medium","ruleTitle":"Quest NC-Pass will be used by Highly-Sensitive users.","description":"DISA has directed that Quest NC-Pass extended authentication be implemented on all domains. All users with WRITE and/or greater access to sensitive system-level data sets and resources, or who possess special security privileges, are required to use NC-Pass for extended authentication. Typical personnel required to use NC-Pass include, but are not limited to, systems programming, security, operations, network/communications, storage management, and production control.\n\nImproper enforcement of extended authentication through NC-Pass could potentially compromise the operating system, Access Control Program (ACP), and customer data.","checkContent":"Refer to the following reports produced by the RACF Data Collection:\n\n- RACFCMDS.RPT(LISTUSER).\n- RACFCMDS.RPT(LISTGRP).\n\nIf the SECURID group is defined and all sensitive users are connected to the SECURID group, this is not a finding.\n\nNote: 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.","fixText":"The ISSO will ensure that sensitive users are properly validated to Quest NC-Pass.\n\nNote: 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.\n\nEnsure SECURID is defined to RACF. Use the following RACF AddGroup command:\n\nAG SECURID SUPGROUP(ADMIN) OWNER(ADMIN)\n\nEnsure sensitive users that require NC-Pass validation is connected to the SECURID group. Use the following command:\n\nCO userid GROUP(SECURID) OWNER(SECURID)","ccis":["CCI-000213"]},{"vulnId":"V-224526","ruleId":"SV-224526r1144942_rule","severity":"medium","ruleTitle":"Quest NC-Pass Started Task name will be properly identified and/or defined to the system ACP.","description":"Quest NC-Pass requires a started task that will be restricted to certain resources, data sets, and other system functions. Defining the started task as a userid to the system ACP allows the ACP to control the access and authorized users that require these capabilities. Failure to properly control these capabilities could compromise the operating system environment, ACP, and customer data.","checkContent":"Refer to the following report produced by the RACF Data Collection:\n\n- RACFCMDS.RPT(LISTUSER).\n\nVerify that the userid(s) for the Quest NC-Pass started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding.\n\nPROTECTED","fixText":"The ISSO working with the systems programmer will ensure the Quest NC-Pass Started Task(s) is properly identified and/or defined to the System ACP.\n\nIf the product requires a Started Task, verify that it is properly defined to the System ACP with the proper attributes.\n\nMost installation manuals will indicate how the Started Task is identified and any additional attributes that must be specified.\n\nThe following commands are provided as a sample for defining Started Task(s):\n\nau NCPASS name('STC, Quest NC-Pass') owner(stc) dfltgrp(stc) nopass -\n\tdata('Start CA1 TMS')","ccis":["CCI-000764"]},{"vulnId":"V-224527","ruleId":"SV-224527r1144944_rule","severity":"medium","ruleTitle":"Quest NC-Pass Started task will be properly defined to the STARTED resource class for RACF.","description":"Access to product resources should be restricted to only those individuals responsible for the application connectivity and who have a requirement to access these resources. Improper control of product resources could potentially compromise the operating system, ACP, and customer data.","checkContent":"Refer to the following report produced by the RACF Data Collection:\n\n- DSMON.RPT(RACSPT).\n\nAutomated Analysis\nRefer to the following report produced by the RACF Data Collection:\n\n- PDI(ZNCP0032).\n\nIf the Quest NC-Pass started task(s) is (are) defined to the STARTED resource class profile and/or ICHRIN03 table entry, this is not a finding.","fixText":"The ISSO working with the systems programmer will ensure the Quest NC-Pass Started Task(s) is properly identified and/or defined to the System ACP.\n\nA unique ACID must be assigned for the CA 1 Tape Management started task(s) thru a corresponding STC table entry.\n\nThe following commands are provided as a sample for defining Started Task(s):\n\nrdef started NCPASS.** uacc(none) owner(admin) audit(all(read)) -\n\tstdata(user(NCPASS) group(stc))\nsetr racl(started) ref","ccis":["CCI-000764"]}]}