The CriteriaModTime identifies the date and time of the last configuration event which significantly changed the behavior of this filter. This date and time is not displayed in the client NTO Control Panel. When a dynamic filter is created, it's CriteriaModTime and anueFilterCreatedTime are both set to the creation time. A port filter's CriteriaModTime will be an empty string until one of the filter configuration events listed below occurs. Events that cause CriteriaModTime to be updated: 1. Modify the filter mode; 2. Modify the filter criteria including type or values; 3. Modify the filter's port mode (for ports and port group) from network to tool, or visa versa; 4. Modify a dynamic filter from one-stage to two-stage, or visa versa; 5. Modify dynamic filter ordering; 6. Modify a 5204 dynamic filter to 'Count Matches In' packets or bytes. When any of the above events occur, all statistics are reset for this filter's row in anueNtoFilterStatsCntModHCTable and anueNtoFilterStatsCntModTable. The fields anueFilterCriteriaModTime, anueFilterCriteriaModTimestamp, anueFilterCriteriaModBy, anueFilterConfigModTimestamp, anueFilterConfigModBy, and anueFilterConfigModFields are updated. The fields anueFilterStatResetTime, anueFilterStatResetBy, anueFilterDropResetTime, and anueFilterDropResetBy are also updated since the filter configuration change triggers a statistics reset. The corresponding row in anueNtoFilterStatsCntRstHCTable and anueNtoFilterStatsCntRstTable are reset, as are all current, peak, and average statistics tables. When CriteriaModTime is updated previous statistics are no longer relevant for this filter since its behavior has been modified. Statistics aggregation and analysis should be restarted after CriteriaModTime is updated. CriteriaModTime is persistently stored in the object model. If one of the configuration events listed above has not occurred since the NTO system has been re-initialized, then the value of this object will pre-date the current system start time.