Brocade Fabric OS Message Reference - Supporting Fabric OS v7.0.1 (53-1002448-01, March 2012)

824 Fabric OS Message Reference
53-1002448-01
SEC-3002
134
SEC-3002
Message <Sequence Number> AUDIT, <timestamp>, [SEC-3002], INFO, SECURITY,
<event-initiator-details>, <event-location>, , Event: <Event Name>, Status:
success, Info: <Event Related Info>.
Probable Cause Indicates the specified security event has occurred. The Event Name can be one of the following:
• There has been an fabric configurations server (FCS) failover.
• A security policy has been activated.
• A security policy has been saved.
• A security policy has been aborted.
• A non-FCS password has changed.
Recommended
Action
Verify the security event was planned. If the security event was planned, no action is required. If the
security event was not planned, take appropriate action as defined by your enterprise security
policy.
Severity INFO
SEC-3003
Message <Sequence Number> AUDIT, <timestamp>, [SEC-3003], INFO, SECURITY,
<event-initiator-details>, <event-location>, , Event: <Event Name>, Status:
success, Info: Created <Policy Name> policy, with member(s) <Member List> .
Probable Cause Indicates a new security policy was created with entries. If you use a wildcard (for example, an
asterisk) in creating a policy, the audit report displays the wildcard in the event info field.
Recommended
Action
Verify the new policy creation was planned. If the new policy creation was planned, no action is
required. If the new policy creation was not planned, take appropriate action as defined by your
enterprise security policy.
Severity INFO
SEC-3004
Message <Sequence Number> AUDIT, <timestamp>, [SEC-3004], INFO, SECURITY,
<event-initiator-details>, <event-location>, , Event: <Event Name>, Status:
success, Info: Created <Policy name> policy.
Probable Cause Indicates a new security policy was created. If you use a wildcard (for example, an asterisk) in
creating a member for a policy, the audit message displays the wildcard in the event info field.
Recommended
Action
Verify the new policy creation was planned. If the new policy creation was planned, no action is
required. If the new policy creation was not planned, take appropriate action as defined by your
enterprise security policy.
Severity INFO