Apprentice Palo Alto Networks Cybersecurity Apprentice Questions and Answers

A false positive occurs when a security tool generates an alert for activity that is actually benign. Overly generalized traffic match criteria can cause a high number of false positives because the detection rule captures too much normal behavior. For example, a rule that flags all encrypted outbound traffic as suspicious would produce excessive alerts because encrypted web traffic is common and expected. Effective detection criteria must be specific enough to identify meaningful risk while broad enough to catch real threats. A well-defined post-breach recovery plan improves response readiness but does not directly create false positives. Strict user privileges may reduce risk and are not a normal cause of noisy alerts. A device failing to receive an IP address is an operational connectivity issue, not a typical false-positive driver. SOC teams manage false positives through tuning, baselining, enrichment, severity adjustment, and better rule logic. Reference/topics: Security Operations 6.4, false positive and false negative alerts; Security Operations 6.2, SOC performance optimization.

In the cloud shared responsibility model, the cloud provider is primarily responsible for the security of the cloud: the physical facilities, host servers, storage hardware, networking equipment, and foundational infrastructure used to deliver services. Therefore, securing underlying physical servers and network infrastructure is the provider responsibility. Customers are responsible for security in the cloud, which includes how they configure services, protect data, manage identities, and secure applications. Application-level settings are usually controlled by the customer or application owner. User access and permissions are identity-layer responsibilities and normally remain with the customer, even if the provider supplies IAM tools. End-user training is an organizational governance responsibility, not a provider obligation. The exact division changes by service model: SaaS shifts more operational responsibility to the provider, while IaaS leaves more configuration and workload security responsibility with the customer. Reference/topics: Cloud Security 5.3, cloud shared responsibility model; Cloud Security 5.2, SaaS, PaaS, IaaS, NaaS.

A vulnerability is a weakness that can be exploited by a threat actor. A code misconfiguration is a vulnerability because it represents an error or unsafe condition in how software, infrastructure, or access is configured. Examples include exposed administrative interfaces, missing authentication checks, overly permissive storage permissions, or insecure default settings. A trojan and a virus are forms of malware, not vulnerabilities. An attack on flawed code is an exploit or exploitation attempt, because it uses the weakness rather than being the weakness itself. The distinction is important: vulnerability is the condition, exploit is the method used to take advantage of it, and threat actor is the entity performing the action. Security programs reduce risk by discovering vulnerabilities, prioritizing them by severity and exposure, and applying remediation such as patching, configuration changes, compensating controls, or access restrictions. Reference/topics: Cybersecurity 1.1, vulnerabilities and exploits; Cybersecurity 1.3, common attack types.

A Wide Area Network, or WAN, connects systems, offices, users, or data centers across large geographic areas. WANs commonly link branch offices to headquarters, cloud resources, remote sites, or regional facilities. This distinguishes a WAN from a LAN, which is usually limited to a local environment such as a building, office, or campus segment. A PAN, or Personal Area Network, covers a very small range around an individual user, such as Bluetooth-connected personal devices. A SAN, or Storage Area Network, is a specialized network for storage access and is not defined by large geographic coverage in the same way as a WAN. WAN knowledge is foundational for cybersecurity because security teams must understand how traffic traverses distributed environments, how remote sites connect, and where controls such as VPN, SD-WAN, firewalls, and routing policies apply. Palo Alto Networks lists area network types, including WAN, LAN, and SD-WAN, as part of the Network Fundamentals blueprint. Reference: Cybersecurity Apprentice Datasheet, Network Fundamentals 2.1.

Internet of Things devices are specialized connected devices that communicate over networks but are not general-purpose user workstations. A security camera is a common IoT device because it collects video, connects to a network, and is often managed remotely. A patient imaging machine is also an IoT or medical IoT device because it is a specialized connected system used in healthcare environments to collect or process clinical data. These devices often have embedded operating systems, unique protocols, long replacement cycles, and limited local security controls. A laptop is an endpoint, but it is a general-purpose computing device rather than a typical IoT device. A router is a network infrastructure device; although some consumer routers have smart features, the certification context distinguishes infrastructure devices from IoT examples. IoT security matters because these devices can expand the attack surface, may be difficult to patch, and often require visibility and segmentation. Palo Alto Networks places IoT devices and endpoints under the Endpoint Security domain. Reference: Cybersecurity Apprentice Datasheet, Endpoint Security 4.1.

An initial action in incident investigation is to identify indicators of compromise, often called IOCs. IOCs are observable artifacts that suggest malicious activity, such as suspicious IP addresses, domains, file hashes, registry keys, process names, login patterns, or unusual network connections. Identifying IOCs helps determine whether an incident exists, what systems may be affected, and what evidence should be collected next. Creating a timeline is important, but it normally depends on first gathering relevant indicators and event data. Writing a threat intelligence report is a later analytical or communication activity. Removing threats from the system is part of containment or eradication and should be performed carefully after enough evidence is preserved and scope is understood. In security operations, moving too quickly to remove artifacts can destroy evidence and weaken understanding of the incident. The investigation process should establish source, scope, impact, and containment priorities. Reference/topics: Security Operations 6.1, investigate and mitigate; Security Operations 6.3, incident response plan.

Batch 4 — Questions 41–55

A proxy server acts as an intermediary between a client and an online resource. Instead of the user system connecting directly to the destination server, the request is sent to the proxy, which forwards, filters, logs, or inspects the traffic according to policy. This design allows organizations to control web access, enforce acceptable use policies, inspect content, apply authentication, and hide some internal network details from external destinations. A proxy does not increase the processing power of the user’s device. It is not limited to email, although mail security gateways can perform similar intermediary functions for email traffic. It also does not directly connect endpoint agents to web servers as its core function. In security architecture, proxies are useful control points because they sit in the request path and can make decisions before a user reaches a site or downloads content. Reference/topics: Network Security 3.3, proxies and URL filtering; Network Security 3.6, enterprise browsers.

A core purpose of security operations is investigating security events to determine whether they represent real threats, policy violations, or benign activity. Security operations teams monitor alerts, analyze evidence, investigate suspicious behavior, contain incidents, and improve detection and response processes. Asset tracking is important for security and IT operations, but it is not the main purpose described here. Installing endpoint security software is a deployment task usually handled by endpoint, infrastructure, or IT teams, although the SOC may consume the telemetry. Aligning applications to compliance standards is part of governance, risk, and compliance activities. Security operations is the day-to-day defensive function that turns telemetry into decisions and action. It asks: what happened, what is affected, how severe is it, what should be done, and how can recurrence be reduced? Investigation is therefore central to the SOC mission. Reference/topics: Security Operations 6.1, Identify/Detect, Investigate, Mitigate, Improve; Security Operations 6.3, event and alert.

A hub operates at Layer 1, the Physical layer of the OSI model. It repeats electrical or signaling information received on one port out to other ports without understanding frames, MAC addresses, IP addresses, sessions, or applications. Because a hub does not make intelligent forwarding decisions, every connected device receives the same signal, creating a shared collision domain in older Ethernet environments. This differs from a switch, which operates primarily at Layer 2 and forwards frames based on MAC addresses. Routers operate at Layer 3 using IP addressing and routing tables. Layer 4 devices or functions evaluate transport information such as TCP or UDP ports. The purpose of knowing where devices sit in the OSI model is to understand what data each device can inspect and what security decisions it can support. A hub provides connectivity but not meaningful segmentation or filtering. Reference/topics: Network Fundamentals 2.6, OSI model; Network Fundamentals 2.7, devices operating at Layers 1 through 4.

VPN gateways commonly provide site-to-site connectivity and remote access. Site-to-site VPN connects networks across encrypted tunnels, such as branch office to headquarters or cloud network to data center. Remote access VPN allows individual users to securely connect to enterprise resources from outside the corporate network. Certificate refresh may support authentication infrastructure in some environments, but it is not a primary VPN gateway function in this question. URL filtering controls web access based on categories or reputation and is a separate network security function. VPN gateways terminate encrypted tunnels, authenticate peers or users, and route protected traffic into the appropriate network. They are important because they allow secure communication over untrusted networks, but they must be configured carefully. Weak authentication, overly broad access, split tunneling misconfiguration, or poor logging can turn VPN access into a major risk path. Reference/topics: Network Security 3.3, VPNs; Network Security 3.4, IKE and tunneling protocols.

A core function of DLP is protecting against sensitive information exposure. DLP solutions identify, monitor, and control sensitive data such as personal information, payment card data, intellectual property, credentials, source code, or regulated records. DLP may inspect content, file types, labels, patterns, user context, and destination risk to determine whether data should be allowed, blocked, encrypted, quarantined, or logged. Encrypting all transmissions is not the general definition of DLP; encryption may be one enforcement action, but DLP decisions are content-aware and policy-based. System backups support recovery and resilience, not data loss prevention. Enhancing network speed is a performance function. DLP is important because data can leave through email, web uploads, cloud storage, removable media, or compromised accounts. Effective DLP helps reduce both accidental leakage and intentional exfiltration. Reference/topics: Network Security 3.5, DLP; Identity Security 7.2.3, least privilege.

Zero Trust is a strategic security approach based on continuous validation rather than implicit trust. Instead of assuming that users, devices, applications, or workloads are trustworthy because they are inside a network boundary, Zero Trust requires verification throughout the digital interaction. This includes validating identity, device posture, application access, least privilege, segmentation, and ongoing behavior. Incident response plans are important after suspicious activity or incidents occur, but they are not the continuous trust validation model. Compliance planning maps controls to regulatory or framework requirements, but compliance alone does not guarantee continuous security verification. Operations playbooks guide repeatable SOC actions, but they are procedural tools rather than the strategic architecture described in the question. Zero Trust adoption changes how access decisions are made: trust is earned, scoped, and re-evaluated, not permanently granted. Reference/topics: Cybersecurity 1.6, Zero Trust; Identity Security 7.1 and 7.2, IAM, MFA, RBAC, least privilege.

A next-generation firewall evaluates traffic beyond basic ports, protocols, and IP addresses. It can inspect application-layer information to identify the actual application, user context, content, and threat indicators before deciding whether traffic should be allowed, blocked, or further inspected. This is the defining difference between a traditional firewall and an NGFW. A switch primarily forwards frames using Layer 2 information, such as MAC addresses. A router forwards packets using Layer 3 information, such as destination IP addresses and routing tables. A WAN accelerator improves performance across wide area links but is not primarily a security enforcement device that makes application-layer allow/block decisions. Application-aware inspection matters because modern applications may use common ports such as TCP 443, making port-only policy insufficient. NGFWs address this by classifying traffic according to application behavior and enforcing security policy accordingly. Reference/topics: Network Security 3.2, stateful firewalls and next-generation firewalls; Network Fundamentals 2.6 and 2.7, OSI model and devices.

Zero Trust is implemented by continuously inspecting and validating traffic, identity, device posture, application access, and behavior. The model does not assume trust based on network location. Instead, every access request should be verified, authorized, and limited to what is necessary. Assigning all security to a proxy solution is too narrow; Zero Trust is an architecture and operating model, not a single product. Designating failover paths improves availability, but it does not implement Zero Trust. Removing excess network devices may simplify infrastructure but does not create continuous validation. In a network context, Zero Trust commonly includes segmentation, least privilege access, strong authentication, application-aware policy, traffic inspection, and continuous monitoring. The goal is to reduce implicit trust and limit the blast radius if a user, device, or workload is compromised. A helpful analogy: Zero Trust is not one locked front door; it is badge checks throughout the building. Reference/topics: Cybersecurity 1.6, Zero Trust; Network Security 3.1 and 3.2.

CI/CD improves the secure development pipeline by making software build, test, delivery, and deployment processes more automated, repeatable, and controlled. Continuous integration encourages developers to merge code frequently into a shared repository where automated tests and checks can run. Continuous delivery keeps software in a deployable state, while continuous deployment can automatically release changes that pass required tests. Security can be embedded into this pipeline through static analysis, dependency scanning, container image scanning, secrets detection, infrastructure-as-code checks, and policy gates. The goal is not merely faster software delivery, but safer and more reliable delivery. Network threat alert potential is a SOC concern, not the primary CI/CD outcome. API interaction optimization may occur in development, but it is too narrow. Storage quotas for code are repository management settings. Secure CI/CD reduces late-stage security surprises and helps organizations detect weaknesses earlier when they are cheaper and easier to fix. Reference/topics: Cloud Security 5.6, CI/CD; Identity Security 7.4.2, CI/CD pipeline secrets.

The Session layer of the OSI model manages the establishment, maintenance, and termination of sessions between communicating systems. It is associated with determining how long communications remain open, how sessions are coordinated, and how dialog control is maintained. The Transport layer provides end-to-end delivery functions such as segmentation, reliability, flow control, and port-based communication through protocols such as TCP and UDP. The Application layer supports user-facing network services and application protocols. The Network layer handles logical addressing and routing between networks. Although real-world TCP/IP implementations often combine upper-layer functions, the OSI model separates them conceptually to clarify responsibilities. In security analysis, session understanding matters because attackers may hijack sessions, abuse long-lived sessions, or maintain persistence through ongoing connections. Firewalls, proxies, and identity systems often enforce timeout, reauthentication, and session termination policies to reduce risk. Reference/topics: Network Fundamentals 2.6, OSI and TCP/IP models.

An incident response plan is the documented strategy that defines how an organization detects, analyzes, contains, eradicates, recovers from, and learns from cybersecurity incidents or disruptive events. It assigns responsibilities, escalation paths, communication rules, evidence-handling expectations, and recovery procedures so that teams can act quickly under pressure. MTTR, or mean time to respond/recover, is a performance metric that measures how long response or recovery takes. MTTD, or mean time to detect, measures detection speed. Security framework alignment helps map controls and practices to recognized standards, but it is not the operational response document itself. A strong incident response plan reduces confusion during an event because teams do not need to invent roles and procedures while an attack is unfolding. It also improves post-incident review by creating a baseline for what should have happened. Reference/topics: Security Operations 6.3, incident response plan and disaster recovery plan; Security Operations 6.1, investigate, mitigate, improve functions.

MTTD, or mean time to detect, measures how long it takes a security team to discover a cybersecurity incident or suspicious activity. A lower MTTD indicates that detection controls, monitoring processes, alert quality, and analyst workflows are working effectively. MTTD is important because attackers often cause more damage the longer they remain undetected. MTTR, or mean time to respond or recover, measures how long it takes to respond to or recover from an incident after detection. MFA is multi-factor authentication, an identity security control used to strengthen login security. NAT is network address translation, which converts one IP address to another. Security operations teams use metrics such as MTTD and MTTR to evaluate SOC performance, improve alerting, tune detection logic, and reduce operational delays. Strong logging, SIEM correlation, endpoint telemetry, threat intelligence, and automation can help reduce detection time. Reference/topics: Security Operations, SOC metrics, MTTD, MTTR, incident detection and response.

Antivirus software contributes to endpoint security by scanning files, programs, and sometimes memory or processes for known malware signatures and suspicious patterns. Signature-based detection compares observed files or code characteristics against known malicious indicators. This helps identify viruses, trojans, worms, spyware, and other malicious software before or during execution. Antivirus may also include heuristic or behavioral detection, but the answer specifically identifies known malware signatures, which is a classic antivirus function. Strong password policies are part of identity security, not antivirus. Filtering unsolicited commercial email is a function of email security or spam filtering. Isolating untested applications describes sandboxing or application isolation rather than standard antivirus scanning. Antivirus remains a basic endpoint control, although modern endpoint protection platforms often add behavior analytics, exploit prevention, device control, and response capabilities. The objective is to reduce the chance that malicious files can execute or persist on user systems. Reference/topics: Endpoint Security 4.3, antivirus and endpoint security components; Cybersecurity 1.5, threat prevention practices.

The function of an antivirus solution is to detect malicious files using malware signatures and related detection methods. Signature-based detection compares files or code patterns against known malware indicators. Antivirus may also include heuristic, reputation-based, or behavioral detection, but known malware signature scanning is the classic function. Regulating traffic based on security rules is a firewall function. Protecting against DNS poisoning is handled through DNS security, secure resolver behavior, validation mechanisms, and network protections. Protecting user credentials is primarily an identity security function involving MFA, password management, phishing resistance, and access controls. Antivirus is a core endpoint security component because malicious files commonly reach users through downloads, attachments, removable media, compromised websites, or unauthorized software. It helps prevent execution, quarantine malicious content, and alert administrators. While modern endpoint platforms go beyond antivirus, the foundational antivirus role remains malware file detection and prevention on the device. Reference/topics: Endpoint Security 4.3, antivirus; Cybersecurity 1.5, threat prevention practices.

AI can help SOC teams by improving alert triage and incident response. In alert triage, AI can cluster related alerts, summarize event context, identify likely severity, enrich indicators, and reduce analyst time spent on repetitive review. This helps analysts focus attention on the events most likely to represent real risk. In incident response, AI can support decision-making by summarizing timelines, suggesting next steps, mapping activity to known tactics, or helping execute defined workflows through automation. Vulnerability patching may be prioritized using analytics, but applying patches is not primarily an alert-handling function. SOC resource management may benefit from reporting and forecasting, but it is less directly tied to alert analysis than triage and response. AI is most useful when it augments analysts rather than replaces them: it speeds up repetitive work, improves correlation, and presents context in a usable form. Reference/topics: Security Operations 6.2, automation and AI for SOC performance; Security Operations 6.7, AI as it relates to alert analysis.

A trojan is malware disguised as legitimate or useful software. It tricks the user or system into running it, then performs malicious actions such as installing backdoors, stealing data, downloading additional payloads, or giving attackers remote access. The key characteristic is deception: the malware is hidden inside or presented as a trusted application. A botnet is a network of compromised devices controlled by an attacker, often through command-and-control infrastructure. Ransomware encrypts or locks systems and demands payment. A virus is malware that attaches to files or programs and replicates when executed, but the scenario specifically describes malicious code hidden within an application to avoid detection, which fits a trojan. Trojans are common because they exploit user trust and can bypass purely technical controls if users install unauthorized software. Endpoint protection, application control, user training, and least privilege help reduce trojan risk. Reference/topics: Cybersecurity 1.3, malware types; Endpoint Security 4.3, antivirus.

An API, or application programming interface, allows software applications and services to communicate and share data in a structured way. APIs define how requests are made, what data formats are accepted, what operations are available, and how responses are returned. In cloud and modern application environments, APIs are fundamental because applications often rely on microservices, third-party integrations, identity providers, automation tools, and cloud management platforms. APIs do not allow operating systems to redesign themselves. They are not specifically for machine learning models to check datagrams, and they are not primarily hardware modification controls. From a security perspective, APIs must be protected because they expose application functions and data paths. API security includes authentication, authorization, rate limiting, input validation, logging, and secrets protection. If poorly secured, APIs can expose sensitive data or allow unauthorized actions. Reference/topics: Cloud Security 5.4, common cloud terms including API and microservice; Identity Security 7.4, secrets management.

When a device or router does not have a more specific route for a destination, traffic is sent to the default gateway or default route. The default gateway acts as the next hop for traffic destined outside the local network when no exact path is known locally. On an endpoint, the default gateway is usually a router interface. On a router, the default route points to another router or upstream path. A VPN gateway may be used for encrypted tunnel traffic, but it is not always the default path. A hub repeats signals and does not make routing decisions. The internet may be the eventual destination path for many routes, but traffic must first be forwarded to the configured default gateway. Default gateways are essential because without them, hosts could communicate only with systems on their local subnet unless specific routes were manually configured. Reference/topics: Network Fundamentals 2.3, function of a default gateway; Network Fundamentals 2.5, routing.

East-west traffic is internal traffic moving between systems within the same environment or data center. Packets moving between virtual servers across a virtual switch are east-west because they remain inside the data center or virtualized environment. This traffic may never pass through a traditional perimeter firewall unless the architecture specifically routes it through inspection points. Internet-originated traffic to a public IP address is north-south because it enters the environment from outside. Traffic from a virtual desktop to a cloud-based proxy leaves toward an external or cloud service, making it north-south or external service traffic. Traffic from a cloud-based server to a virtual desktop crosses environment boundaries and is not the clearest east-west example. East-west visibility is critical because attackers who compromise one workload often attempt lateral movement to other internal systems. Segmentation, internal firewalls, workload security, and telemetry help control this risk. Reference/topics: Network Fundamentals 2.2, east-west and north-south traffic; Cloud Security 5.4, virtualization.

A HIDS directly integrates with an endpoint or host and monitors activity on that system. It can evaluate logs, file changes, processes, authentication activity, configuration changes, and local indicators that may not be visible on the network. This makes it a last line of defense because it can detect suspicious activity after traffic has reached the host or when malicious activity occurs locally. A NIDS monitors traffic on a network segment rather than being installed on each individual endpoint. Answer A incorrectly describes network-based detection as endpoint-installed. Answer B is awkwardly worded and less precise than answer C. Answer D incorrectly assigns endpoint integration to NIDS. HIDS and NIDS are complementary. NIDS provides broad network visibility, while HIDS provides deep host-level visibility. Security teams use both types of telemetry to understand attack scope and confirm whether suspicious network behavior resulted in endpoint compromise. Reference/topics: Cybersecurity 1.4, IDS, HIDS, and NIDS; Endpoint Security 4.3, host-based controls.

People should be the first pillar when establishing a security operations department. Tools and processes matter, but a SOC ultimately depends on skilled people who understand the environment, interpret alerts, make decisions, communicate risk, and improve operations. Without defined roles, responsibilities, escalation paths, and analyst capability, even advanced technology can become noisy and ineffective. Processes come next because people need repeatable methods for triage, investigation, mitigation, and improvement. Technology should support those people and processes, not replace them. Business context is also essential because the SOC must prioritize what matters most to the organization, but the first practical foundation is staffing and capability. A strong SOC needs analysts, incident responders, engineers, threat intelligence support, leadership, and clear ownership. Security operations is not just a tool stack; it is an operating function that converts telemetry into risk reduction. Reference/topics: Security Operations 6.1, SOC functions; Security Operations 6.2, optimizing SOC performance.

Batch 8 — Questions 101–113

A firewall is an inline security control that can inspect traffic destined for a host and determine whether to allow, block, or further analyze it. Modern firewalls, especially next-generation firewalls, can identify malicious traffic using application awareness, threat prevention, signatures, URL categories, and policy context. Quality of service prioritizes or manages traffic performance, not security inspection. Endpoint protection resides on the host and is not primarily an inline network option. A WAN accelerator improves performance over wide area networks but does not serve as the main malicious traffic enforcement device. Inline placement matters because it allows the firewall to stop traffic before it reaches the target. This differs from passive monitoring tools that may alert after seeing suspicious traffic but do not block it directly. Firewalls are foundational network security controls because they define trust boundaries and enforce policy between zones, networks, users, applications, and destinations. Reference/topics: Network Security 3.2, firewalls and NGFWs; Cybersecurity 1.5, firewalls as threat prevention systems.

Actions on the Objective is the stage where the attacker performs the mission they intended to accomplish. This may include stealing data, encrypting systems for ransom, defacing a website, destroying information, disrupting services, or manipulating business processes. Data exfiltration and web property defacement are clear outcomes of this phase because the attacker has already progressed through earlier stages and is now achieving the final goal. Host sweeps and port scans belong to reconnaissance because they help identify targets. Outbound communication channels are associated with Command and Control, where compromised systems exchange instructions with attacker infrastructure. Exploits launched against a vulnerable application occur during the exploitation phase. Understanding this lifecycle helps defenders align controls: reconnaissance can be limited through exposure management, delivery can be filtered, exploitation can be blocked through patching and IPS, C2 can be detected through outbound monitoring, and actions on objectives can be constrained by segmentation and DLP. Reference/topics: Cybersecurity 1.2, cyber attack lifecycle.

DHCP provides IP addressing information to a client. When a device joins a network, it can request configuration from a DHCP server instead of requiring manual assignment. The server leases an IP address to the client and may also provide subnet mask, default gateway, DNS server, lease duration, and other options. DHCP does not provide a MAC address; the MAC address is assigned to the network interface by the hardware vendor. It does not provide a security zone, which is a firewall or segmentation concept. It also does not assign a port range in the normal client addressing process. DHCP is important operationally because it reduces manual configuration and supports scalable network management. It is also useful in investigations because DHCP lease records can help map an IP address observed in logs to the device that used it at a specific time. Reference/topics: Network Fundamentals 2.4, DHCP; Network Fundamentals 2.3, default gateway.

A Network-Based Intrusion Detection System monitors network traffic and reports suspicious findings to administrators or security tools. It observes packets traversing a network segment and compares activity against signatures, patterns, protocol anomalies, or behavior models. Because it is detection-focused, a NIDS typically alerts rather than blocks traffic inline. Scanning and quarantining infected files on a host machine is an endpoint security function. Proxying traffic before it reaches an internal network is a proxy function. Blocking malicious traffic in real time is more closely associated with an IPS or firewall. A NIDS is useful because it can provide visibility across multiple hosts without installing an agent on each one. However, encrypted traffic, high throughput, and east-west blind spots can limit visibility if sensors are not placed correctly. SOC teams use NIDS alerts as evidence during investigation and correlation. Reference/topics: Cybersecurity 1.4, NIDS and other threat detection systems; Security Operations 6.3, alerts and events.