Bug 1003774

Summary: Implement test coverage for Audit Log
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Ondrej Lukas <olukas>
Component: Logging, SecurityAssignee: Ondrej Lukas <olukas>
Status: CLOSED CURRENTRELEASE QA Contact: Ondrej Lukas <olukas>
Severity: medium Docs Contact: Russell Dickenson <rdickens>
Priority: unspecified    
Version: 6.2.0CC: brian.stansberry, jcacek
Target Milestone: GA   
Target Release: EAP 6.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-29 12:12:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 999673    
Bug Blocks:    

Description Ondrej Lukas 2013-09-03 07:41:58 UTC 
A Common Criteria Requirement is the ability to configure an audit log of management operations. The design note in the Eng Notes satisfies the criteria.
We will provide audit logging via a logging subsystem appender, similarly to EAP 5.
– Resistance to message deletion/alteration will be provided because it is possible for the user to configure an appender that uses syslog to ensure a copy of the log is in a location owned by a separate process or even in a separate server. JBoss Logging supports a syslog appender. 
– Non-repudidation of logging messages will be possible by configuring a syslog appender that uses TLS. EAP engineering will provide such an appender as part of this task-- This facility will be limited to management operation logging; not for EE application event logging.
– See https://docs.google.com/document/d/1sR1WjX7UDW-H1f4TJO4Qsd0u8p_Mjew7PDRlVgXQ05Q/edit for an analysis of possible features in an audit logging solution. Our intent is to deliver items 1 and 2 in that list.

We need test coverage for this feature.
Comment 1 Josef Cacek 2014-07-29 12:12:58 UTC 
This issue reported against older version, cannot be reproduced against latest 6.3.0. bits, which means it was fixed earlier. Therefore, we are closing this bug. Thank you for reporting this issue.