Where this offering fits
GigaSMART adds selected traffic-processing functions to a supported Gigamon design. Options such as deduplication, masking, slicing or flow generation should be chosen for a consumer requirement. Removing or changing packet content can help one tool while reducing evidence available to another.
Architecture and rollout decisions
List the transformations required and confirm platform, engine and licence dependencies. Pilot approved sample traffic through each selected operation and compare the resulting output. Have the receiving tool owner validate usefulness. Keep an original-to-transformed field or packet description so analysts understand what information was intentionally removed or altered.
An evaluation scenario for this offering
Use an approved packet sample containing a deliberately duplicated exchange and synthetic sensitive content. Select only the GigaSMART operations included in the proposed licence, then state the expected output for each consumer before processing the sample. Compare resulting content and counts with those expectations, including a consumer that still needs information another output removes. Confirm unsupported or invalid input handling using the documented configuration. Retain the operation sequence, engine and platform details, representative output and consumer approval. A successful masking or reduction result is not sufficient if it also removes context necessary for the receiving analysis.
Evidence to request for this scope
- Confirm feature-specific platform and licence requirements.
- Validate transformation accuracy on representative traffic.
- Record evidence changes and consuming-tool approval.