The Mainframe Product must audit detected potential integrity violations.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-205597 | SRG-APP-000484-MFP-000383 | SV-205597r961767_rule | CCI-002723 | medium |
| Description | ||||
| Without an audit capability, an integrity violation may not be detected. Organizations select response actions based on types of software, specific software, or information for which there are potential integrity violations. The integrity verification application must have the capability to audit and it must be enabled. | ||||
| STIG | Date | |||
| Mainframe Product Security Requirements Guide | 2026-05-23 | |||
Related Frameworks
1 mapping across 2 frameworks
Related Frameworks
NIST 800-530 mappings
No source states a mapping between these directly.
Also reachable in 2 hops (1) derived by us, not asserted by any source
Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.
- DISA STIG Benchmark (XCCDF)V3R5intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
CCI1 mapping
CCI-002723
1.00
- DISA STIG Benchmark (XCCDF)V3R5intersects(normalised)
Details
Check Text (C-205597r961767_chk)
If the Mainframe Product has no function or capability for integrity verification, this is not applicable.
Examine installation and configuration settings.
If the Mainframe Product is not configured to audit detected potential integrity violations, this is a finding.
Fix Text (F-5863r300019_fix)
Configure the Mainframe Product to audit detected potential integrity violations.