Brocade Fabric OS Message Reference - Supporting Fabric OS v5.3.0 (53-1000437-01, June 2007)

466 Fabric OS Message Reference
53-1000437-01
SEC-3003
81
SEC-3003
Message 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 that a new security policy was created with entries.
Note: 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 that 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 AUDIT, <timestamp>, [SEC-3004], INFO, SECURITY, <event-initiator-details>,
<event-location>, , Event: <Event Name>, Status: success, Info: Created <Policy
name> policy.
Probable Cause Indicates that a new security policy was created.
Note: 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 that 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-3005
Message AUDIT, <timestamp>, [SEC-3005], INFO, SECURITY, <event-initiator-details>,
<event-location>, , Event: <Event Name>, Status: success, Info: Added member(s)
<Members added> to policy <Policy name>.
Probable Cause Indicates that new member(s) have been added to the specified security policy.
Note: If you use a wildcard (for example, an asterisk) in adding members to a policy, the audit
report displays the wildcard in the event info field.
Recommended
Action
Verify that the addition of members to the policy was planned. If the addition of members was
planned, no action is required. If the addition of members was not planned, take appropriate
action as defined by your enterprise security policy.
Severity INFO