Transcription of Common Event Format Configuration Guide
{{id}} {{{paragraph}}}
Common Event Format Configuration Guide Common Event Format ArcSight, Inc. July 22, 2010. Revision 16. Common Event Format July 17, 2009. Copyright 2006 2009 ArcSight, Inc. All rights reserved. ArcSight, the ArcSight logo, ArcSight TRM, ArcSight NCM, ArcSight Enterprise Security Alliance, ArcSight Enterprise Security Alliance logo, ArcSight Interactive Discovery, ArcSight Pattern Discovery, ArcSight Logger, FlexConnector, SmartConnector, SmartStorage and CounterACT are trademarks of ArcSight, Inc. All other brands, products and company names used herein may be trademarks of their respective owners. Follow this link to see a complete statement of ArcSight's copyrights, trademarks and acknowledgements: Any network information used in the examples in this document (including IP addresses and hostnames) are for illustration purposes only. This document is ArcSight Confidential. Revision History Date Description 07/22/10 Made additional corrections to Extension Dictionary table.
Jul 22, 2010 · types of devices as well, and helps correlation engines deal with the events. Name is a string representing a human-readable and understandable description of the event. The event name should not contain information that is specifically mentioned in other fields. For example: “Port scan from 10.0.0.1 targeting 20.1.1.1” is not a good event ...
Domain:
Source:
Link to this page:
Please notify us if you found a problem with this document:
{{id}} {{{paragraph}}}