[Openstack-security] [Bug 1590911] Re: Security role audit rules should have key fields

OpenStack Infra 1590911 at bugs.launchpad.net
Fri Jun 10 07:46:04 UTC 2016


Reviewed:  https://review.openstack.org/327872
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-security/commit/?id=44e6056a933a53456711b6e8b3f2dae906830f8e
Submitter: Jenkins
Branch:    master

commit 44e6056a933a53456711b6e8b3f2dae906830f8e
Author: Major Hayden <major at mhtx.net>
Date:   Thu Jun 9 13:42:18 2016 -0500

    Add key fields to audit rules
    
    This patch adjusts the key fields in the audit rules that are added
    by the security rule to make it easier to link a log entry with the
    audit rules that caused it. Deployers with overflowing logs should
    be able to narrow down the rule much more easily.
    
    Closes-Bug: 1590911
    
    Change-Id: I39c673d515467f685004463e914a0a1aaec3c153


** Changed in: openstack-ansible
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of OpenStack
Security, which is subscribed to OpenStack.
https://bugs.launchpad.net/bugs/1590911

Title:
  Security role audit rules should have key fields

Status in openstack-ansible:
  Fix Released

Bug description:
  The audit rules added by the security role should have a key field
  added so that it's easier to figure out which rule caused something to
  be audited.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openstack-ansible/+bug/1590911/+subscriptions




More information about the Openstack-security mailing list