Dev.to Security 🔐 Cybersecurity 👁 0 📖 8 min read

Palo Alto Cybersecurity Apprentice Certification: Learn All 7 Domains From Your Terminal

The Palo Alto Networks Certified Cybersecurity Apprentice is a foundational certification. It checks that you understand cybersecurity concepts, network fundamentals, network, endpoint and cloud security, security operat

The Palo Alto Networks Certified Cybersecurity Apprentice is a foundational certification. It checks that you understand cybersecurity concepts, network fundamentals, network, endpoint and cloud security, security operations and identity security. You don't need any work experience to take it. The exam questions are conceptual, but the concepts stick much faster when you've seen them on a real machine. This post gives you the blueprint and the exam facts, then one short terminal or Python exercise for each of the seven domains.

Everything here runs on a laptop with Python 3, OpenSSL 3 and a shell. You don't need a firewall, a cloud account or a lab.

What is the Palo Alto Cybersecurity Apprentice certification?

It's the entry point to the Palo Alto Networks certification portfolio. According to the official Cybersecurity Apprentice certification page, it's aimed at high school and university students, career changers and non-technical professionals such as marketing and sales staff who are moving into cybersecurity. The level is Foundational, and Palo Alto recommends reviewing the datasheet topics before working through the digital learning path.

The quick facts:

Item Detail
Exam name Palo Alto Networks Certified Cybersecurity Apprentice
Exam code CyberSec-Apprentice
Level Foundational, no work experience required
Questions 50
Time 90 minutes
Passing score 860 on a scale of 300 to 1000
Price US$150
Language English, with a 30-minute extension by default in non-English-speaking countries
Registration Pearson

The level, audience, language and extension come from Palo Alto Networks. The question count, time, passing score and price are as listed on the NWExam syllabus page, so check them again when you book.

What is on the 2026 blueprint?

The Cybersecurity Apprentice datasheet (May 2026 edition) lists seven domains:

Domain Weight
1. Cybersecurity 16%
2. Network Fundamentals 16%
3. Network Security 14%
4. Endpoint Security 10%
5. Cloud Security 13%
6. Security Operations 13%
7. Identity Security 18%

Identity Security is the biggest domain at 18%. It covers IAM, privileged access management, PKI and secrets management. If you studied for an older entry-level security exam, that's the area most likely to be new to you. The domain also mentions AI-powered attacks, enterprise browsers and AI in alert analysis, so the blueprint is current.

Domain 1, Cybersecurity: can you name the attack lifecycle stage?

Domain 1 asks you to identify vulnerabilities, exploits, attack types and the stages of the attack lifecycle. A useful exercise is to take events from real logs and label each one with its stage. This snippet does that for a short, made-up incident:

lifecycle = ["reconnaissance", "weaponization", "delivery",
             "exploitation", "installation", "command and control",
             "actions on the objective"]

incident = {
    "port scan from 203.0.113.50 against the VPN gateway": "reconnaissance",
    "phishing email with a macro document": "delivery",
    "macro runs PowerShell on the laptop": "exploitation",
    "scheduled task created for persistence": "installation",
    "beacon to an unknown domain every 60 seconds": "command and control",
}

for event, stage in incident.items():
    print(f"{lifecycle.index(stage) + 1}. {stage:<22} <- {event}")

The exam point is prevention: every stage you block stops the attack. That's also how the blueprint frames threat prevention (task 1.5) and Zero Trust (task 1.6): never trust by default, and check every request.

Domain 2, Network Fundamentals: what does your own machine tell you?

The tasks cover the default gateway, NAT, DNS and DHCP, routed and routing protocols, and the OSI and TCP/IP models. You can see most of them on your own computer:

# Default gateway (Linux / macOS)
ip route show default        # Linux
netstat -rn | grep default   # macOS

# Windows: gateway, DHCP server and DNS servers in one place
ipconfig /all

# DNS: name to address, and the mail servers for a domain
nslookup example.com
dig +short example.com A
dig example.com MX

# Layer 4: which TCP and UDP ports are listening
ss -tuln                     # Linux
netstat -an                  # Windows / macOS

When you run ipconfig /all, the DHCP server and the default gateway are often the same home router, and the router also does NAT for every device behind it. One box doing three jobs is a good way to remember what each one does. For task 2.2, north-south traffic goes in or out of the environment (your laptop to example.com), and east-west traffic stays inside it (your laptop to the printer).

Domain 3, Network Security: how does subnetting segment a network?

Task 3.1 lists IP subnetting, VLANs and zones as segmentation methods. Python's ipaddress module lets you check subnet maths without a calculator:

import ipaddress

net = ipaddress.ip_network("10.10.0.0/22")
print(net.num_addresses)                    # 1024
for sub in net.subnets(new_prefix=24):
    print(sub)                              # 10.10.0.0/24 ... 10.10.3.0/24

print(ipaddress.ip_address("10.10.3.7") in net)    # True
print(ipaddress.ip_address("10.10.3.7").is_private) # True

Split a /22 into four /24s, call them users, servers, IoT and guests, and decide which ones may talk to each other. That's the thinking behind zones on a next-generation firewall. A stateful firewall tracks connections by address and port. An NGFW also identifies the application, the user and the content (task 3.2).

For task 3.4 (tunnelling protocols), look at a TLS session yourself:

openssl s_client -connect example.com:443 -servername example.com </dev/null 2>/dev/null \
  | grep -E "Protocol|Cipher"

Domain 4, Endpoint Security: is the endpoint patched and protected?

Endpoint security is the smallest domain at 10%, and it's about objectives and components: updates, antivirus and host-based firewalls (task 4.3). Check all three on your own machine:

# Windows (PowerShell)
Get-MpComputerStatus | Select AMServiceEnabled, AntivirusSignatureLastUpdated
Get-NetFirewallProfile | Select Name, Enabled
Get-HotFix | Sort-Object InstalledOn -Descending | Select -First 5

# Ubuntu / Debian
sudo ufw status
apt list --upgradable 2>/dev/null | head

IoT devices (task 4.1) are the endpoints where you usually can't install any of this, which is why the network has to protect them instead.

Domain 5, Cloud Security: who is responsible for what?

The tasks cover the four deployment models (public, private, hybrid and community), the service models (SaaS, PaaS, IaaS, NaaS), the shared responsibility model and CI/CD. A small lookup table is a quick way to drill shared responsibility:

responsibility = {
    #  layer               IaaS        PaaS        SaaS
    "data":             ("customer", "customer", "customer"),
    "identity & access": ("customer", "customer", "customer"),
    "application":      ("customer", "customer", "provider"),
    "operating system": ("customer", "provider", "provider"),
    "virtualization":   ("provider", "provider", "provider"),
    "physical":         ("provider", "provider", "provider"),
}
model = {"IaaS": 0, "PaaS": 1, "SaaS": 2}

for layer, owners in responsibility.items():
    print(f"{layer:<18} SaaS -> {owners[model['SaaS']]}")

Data and identity stay with the customer in every model. If an exam question asks who is responsible for a misconfigured access policy in a SaaS app, the answer is the customer.

Domain 6, Security Operations: can you read a syslog line?

Task 6.5 is the function of syslog, and task 6.4 is false positives and false negatives. This parses an RFC 5424 message and decodes its priority:

line = "<34>1 2026-11-21T10:22:15.003Z fw01 sshd 4123 - - Failed password for root from 203.0.113.50 port 51234 ssh2"

pri = int(line[1:line.index(">")])
facility, severity = divmod(pri, 8)
print(facility, severity)   # 4 (security/auth), 2 (critical)

Then the alert maths that SOC analysts live with:

alerts = {"true_positive": 12, "false_positive": 88,
          "false_negative": 3, "true_negative": 9897}

precision = alerts["true_positive"] / (alerts["true_positive"] + alerts["false_positive"])
print(f"{precision:.0%} of alerts were real")   # 12%

Eighty-eight wasted investigations out of 100 alerts is why the blueprint lists automation and AI (tasks 6.2 and 6.7) and SOAR and SIEM (task 6.6). A SIEM collects and correlates events like the syslog line above. A SOAR platform runs the response playbook. A false negative is the dangerous one, because nothing alerts at all.

Domain 7, Identity Security: how do MFA, PKI and secrets work?

This is the heaviest domain, so it gets three exercises.

Multifactor authentication (task 7.1.2). The six-digit codes in authenticator apps are TOTP, a hash of a shared secret and the current 30-second window:

import base64, hashlib, hmac, struct, time

def totp(secret_b32, step=30, digits=6):
    key = base64.b32decode(secret_b32)
    counter = struct.pack(">Q", int(time.time()) // step)
    h = hmac.new(key, counter, hashlib.sha1).digest()
    offset = h[-1] & 0x0F
    code = (struct.unpack(">I", h[offset:offset + 4])[0] & 0x7FFFFFFF) % 10**digits
    return str(code).zfill(digits)

print(totp("JBSWY3DPEHPK3PXP"))

The code proves you have the device, which is the "something you have" factor.

Public and private keys (task 7.3.2). Sign with the private key and verify with the public key:

openssl genpkey -algorithm ed25519 -out key.pem
openssl pkey -in key.pem -pubout -out pub.pem
echo "approve change 4711" > msg.txt
openssl pkeyutl -sign -inkey key.pem -rawin -in msg.txt -out msg.sig
openssl pkeyutl -verify -pubin -inkey pub.pem -rawin -in msg.txt -sigfile msg.sig
# Signature Verified Successfully

Change one character in msg.txt and verification fails. For certificate authorities and trust chains (task 7.3.1), print the chain a website sends:

openssl s_client -connect example.com:443 -servername example.com -showcerts </dev/null 2>/dev/null \
  | grep -E "^ *[0-9] s:|^ *i:"

Each certificate's issuer (i:) is the subject (s:) of the next one up, ending at a root CA your operating system already trusts.

Secrets management (task 7.4). Search a repository for something that should never be there:

git grep -nE "AKIA[0-9A-Z]{16}|-----BEGIN (RSA|OPENSSH) PRIVATE KEY-----"

If that finds anything, the fix is a secrets vault, with credentials injected into the CI/CD pipeline at run time and rotated (tasks 7.2.1 and 7.4.2).

How long does it take to prepare?

For someone new to IT, three to four weeks of an hour a day is a realistic plan:

Week Domains Do this
1 Cybersecurity, Network Fundamentals Map an incident to the lifecycle, run the network commands above
2 Network Security, Endpoint Security Subnet a /22, audit your own laptop's updates and firewall
3 Cloud Security, Security Operations Drill shared responsibility, parse syslog, learn the SIEM vs SOAR difference
4 Identity Security, then review TOTP, signing and the certificate chain, then timed practice

Work through the datasheet task by task and the Palo Alto digital learning path alongside it. The CyberSec-Apprentice syllabus on NWExam lists the same objectives in one place, which works well as a checklist. In week 4, the Cybersecurity Apprentice sample questions help you see how the concepts are worded in exam questions, which is different from how they look in a terminal.

FAQ

Is the Palo Alto Cybersecurity Apprentice certification worth it for developers?

It's worth it if you want a structured, vendor-backed tour of security basics. Developers usually know CI/CD and APIs already, and the identity and secrets topics in domain 7 relate directly to everyday work. If you already hold an associate-level security certification, look at the next level of the portfolio instead.

Do I need experience to take the exam?

No. Palo Alto Networks lists the recommended work experience as "none; entry-level".

Which domain carries the most weight?

Identity Security, at 18%. Cybersecurity and Network Fundamentals follow at 16% each.

Is the exam about Palo Alto products?

Mostly not. The blueprint is written around concepts such as Zero Trust, NGFWs, SIEM, SOAR, PKI and the shared responsibility model, rather than product configuration.

How many questions are there, and what score do I need?

As listed on NWExam: 50 questions in 90 minutes, with a passing score of 860 on a 300 to 1000 scale. Check the current figures in the Palo Alto Networks certification handbook before you book.

You don't have to memorise the seven domains as definitions. Once you've run a command for each one, most questions ask you to recognise something you've already seen.

📰 Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.