CL/SuperSession Started task(s) must be properly defined to the Started Task Table ACID for Top Secret.
Severity | Group ID | Group Title | Version | Rule ID | Date | STIG Version |
|---|---|---|---|---|---|---|
| medium | V-224654 | SRG-OS-000104 | ZCLST032 | SV-224654r958482_rule | 2024-12-16 | 7 |
| 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. |
| ℹ️ Check |
|---|
| 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(ZCLS0032) Verify that the CL/SuperSession started task(s) is (are) defined in the TSS STC record. |
| ✔️ Fix |
|---|
| The CL/SuperSession system programmer and the IAO will ensure that a product's started task(s) is (are) properly identified and/or defined to the System ACP. A unique ACID must be assigned for the CL/SuperSession started task(s) thru a corresponding STC table entry. The following sample set of commands is shown here as a guideline: TSS ADD(STC) PROCNAME(KLS) ACID(KLS) |