STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 7 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to z/OS Front End Processor for RACF Security Technical Implementation Guide

V-224486

CAT II (Medium)

An active log is not available to keep track of all hardware upgrades and software changes made to the FEP (Front End Processor).

Rule ID

SV-224486r1144836_rule

STIG

z/OS Front End Processor for RACF Security Technical Implementation Guide

Version

V7R2

CCIs

CCI-000318CCI-000366

Discussion

If components of the FEPs are not properly protected, they can be stolen, damaged, or disturbed. Without adequate physical security, unauthorized users can access the control panel, the operator console, and the diskette drive of the service subsystem. Therefore, they can interfere with the normal operations of the FEPs. Improper control of FEP components could compromise network operations.

Check Content

Review site documentation to validate that procedures are in place to protect the FEP service subsystem and diskette drive:

- All documents and procedures that apply to FEP operations including network management, FEP initialization, IPL, shutdown, NCP dumping, backup, and recovery.

If a log is in place to keep track of all hardware upgrades and software changes, this is not a finding.

Fix Text

The systems programmer will notice that a log of all hardware and software upgrades/changes has been created for auditing purposes and problem tracking. All changes and upgrades will be logged.