STIG ID - BACF1011: Back up the Database Regularly

Severity
: 2 - Medium
All
ACF2
records are stored in three
ACF2
databases: logonid, rule, and Infostorage. Regularly scheduled backups of the
ACF2
databases are important to ensure the integrity of these databases and avoid interruption in the service of the operating system environment. At a minimum, nightly backups of the
ACF2
database should be performed. More frequent backups (two or three times daily) will reduce the time necessary to affect recovery.
This STIG article shows how to ensure there is a backup plan in place and how to execute the plan..
Your organization will ensure that the Information System Security Officer (ISSO) has a documented plan in place to backup
ACF2
databases and critical security files and that the plan is being executed.
Identify Audit Finding
Review the following data to determine if you should consider remediation:
Follow these steps
:
  1. Check with the ISSO to determine if there is a documented plan in place to ensure that the
    ACF2
    databases and critical security files are backed up on a regular basis.
  2. Verify the GSO BACKUP record options are defined. The BACKUP record specifies the automatic backup procedures for the logonid, rule, and Infostorage databases.
    SET CONTROL GSO CONTROL LIST BACKUP XXX / BACKUP LAST CHANGED BY SYSPROG1 ON 07/25/19-09:20 #UNITS(1) BUFNO(1) CPUID(
    smfid
    ) PRISPACE(5) SECSPACE(5) STRING(
    backup completed
    ) SYSUT1 TIME(00:01) WORKUNIT(VIO)
    In this example, GSO BACKUP options are defined.
    • BUFNO(
      1
      |
      nn
      )
      Designates the number of buffers that will be specified on the SYSUT1 and BACKUP file DCBs at OPEN time. If nothing is specified the system provides 5 buffers. The BUFNO value can be up to 25. If there are plans to increase the BUFNO value, the REGION parameter on the ACF2 PROC must be increased.
    • CPUID(smfid)
      Specifies the SMF ID of the CPU designated to take the automatic backups in a multi-CPU environment. If you specify this field,
      ACF2
      compares it with the actual MVS system SMF ID.
      ACF2
      bypasses the automatic backup if the two do not match. Operators can take backups at any time from any CPU. You should designate a single CPU in a multisystem configuration as the sole automatic backup processor. Masking cannot be used in the CPUID( ) field value.
      ACF2
      interprets the dash and the asterisk as literal values and not as masking characters.
    • PRISPACE(
      5
      |
      nnn
      )
      Specifies the amount of primary work space to be allocated for backup processing. The default value is 5. The units are expressed in cylinders. This field does not display if not entered.
    • SECSPACE(
      5
      |
      nnn
      )
      Specifies the amount of secondary workspace to be allocated for backup processing. The default value is five. Units are expressed in cylinders. This field does not display if not entered.
    • STRING(string)
      Specifies a text string that you want
      ACF2
      to issue when it completes its backup. This text is usually an MVS START console command used to perform additional site-required processing. As part of the
      ACF2
      database recovery facility, a procedure named ACFBKUP is placed into SYS1.PROCLIB during the installation process. You can use ACFBKUP or a similar facility to REPRO the primary sequential backup data sets into the alternate VSAM clusters.
      If you do not specify a string,
      ACF2
      does not issue a console command.
    • SYSUT1
      |NOSYSUT1
      Indicates whether the copy to the interim SYSUT1 file will be bypassed. Normally the VSAM file is first copied to the SYSUT1 file before being copied to the backup file.
    • TIME(
      hh:mm
      |
      00:01
      )
      Specifies the time of day (24-hour format) when the backup is initiated. If you specify TIME(00:00),
      ACF2
      does not perform a backup.
      Default
      : 00:01 AM.
    • WORKVOL(volser)
      Specifies the volser of the volume where the backup work files are allocated. There is no default value for the field. This field does not display if not entered.
    • WORKUNIT(
      VIO
      |
      devicetype
      )
      Indicates the device type on which
      ACF2
      is to dynamically allocate its work files for backup processing. Device names are VIO, SYSDA, or DISK (VIO is the default). You can also use a name of your own choice. This field does not display if not entered.
    • #UNITS(
      1
      |
      nn
      )
      Indicates the number of units associated with the back-up file. Will only be used if WORKVOL has not been specified. The default value of #UNITS is 1.
  3. If a documented plan exists and the options are defined to ensure that the
    ACF2
    databases are backed up on a regular basis,
    your organization does not have an audit finding
    .
  4. If a documented plan does not exists and the options to ensure
    ACF2
    databases are backed up are not defined,
    your organization has an audit finding
    . See Remediate Audit Finding.
Remediate Audit Finding
The Systems Programmer ensures that the
ACF2
databases are backed up on a regular basis. and data sets are on a separate volume from the backup and recovery data sets to provide backup and recovery in the event of physical damage to a volume.
Follow these steps:
  1. Document a plan which ensures that the
    ACF2
    databases and critical security files are backed up on a regular basis. Your organization's systems programmer and Information System Security Officer (ISSO) develop the plan.
  2. Configure the GSO BACKUP option record fields to specify the automatic backup procedures for the logonid, rule, and Infostorage databases.
    SET CONTROL CONTROL INSERT BACKUP #UNITS(1) BUFNO(1) CPUID(
    smfid
    ) PRISPACE(5) SECSPACE(5) STRING(
    backup completed
    ) SYSUT1 TIME(00:01) WORKUNIT(VIO)
Your organization performs regularly scheduled backups of the logonid, rule, and Infostorage databases, ensuring the integrity of these databases and avoid interruption to the service of the operating system environment.
Control Correlation Identifier (CCI)
A Control Correlation Identifier (CCI) list provides a standard identifier and description for each of the singular, actionable statements that comprise a control or best practice. The following CCIs are related to this STIG. For more information, see the National Institute of Standards and Technology website.
CCIs
: CCI-000537
CCI
:
CCI-000537
Published Date
:
2009-09-21
Definition
:
The organization conducts backups of system-level information contained in the information system per organization-defined frequency that is consistent with recovery time and recovery point objectives.
Type
:
policy
References
:
NIST: NIST SP 800-53 (v3): CP-9 (b)
NIST: NIST SP 800-53 Revision 4 (v4): CP-9 (b)
NIST: NIST SP 800-53A (v1): CP-9.1 (v)