PCNSE study materials
PCNSE study resources

PCNSE study plan

PCNSE · Give each week a clear focus.

8 weeks · About 7 hours per week

Week 1

Deploy and Configure

  • Configure L3, L2, virtual-wire, and tap interfaces in a lab and verify traffic behavior for each type

  • Build security policy rules using application, user, and service objects, then confirm hit counts increment on each rule

  • Configure source NAT, destination NAT, and twice-NAT, then trace one flow end to end with session detail and packet capture

  • Diagram the relationship between zones, virtual routers, interfaces, and virtual systems for a single-vsys and a multi-vsys design

Your checkpoint

A saved lab configuration plus a one-page flow diagram tracing three test flows from ingress zone through NAT to egress zone

Week 2

Deploy and Configure & Plan (architecture, design, and deployment planning)

  • Distinguish active/passive from active/active HA and list the link types, failure triggers, and session-state behaviors for each

  • Configure HA across two lab firewalls, force a failover, and record failover duration and which sessions survived

  • Convert a stated business requirement into sizing and architecture decisions covering throughput, session capacity, and interface count

  • Write a deployment plan covering licensing, device registration, bootstrap configuration, and cutover order

Your checkpoint

An HA failover test log with timestamps and observed session behavior, plus a one-page architecture decision record for a two-site design

Week 3

Troubleshoot

  • Isolate a policy-deny symptom from a routing-loop symptom using CLI show commands, traffic logs, and counters

  • Diagnose a NAT misconfiguration by correlating session detail with packet captures on both directions

  • Interpret session table, CPU, and commit-failure indicators and rank the three most likely root causes for each

  • Order a triage checklist from fastest to slowest check and justify the ordering

Your checkpoint

A troubleshooting runbook documenting five fault scenarios, the symptom observed, the check that found it, and the verified root cause

Week 4

Troubleshoot & Operate

  • Reproduce an SSL or decryption-related connectivity failure and resolve it without disabling inspection

  • Configure log forwarding to an external collector and verify records arrive with the expected fields populated

  • Query stored logs to answer three operational questions: top denied applications, top source addresses, and rules with no hits

  • Apply a content update and verify resulting version state and any required commit

Your checkpoint

A written log-analysis report answering the three operational questions, plus a verified forwarding configuration

Week 5

Operate

  • Configure scheduled configuration backups and complete a restore, confirming the restored config matches the source

  • Set up alerting for key health thresholds and trigger one alert deliberately to prove delivery

  • Trend a health metric over time on a dashboard and define the threshold that would trigger escalation

  • Apply a configuration change through a staged workflow and verify it with a config diff before committing

Your checkpoint

An operations checklist plus a documented backup-and-restore drill with verification steps and observed results

Week 6

Advanced Security Configuration (threat prevention, decryption, VPN, and related features)

  • Build a site-to-site IPsec tunnel, confirm both IKE and IPsec phases reach up state, and verify traffic passes bidirectionally

  • Configure a remote-access VPN portal and gateway and validate user authentication end to end

  • Write forward-proxy and inbound decryption policies and explain what fails when the certificate chain is not trusted

  • Identify three traffic categories that should be excluded from decryption and justify each exclusion

Your checkpoint

VPN and decryption lab notes containing verification output for each tunnel state and the decryption policy rationale

Week 7

Advanced Security Configuration (threat prevention, decryption, VPN, and related features) & Deploy and Configure

  • Tune a security profile group covering antivirus, anti-spyware, vulnerability protection, URL filtering, and file submission, justifying every action setting

  • Configure DNS-based and credential-phishing protections and confirm events populate in the logs

  • Map eight distinct threat vectors to the specific profile settings that address them

  • Revisit policy design to reduce rule sprawl by consolidating overlapping rules without changing permitted traffic

Your checkpoint

A profile-tuning rationale table mapping eight threat vectors to settings, actions, and the log evidence each generates

Week 8

Deploy and Configure & Troubleshoot

  • Re-run all five fault scenarios from the week-3 runbook without notes and resolve each in under ten minutes

  • Complete two timed full-length practice sets and tag every miss with a domain and root-cause label

  • Condense weak-area notes into twenty recall prompts and self-test until all are answered correctly

  • Walk an end-to-end scenario from requirement to design to configuration to verification to troubleshooting on paper within 45 minutes

Your checkpoint

A final gap list with every item closed or explicitly deprioritized, plus a one-page pre-exam checklist

Milestones

Week 2: Both HA failover modes configured in the lab; failover completed with duration and session behavior documented; architecture decision record reviewed against the stated business requirement

Week 4: Score at least 75% on a timed 50-question mixed set covering domains 1 through 4, with zero unexplained misses in the troubleshooting domain

Week 6: IPsec tunnel reaches up state in both directions, remote-access VPN authenticates a test user, and a decryption policy is verified against a known site with certificate trust confirmed

Week 8: Two full-length timed practice sets completed at 80% or higher, every miss tagged by domain and root cause, and the final gap list shows no unaddressed items