N10-009 ยท Documentation, lifecycle and monitoring
Flow data, packet capture and logging
Flow data, packet capture, port mirroring, syslog collectors, SIEM and API integration.
Key points
- Flow records (such as NetFlow/IPFIX) summarise conversations: source, destination, ports, bytes.
- Packet capture keeps full frames for deep analysis.
- Port mirroring (SPAN) copies traffic to a capture device.
- Syslog (UDP 514) ships device logs to a collector; a SIEM correlates logs and alerts; APIs let tools exchange data.
Practice questions
Which captures only metadata about conversations (addresses, ports, byte counts) rather than payloads?
- Full packet capture
- Flow data such as NetFlow
- A MIB
- A golden configuration
Show answer
Answer: B. Flow data such as NetFlow
Flow data summarises conversations without payloads. A packet capture stores the full frames, and syslog carries device messages.
What benefits does a central syslog collector or SIEM provide?
- Logs survive if a device is wiped or rebooted
- Events from many devices can be correlated
- It removes the need for patching
- It encrypts all user traffic
- It assigns IP addresses to clients
Show answer
Answer: A. Logs survive if a device is wiped or rebooted, B. Events from many devices can be correlated
Central collection keeps logs after a device fails or is tampered with and enables correlation across devices. It does not replace patching or encrypt your traffic.
NetFlow records let you read the contents of the files users transferred.
Show answer
Answer: False
False. Flow records contain conversation metadata only. You would need a full packet capture (and unencrypted traffic) to see content.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
