How do you stop a data breach if you cannot even see which applications are running on your network? That is the exact problem ‘Visibility and Application Control’ solves for security professionals studying for their 350-701 exam. This topic teaches you how to look under the hood of your network traffic, identify every application that is communicating, and decide which ones are safe and which need to be blocked for good.
Jump to a section
A simple way to picture Visibility and Application Control
Because the office kitchen refrigerator has become a black hole where communal food goes to mysteriously vanish without a trace, the facilities manager decided to install a clear, lockable fridge with a sign-in sheet.
Now, before anyone can put their lunch inside, they must write their name, the date, and exactly what they’re storing on a log taped to the door. The fridge itself has a transparent front, so anyone walking by can see what’s inside without opening it. If someone tries to sneak in a container that’s labelled as “leftover pasta” but the manager can see it’s actually a whole birthday cake, that container gets flagged and removed.
This is exactly how visibility and application control work on a corporate network. The clear fridge is your network monitoring tools that let you see every packet of data flowing across the wire. The sign-in sheet is your policy engine that categorises each application by its real purpose (Oracle database traffic versus a heavily disguised peer-to-peer file-sharing tool). The manager who spots the mislabelled cake is your Intrusion Prevention System (IPS) that blocks applications pretending to be something they’re not.
Without this system, network traffic is like a blurry, locked fridge: you know food goes in and sometimes comes out, but you have no idea what’s actually inside or who touched it last.
Visibility and application control are two sides of the same coin in modern network security. Without visibility, you are flying blind. Without control, you cannot enforce your security policy even if you know what is happening. Let’s break both down from the ground up.
First, what do we mean by visibility? In an IT context, visibility means the ability to see exactly what kind of traffic is crossing your network at any given moment. This includes knowing which devices are talking to each other, which applications they are using, and how much bandwidth those applications are consuming. For a beginner, think of it like the dashboard in a car: you can see your speed, fuel level, and engine temperature. If a warning light comes on, you know something needs attention. Network visibility tools provide the same kind of dashboard for your data traffic.
The traditional tool for achieving visibility is NetFlow, which is a protocol developed by Cisco. NetFlow collects metadata about network traffic. Metadata is data about data — it does not capture the actual contents of a message, but it records who sent it, who received it, when it happened, how much data was sent, and which protocol was used. A protocol is a set of rules that allows two devices to communicate; the most common example is TCP (Transmission Control Protocol), which reliably delivers data in the correct order. NetFlow summarises these flows into a report that a security analyst can review to spot anomalies, like a sudden spike in traffic to an unknown server.
A more advanced version called IPFIX (IP Flow Information Export) is an industry standard that builds on NetFlow but allows for more flexible data collection. Both NetFlow and IPFIX give you raw traffic data, but they do not automatically tell you which application generated the traffic. That is where Network-Based Application Recognition (NBAR) comes in. NBAR is a Cisco technology that inspects packets at a deeper level to identify the specific application, even if the application tries to hide by using a non-standard port. For example, a game or a torrent client might run on port 80 (normally used for web browsing) to bypass firewalls. NBAR looks at the actual payload — the data inside the packet — to determine that it is really a game, not a webpage. This is called deep packet inspection (DPI).
Now, why does this matter for the 350-701 exam? Because the exam wants you to understand that visibility alone is useless if you cannot act on what you see. Application control is the follow-through. Once your visibility tools have identified an application, your security policy can decide whether to allow it, block it, or limit its bandwidth. Cisco’s Next-Generation Firewall (NGFW) and the Firepower Threat Defence (FTD) system are the main platforms that combine visibility and control. They use a feature called Application Visibility and Control (AVC) to do this. AVC uses NBAR to recognise the application and then applies a rule (like a Quality of Service policy) to shape the traffic. Quality of Service (QoS) is the practise of prioritising certain types of traffic — for instance, giving video conferencing more bandwidth than file downloads to prevent choppy calls.
The exam also covers Cisco Stealthwatch, which uses NetFlow to build a baseline of normal network behaviour. Once the baseline is established, Stealthwatch applies machine learning algorithms to detect behaviour that deviates from the norm, such as a device sending data to a known malicious IP address. This is called behavioural analysis. The combination of signature-based detection (looking for known malware patterns) and behavioural analysis (looking for unusual activity) is the backbone of modern traffic analysis.
Finally, there is the concept of encrypted traffic analysis. Because so much modern traffic is encrypted with TLS (Transport Layer Security), traditional DPI cannot see the payload. Cisco’s Encrypted Traffic Analytics (ETA) uses machine learning to analyse the patterns of encrypted flows — like the size and timing of packets — to classify applications without decrypting them. This is a critical skill for the exam because encryption is becoming more common, and the best answer on the test will often involve recognising that you cannot block all encrypted traffic, but you can use ETA to profile it.
To summarise, the core workflow is: collect traffic metadata (NetFlow/IPFIX), identify applications (NBAR/DPI), apply controls (AVC/QoS), and analyse behaviour (Stealthwatch/ETA). Every exam question about visibility or application control will map to one of these steps or the tools that support them.
Enable Flow Export on Network Devices
Configure Cisco routers, switches, or firewalls to export NetFlow or IPFIX records to a central collector. This generates the raw metadata (source IP, destination IP, ports, timestamps, byte counts) needed for visibility. Without this step, no traffic data exists to analyse.
Deploy a NetFlow Collector (Stealthwatch or FMC)
A collector receives all the flow records and stores them in a database. Cisco Stealthwatch or the Firepower Management Center (FMC) both can act as collectors. This step transforms raw metadata into a searchable, visual dashboard of network activity.
Configure NBAR for Application Identification
Activate Network-Based Application Recognition (NBAR) on the NGFW or router. NBAR performs deep packet inspection on a subset of the traffic to identify the specific application name (e.g., 'Facebook' or 'BitTorrent'), not just the port number. This step turns generic IP flows into labelled application data.
Create Application Control Policies
Define rules in the FMC or on the NGFW that specify which applications are allowed, blocked, or throttled. Use the identities provided by NBAR to write rules like 'Block all peer-to-peer file sharing applications' or 'Prioritise WebEx video traffic over YouTube'. This step enforces security and business policies.
Establish a Behavioural Baseline with Stealthwatch
Allow Stealthwatch to observe normal network traffic over a period (usually one to two weeks). It builds a statistical model of what 'normal' looks like for each device and user. This baseline enables the tool to automatically flag unusual behaviour, such as a workstation suddenly sending large amounts of data to a foreign IP at 3 AM.
Review Alerts and Refine Policies
When Stealthwatch or the FMC generates an alert (e.g., 'Anomaly detected — possible data exfiltration'), the analyst investigates using the dashboard. If the alert is valid, update the access control policy to block the offending application or IP. This step closes the loop: visibility leads to control, and control is continuously refined based on new visibility.
Let’s place this in a realistic business scenario. You work as a junior security analyst at a mid-sized insurance company called SecureCover Ltd. The network team has just deployed a Cisco Firepower 2100 Series NGFW at the internet edge. The Chief Information Security Officer (CISO) has received complaints from employees that the network is slow during lunch hours. The CISO also wants to ensure that no unauthorised file-sharing applications are exfiltrating customer data.
Step 1: You log into the Firepower Management Center (FMC), which is the central management console for all your security devices. You navigate to the traffic analysis dashboard and enable NetFlow export from the NGFW to the FMC’s built-in NetFlow collector. Within minutes, the dashboard shows you a live list of all the conversations happening across your network. You see that a large volume of traffic is flowing from employee laptops to a server IP that resolves to a known video-streaming domain.
Step 2: You drill down into that traffic using Application Visibility and Control (AVC). The dashboard uses NBAR to inspect the packets and tells you that the application is not standard web browsing but a specific peer-to-peer streaming service called StreamP2P. Even though the traffic is using the standard HTTPS port (443), NBAR’s deep packet inspection identified the unique handshake signature of StreamP2P. You now have visibility.
Step 3: You need control. You create an access control policy in the FMC that specifically blocks all traffic matching the StreamP2P application signature. You configure the rule to generate an alert every time a user tries to connect. Within 30 minutes, the alerts show that several employees were attempting to use the blocked service, and the network load during peak hours drops by 40%.
Step 4: The CISO asks about encrypted traffic. You deploy Cisco Stealthwatch and enable Encrypted Traffic Analytics (ETA). After one week of baseline learning, Stealthwatch flags a workstation that is sending small, regular encrypted packets to an IP in a foreign country at 3:00 AM every night. The packet sizes and timing patterns match known command-and-control (C2) behaviour for a malware variant. You report this to the incident response team, who isolate the workstation and find a hidden backdoor.
Step 5: You document this entire process for your organisation’s security playbook. The CISO presents your work to the board, demonstrating that the company now has real-time visibility into its network traffic and the ability to control risky applications. For the 350-701 exam, you would need to know that the tool you used for step 2 was NBAR, the policy engine was the FMC’s access control policy, and the encrypted traffic analysis was powered by ETA inside Stealthwatch.
The 350-701 exam tests Visibility and Application Control in several specific ways, and knowing these patterns will save you valuable time on exam day. The exam writers love to set traps where you must choose the most specific or most modern tool for a given task.
First, you need to memorise the exact differences between the tools that provide visibility. A common question format is: ‘Which Cisco technology identifies applications using deep packet inspection?’ The answer is always NBAR. Do not pick NetFlow or IPFIX, because those collect metadata only, not application identity. Another frequent trap: ‘Which tool analyses encrypted traffic without decryption?’ The answer is Encrypted Traffic Analytics (ETA). Some candidates incorrectly choose decryption proxy or SSL inspection, but the exam expects you to know that ETA does the job without breaking encryption.
Second, the exam tests your understanding of where these technologies fit in the network architecture. You will see questions about the difference between a Next-Generation Firewall (NGFW) and a traditional firewall. The key point is that NGFW includes application awareness and intrusion prevention, while a traditional firewall only looks at source/destination IPs and ports. If a question describes blocking an application like Skype by looking at packet signatures, the correct technology is an NGFW with AVC enabled.
Third, the exam expects you to know which protocol provides the flow export data. NetFlow is Cisco-proprietary, and IPFIX is the standardised version. A question might ask: ‘Which flow export protocol is defined by IETF standards?’ The answer is IPFIX. Be ready for a question that gives you a scenario where the network team has a mix of Cisco and non-Cisco devices — you need to choose IPFIX for compatibility.
Fourth, the subtopic of behavioural analysis using Stealthwatch often appears. The exam asks: ‘Which solution uses machine learning to establish a baseline of normal behaviour?’ The answer is Stealthwatch (or Cognitive Threat Analytics, which is a related cloud-based service). The trap here is that some candidates think NBAR does behavioural analysis, but NBAR only identifies applications. Stealthwatch analyses the behaviour over time.
Fifth, the exam quizzes you on the policy enforcement layer. You will be asked about Application Visibility and Control (AVC) and how it integrates with Cisco’s policy framework, specifically Identity Services Engine (ISE). A typical question: ‘A security policy requires that all social media traffic be blocked for users in the HR department but allowed for marketing. Which two technologies work together to achieve this?’ The correct answer pairs ISE (which identifies the user via their login credentials) with AVC (which identifies the social media traffic).
Key definitions to memorise:
NetFlow: records flow metadata (source IP, destination IP, ports, protocol, timestamps).
IPFIX: standardised version of NetFlow.
NBAR: performs deep packet inspection to identify applications.
AVC: combination of NBAR for identification and QoS or access control for enforcement.
QoS: prioritises traffic based on policy.
Stealthwatch: uses NetFlow data and behavioural analytics for threat detection.
ETA: classifies encrypted traffic by pattern analysis without decryption.
Exam traps to watch for:
Choosing ‘Packet capture’ when the question asks for a NetFlow-based solution. Packet capture records every bit, which is too heavy for continuous monitoring.
Assuming that ‘Application Control’ only means blocking. On the exam, it also includes bandwidth shaping (QoS) and prioritisation.
Confusing NBAR with a firewall rule. NBAR identifies; a firewall rule enforces.
Finally, the exam will present you with a scenario involving an unknown application running on port 443. The correct first step is to use NBAR to identify the application rather than blindly blocking the port. If you block port 443 entirely, you shut down all HTTPS traffic, which is not the goal.
Visibility is the ability to see which applications are running on your network, and application control is the ability to enforce a policy on those applications — you cannot have effective security without both.
NetFlow collects metadata about traffic flows (who sent what, when, and how much), but it does not identify the application name — that is the job of NBAR.
NBAR uses deep packet inspection (DPI) to look inside the data payload of a packet, allowing it to identify applications even when they use non-standard ports.
Encrypted Traffic Analytics (ETA) from Cisco can classify encrypted traffic by analysing patterns like packet size and timing, without needing to decrypt the traffic.
Stealthwatch builds a baseline of normal network behaviour using NetFlow data and then uses machine learning to detect anomalous activity that might indicate a breach.
A Next-Generation Firewall (NGFW) combines traditional firewall rules with application awareness (AVC), intrusion prevention, and threat intelligence — it is the central enforcement point for application control.
Quality of Service (QoS) policies can prioritise critical business applications (like VoIP or video conferencing) over recreational traffic, even if both are allowed through the firewall.
The 350-701 exam expects you to distinguish between flow export protocols: NetFlow (Cisco proprietary) versus IPFIX (industry standard for multi-vendor environments).
These come up on the exam all the time. Here's how to tell them apart.
NetFlow
Records flow-level metadata (IPs, ports, timestamps, byte counts)
Does not identify the specific application name
Used for traffic accounting and baselining
NBAR
Performs deep packet inspection to identify the application (e.g., Skype, BitTorrent)
Looks at the payload inside each packet
Used for application-level policy enforcement
Traditional Firewall
Filters traffic based only on source/destination IP, port, and protocol
Cannot identify applications that hide on non-standard ports
Lacks integrated intrusion prevention capabilities
Next-Generation Firewall (NGFW)
Includes application awareness via NBAR or similar DPI engines
Can enforce policies based on application identity, not just port
Integrates Intrusion Prevention System (IPS) and threat intelligence
Signature-Based Detection
Matches traffic against known malware signatures or patterns
Cannot detect zero-day or novel attacks
Generates alerts based on static rules
Behavioural Analysis (Stealthwatch)
Establishes a baseline of normal network behaviour
Flags deviations that may indicate unknown threats or insider misuse
Uses machine learning to adapt to changing traffic patterns
AVC (Application Visibility and Control)
Focuses on identifying applications and allowing or blocking them
Primarily a security and compliance tool
Decides which applications are permitted on the network
QoS (Quality of Service)
Focuses on prioritising bandwidth for allowed applications
Primarily a performance and resource management tool
Decides how much bandwidth each permitted application gets
Mistake
NetFlow and NBAR do the same job of identifying applications.
Correct
NetFlow only records flow metadata (IP addresses, ports, timestamps) and does not identify the application. NBAR performs deep packet inspection to identify the specific application name.
Both tools are used in visibility, so beginners assume they are interchangeable, but they serve completely different layers of analysis.
Mistake
If traffic is encrypted, you cannot see anything about it, so you must block all encrypted traffic to be safe.
Correct
Encrypted Traffic Analytics (ETA) can classify encrypted flows by analysing packet sizes, timing, and directionality patterns without decrypting the payload. You do not need to block all encrypted traffic.
The word 'encrypted' scares beginners into thinking visibility is impossible, but the exam tests that modern tools like ETA still give you control.
Mistake
Application control is only about blocking unwanted applications.
Correct
Application control also includes allowing, prioritising via Quality of Service (QoS), throttling bandwidth, and logging traffic for compliance. Blocking is only one action among many.
Beginners focus on the most obvious use case (blocking social media) and miss the broader policy enforcement that includes traffic shaping and prioritisation.
Mistake
Visibility means you need to capture every single packet (full packet capture) to analyse traffic.
Correct
Visibility typically uses flow-level data (NetFlow/IPFIX) or sampled traffic, which provides a summary without the storage and processing overhead of full packet capture. Full packet capture is used for forensic investigation after an alert, not for continuous visibility.
The term 'visibility' sounds like you need to see everything, but in practice it means having useful metadata and summaries, not raw packet dumps.
Mistake
A traditional firewall can provide application visibility because it sees the port number (e.g., TCP 443 = HTTPS).
Correct
Many applications now run on non-standard ports or hide behind standard ports. NBAR performs deep packet inspection to look at the actual payload, not just the port number, to identify the true application.
This misconception arises because older exams focused on port-based firewalling, but the modern exam tests that port-based identification is unreliable.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
NetFlow records metadata about a traffic flow (who sent what, when, and how much data). NBAR inspects the actual content of packets to identify which application generated the flow. NetFlow gives you a summary; NBAR gives you the application name.
Not the content itself, but Cisco's Encrypted Traffic Analytics (ETA) can classify encrypted flows by analysing packet sizes, timing, and directionality patterns without decrypting the payload. This allows you to identify the type of application even when the data is encrypted.
No, Cisco's Next-Generation Firewall (NGFW) running Firepower Threat Defence (FTD) combines both. It uses NBAR for visibility and the FMC's access control policy for enforcement, all in one platform.
QoS allows you to prioritise or limit bandwidth for specific applications. For example, you can guarantee 50% of available bandwidth for VoIP traffic while capping YouTube streaming to 10 Mbps. This ensures critical business applications get the resources they need.
Stealthwatch uses behavioural analysis: it learns the normal traffic patterns for each device and user, then flags any significant deviation. This catches zero-day attacks and insider threats that signature-based tools might miss.
IPFIX is the industry-standard version of NetFlow. NetFlow is Cisco-proprietary, while IPFIX is defined by the IETF and works across multi-vendor environments. Both export flow metadata, but IPFIX is more flexible and extensible.
Deep packet inspection (DPI) means the device looks beyond just the source and destination addresses (the envelope) and actually reads the data inside the packet (the letter) to see which application sent it. NBAR is Cisco's DPI engine.
You've finished Visibility and Application Control. Continue through the 350-701 study guide to build a complete picture of the exam.
Done with this chapter?