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 6 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to SPEC Innovations Innoslate 4.x Security Technical Implementation Guide

V-254096

CAT II (Medium)

Innoslate must generate audit records when DoD required events occur.

Rule ID

SV-254096r845264_rule

STIG

SPEC Innovations Innoslate 4.x Security Technical Implementation Guide

Version

V1R1

CCIs

CCI-000172

Discussion

Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). 1. Access Innoslate folder. 2. Navigate to Innoslate4\apache-tomcat\logs. 3. View the logs. Satisfies: SRG-APP-000495, SRG-APP-000496, SRG-APP-000497, SRG-APP-000498, SRG-APP-000499, SRG-APP-000500, SRG-APP-000501, SRG-APP-000502, SRG-APP-000503

Check Content

1. Locate the logging.properties file in the following directory: Innoslate\apache-tomcat\conf.
2. Modify lines 25, 29, 33, and 41 to be set to DEBUG or VERBOSE as needed.
3. If after a service restart the logs do not change, this is a finding.

Fix Text

1. Locate the logging.properties file in the following directory: Innoslate\apache-tomcat\conf.
2. Modify lines 25, 29, 33, and 41 to be set to DEBUG or VERBOSE as needed.